Remote MCP: MCP server, CLI and agent surfaces
Yes: Remote MCP runs a public MCP server at mcp.remote-mcp.com that listed 1 tool to a client with no credentials on 4 November 2026. Examples: ListRemoteMCPServers. It speaks streamable-http, protocol 2025-11-25. Open servers are readable by any agent; writes still depend on each tool.
Fact sheet
| Company | Remote MCP |
|---|---|
| Domain | remote-mcp.com |
| Category | Infrastructure (assigned by this directory from the registry description) |
| MCP server | Verified (No authentication) |
| Ora score | none: Ora returned no cached score for remote-mcp.com when asked on 5 November 2026 |
| Company found through | the awesome-remote-mcp-servers list; the official MCP Registry |
| Last verified | 4 November 2026 |
MCP server
| Endpoint | https://mcp.remote-mcp.com |
|---|---|
| How it was found | listed in the awesome-remote-mcp-servers list; the official MCP Registry |
| Transport | streamable-http |
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server | Remote MCP Server Directory 1.0.1 |
| Capabilities | tools |
| Tools | 1 |
| Resources | 0 |
| Prompts | 0 |
| Connected | 4 November 2026, 20:04 UTC |
| Handshake time | 145 ms over 1 attempt |
Tools listed
1 tool
- ListRemoteMCPServers
Connector log
2 connections on 4 November 2026, read-only methods only
- 19:59:09Z https://mcp.remote-mcp.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 629 ms
- 20:04:14Z https://mcp.remote-mcp.com sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 145 ms
Authentication
| Auth type | No authentication |
|---|---|
| Auth as listed by a registry | Open (a claim, not checked by connecting) |
The sign-in route, step by step
- Send the handshake to
https://mcp.remote-mcp.comover streamable-http. Servers on the 2026-07-28 revision answerserver/discover; older servers answerinitialize. - Send
tools/list, thenresources/listandprompts/listif the capabilities name them. - Send no token. The connector sent none and the server answered, so any MCP client can read this list.
- Calling a tool is a separate step this directory never takes.
See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.
CLI
No CLI is on record for Remote MCP. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.
Other agent surfaces
| Surface | Result |
|---|---|
| OpenAPI file | No OpenAPI file at the root paths checked. |
| WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. |
| MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. |
| A2A agent card | Not checked: the domain is not in the shared crawl for this edition. |
| A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. |
| agents.json | Not checked: the domain is not in the shared crawl for this edition. |
| OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. |
| NLWeb endpoint | Not checked in this edition. |
Registry listings
| Registry | Listed |
|---|---|
| Official MCP Registry | Yes: com.remote-mcp/registry-mcp |
| GitHub MCP Registry | No |
| awesome-remote-mcp-servers | Yes |
| Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. |
| Glama | Not checked: Glama's API needs a key and attribution terms. |