Router
MCP Server Router provides a proxy for connecting to remote MCP servers, enabling clients like Claude Desktop to access tools hosted on external servers. Developed by chatmcp, this implementation creates a bridge between local MCP clients and remote servers by routing requests through a central service at router.mcp.so. The server authenticates with a server key obtained from MCP.so and handles tool listing and execution requests, forwarding them to the appropriate remote endpoints. Built with TypeScript using the Model Context Protocol SDK, it communicates over stdio and is particularly valuable for users who want to leverage remotely hosted tools without running their own MCP server infrastructure.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- other
- Source
- PulseMCP
- Repository
- github.com/chatmcp/mcp-server-router
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Router from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.