Developer · Remote MCP server
MCP Gateway
Curated gateway to snapshot-versioned Canadian public data services with source provenance.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Davedat-110105/mcp-gateway- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- Davedat-110105 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Davedat-110105) · how
- Repository
- github.com/Davedat-110105/mcp (folder services/gateway)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://gateway-production-c71a.up.railway.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect MCP Gateway
MCP Gateway is a remote MCP server: there is nothing to install. Its endpoint is https://gateway-production-c71a.up.railway.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| MCP Failure LabA chaos-engineering and resilience-testing toolkit for Model Context Protocol servers. | Local · stdio |
| MCP FilesystemAdvanced filesystem operations with strict security boundaries for AI agents. | Local · stdio |
| MCP Firefly IiiSecurity-first, self-hosted MCP server for Firefly III - 152 operations behind 5 scoped tools. | Local · stdio |
| MCP FunnelMCP proxy that aggregates multiple servers with tool filtering and customization. | Local · stdio |
| MCP GatewayUniversal MCP gateway with Meta-MCP discovery, routing, and REST API capabilities. | Local · stdio |
| MCP GatewayMulti-tenant MCP platform with OAuth 2.1, Entra SSO, RBAC and audit logging. | Remote · SSELive check: ✗ no handshake |
| MCP GatewayAggregates tools from multiple MCP servers with unified BM25/regex search and deferred loading. | Local · stdio |
| MCP GatewayIdentity, authorization, audit trails, and revocable permissions for AI agents accessing MCP tools. | Remote · HTTPLive check: sign-in required |