Public Query MCP Server

by amalgament Your server? Claim it

answering

Public Query is answering right now. Last checked 14 min ago.

Agent-native MCP over US public + government records, entity- and parcel-keyed.

Uptime history 12 days of history

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

135 ms

Response time

average over 24h

API key or OAuth

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Public Query every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add public-query --transport http https://api.amalgament.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "public-query": {
      "url": "https://api.amalgament.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.public-query]
url = "https://api.amalgament.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "public-query": {
      "url": "https://api.amalgament.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "public-query": {
      "url": "https://api.amalgament.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://api.amalgament.com/mcp	streamable-http	needs key	137 ms	14 min ago

Alternatives to Public Query

same job, measured the same way

Hilma

by pipeworx-io

Hilma MCP — Finnish government public procurement notices (keyed).

34 tools answering

saagarpatel.dev Portfolio

by saagpatel

Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.

50 installs/wk 8 tools answering

Govinfo

by pipeworx-io

GovInfo.gov MCP — full text of US government publications

36 tools answering

Statey

by statey

An agent-native database over MCP: shared, validated, structured records in every AI chat.

answering

Paraguay Dncp

by pipeworx-io

Paraguay DNCP MCP — Paraguay government procurement / public contracts (keyless).

33 tools answering

Tender MCP

by ojaskord

Government tender search for AI agents. UK, EU and US procurement opportunities.

169 installs/wk 2 tools answering

Udbud Dk

by pipeworx-io

Udbud.dk MCP — Danish government public procurement notices (keyless).

34 tools answering

HODLXXI Read-Only

by hodlxxi

Public read-only MCP server for HODLXXI agent identity, trust, receipts, and verification.

26 tools answering

Public Query — questions

Answers built from our own checks of this server.

Why is there no tool list for Public Query?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Public Query working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 135 ms. The bar chart above shows every period we have measured.

How do I connect Public Query?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.

Does Public Query need an API key?

Yes. Every time we knock, Public Query answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Public Query?

It answers our handshake in 135 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.