mcp-data-gateway
Registry code: ad1f40f7e91ecc97
Live U.S. government data, fetched from the agency at call time. Only U.S.
federal, state and local sources; nothing international. Never answer a U.S.
- endpoint
- https://data.mcp.usafacts.org/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is mcp-data-gateway live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is mcp-data-gateway free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does mcp-data-gateway have?
- 4 tools: call_source_tool, get_source_tools, get_source, list_sources.
- Is mcp-data-gateway safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 4 tools
- degraded → live
- unknown → live
- used for
- find us government data sources
- get source playbook and tools
- call a government data source tool
- fetch live federal or state statistics
- takes → gives
- text → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_sources reads open 1h ago
List available data sources and their descriptions.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linescall_source_tool reads unknown 1h ago
Call a tool on a data source. Requires a source_id and tool_name previously returned by get_source_tools(), with an arguments object matching the schema it gave for that tool. On success, the response carries `_citation` -- use it for attribution rather than reconstructing one. Read-only: every source in this gateway (U.S. government statistics APIs, legislative and spending data, .gov web search -- see list_sources() for the full, current list) only retrieves data, even where the upstream requires POST for a request body.
{ "type": "object", "required": [ "source_id", "tool_name" ], "properties": { "arguments": { "anyOf": [ { "type": "object", "additionalProperties": true }, { "type": "null" } ], "default": null, "description": "Arguments for the source tool, matching the schema from\nget_source_tools(). Omit or null if the tool takes none." }, "source_id": { "type": "string", "description": "Exact source identifier returned by list_sources() or\nget_source(). Do not invent one." }, "tool_name": { "type": "string", "description": "Exact tool name from that source's get_source() tool\nindex, with its schema fetched via get_source_tools(). Do not\ninvent one." } }, "additionalProperties": false }arguments 31 linesget_source_tools reads unknown 7h ago
Get the full description and argument schema of named source tools. call_source_tool() requires a schema previously returned here for the source_id/tool_name pair it's given. Name every tool you may call in one request; call this once per source, after get_source() and before any call_source_tool.
{ "type": "object", "required": [ "source_id", "tools" ], "properties": { "tools": { "type": "array", "items": { "type": "string" }, "minItems": 1, "description": "Exact tool names from this source's get_source() tool index.\nAt least one." }, "source_id": { "type": "string", "description": "Data source identifier from list_sources(). Do not\ninvent one." } }, "additionalProperties": false }arguments 22 linesget_source reads unknown 1h ago
Get a source's playbook, methodology, and tool index. The playbook names the tool for each question shape and defines the source's concepts. The tool index carries names, summaries and groups only, not schemas; get_source_tools() returns the schema for named tools from that index.
{ "type": "object", "required": [ "source_id" ], "properties": { "source_id": { "type": "string", "description": "Data source identifier from list_sources() (e.g. 'bls',\n'fred'). Do not invent one." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idad1f40f7e91ecc97.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ad1f40f7e91ecc97/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ad1f40f7e91ecc97?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.