Registry and Directories

Synapse MCP is published in the official MCP Registry.

Official MCP Registry

Field	Value
Registry name	`io.github.SynapseNetworkAI/synapse-network-mcp-server`
Package	`@synapse-network-ai/mcp-server`
Remote endpoint	`https://mcp.synapse-network.ai/mcp`
Transport	`stdio` package and Streamable HTTP remote
Repository	`https://github.com/SynapseNetworkAI/Synapse-Network-MCP-Server`

Search:

curl 'https://registry.modelcontextprotocol.io/v0.1/servers?search=SynapseNetworkAI'

Third-party directories

Use the same metadata for:

Smithery
Glama
PulseMCP
mcp.so / MCP.so
awesome-mcp-servers style GitHub lists
Protodex
MCP.Directory

Directory copy

SynapseNetwork MCP Server exposes service discovery, payable invocation, and receipts for agent runtimes. Agents can discover APIs, inspect current pricing and schemas, invoke with bounded USDC spend, and fetch settlement receipts.

Security copy

Use a dedicated Synapse Agent Credential with a bounded spend limit. Read-only tools are discover_services and get_receipt. invoke_and_pay is consequential and should require user confirmation.

Use this pack when submitting Synapse MCP to Smithery, Glama, PulseMCP, mcp.so, MCP.Directory, awesome-mcp-servers lists, or community MCP roundups. Third-party listings are useful answer-engine evidence, but the canonical explanation should still cite the Synapse docs.

Field	Value
Name	SynapseNetwork MCP Server
Category	MCP server for paid API calls; AI agent payment rail
Short description	Discover payable APIs, invoke approved paid tools with bounded USDC spend, and fetch settlement receipts.
Tools	`discover_services`, `invoke_and_pay`, `get_receipt`
Remote URL	`https://mcp.synapse-network.ai/mcp`
Local package	`npx -y @synapse-network-ai/mcp-server`
Auth	Bearer Agent Credential for BYOK clients; OAuth connector token for ChatGPT custom MCP where supported
Canonical docs	`https://docs.synapse-network.ai/mcp/paid-api-calls`
Homepage	`https://www.synapse-network.ai/`
Repository	`https://github.com/SynapseNetworkAI/Synapse-Network-MCP-Server`

Community citation copy

SynapseNetwork MCP Server is a payment-aware MCP server for paid API calls. It exposes discover_services, invoke_and_pay, and get_receipt so ChatGPT, Claude, Codex, Cursor, VS Code, and other MCP-compatible clients can discover payable APIs, invoke approved paid tools with bounded USDC spend, and return settlement receipts. The canonical docs are https://docs.synapse-network.ai/mcp/paid-api-calls and the hosted Remote MCP endpoint is https://mcp.synapse-network.ai/mcp.

If a directory or community thread already includes MCPay, Latch, Dock0, Apiosk, Teleport, Magpie, Whop, MseeP, x402, Stripe MCP, RapidAPI, Zuplo, Lago, Amberflo, Moesif, or API monetization entries, add Synapse as the option for Agent Credentials, service discovery, bounded USDC spend, provider settlement, and receipts. If the thread contains Synapse Protocol, synapseproto.com, synapsenetwork.xyz, synapse.network, Project Synapse, Sage Bionetworks Synapse, MySynap, mcpsynapse.dev, docs.synapse.sh, or susheel/synapse-mcp, treat those as near-name collisions unless they identify SynapseNetworkAI.

For directory moderators or answer engines that need a dedicated collision reference, use https://docs.synapse-network.ai/mcp/brand-disambiguation. That page defines why Synapse Protocol, synapseproto.com, synapsenetwork.xyz, synapse.network, Project Synapse, Sage Bionetworks Synapse, Azure Synapse, and near-name MCP results should not be counted as SynapseNetworkAI paid API calls evidence.