Mcp Gateway

io.github.Davedat-110105Published by GitHub account Davedat-110105v0.1.0Updated Oct 24, 2026

Curated gateway to snapshot-versioned Canadian public data services with source provenance.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

A remote MCP gateway that gives an assistant access to curated, snapshot-versioned Canadian public data services with source provenance.

What you can do
It acts as a single remote endpoint that fronts curated Canadian public data services. According to its description, the data is snapshot-versioned and carries source provenance, so responses can be traced back to their origin. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
When to use it
Worth considering when an assistant needs Canadian public data and you want a single hosted endpoint rather than wiring up each source yourself. The snapshot versioning and provenance may suit work where you need to know which release of the data you are looking at.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, environment variables, or headers are declared. The manifest declares no authentication, so no account or API key appears to be needed.
Before you install
The manifest declares no authentication and no credentials, so anything sent to this endpoint is not gated by a key you control. No tools are listed, so what the server can read or change is undocumented; verify the actual tool list before relying on it. Data is fetched from a third-party hosted service, so requests leave your machine.

Installation

In SourceWeft

  1. Open Mcp Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Davedat-110105%2Fmcp-gateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "gateway": {
      "type": "http",
      "url": "https://gateway-production-c71a.up.railway.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.