NexusSDR AI — 4-Agent B2B Buying-Intent & Outbound MCP Server

Official registry AI and agents

Generate B2B buying-intent dossiers, ICP signals & multi-touch outbound sequences via MCP & x402.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http nexussdr-ai-4-agent-b2b-buying-intent-ou 'https://nexussdr-ai.run402.com/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "nexussdr-ai-4-agent-b2b-buying-intent-ou": {
            "type": "http",
            "url": "https://nexussdr-ai.run402.com/api/mcp"
        }
    }
}

Frequently asked questions

What is NexusSDR AI — 4-Agent B2B Buying-Intent & Outbound MCP Server?

Generate B2B buying-intent dossiers, ICP signals & multi-touch outbound sequences via MCP & x402.

How do I install NexusSDR AI — 4-Agent B2B Buying-Intent & Outbound MCP Server?

It runs as a remote server. In Claude Code: claude mcp add --transport http nexussdr-ai-4-agent-b2b-buying-intent-ou 'https://nexussdr-ai.run402.com/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does NexusSDR AI — 4-Agent B2B Buying-Intent & Outbound MCP Server need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Who maintains NexusSDR AI — 4-Agent B2B Buying-Intent & Outbound MCP Server?

It is published by sh.surge.nexussdr-cloud. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.