Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pushbuild Data APIs

REMOTE · API.PUSHBUILD.COM

Search and call 422 official public-data APIs: elections, courts, permits, SEC filings.

68 Trust /100

Last scanned (1 hour ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 357 tokens (~119/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 2 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 0
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 1.0 ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “call_api” rewrote its description, which is the text the model reads security
    • Schema quality: 90 → 119 ▼ functional
    • “call_api” made “params” required, so existing callers break ▼ functional
    • “call_api” reworded the description of “params” cosmetic
  • 3 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://api.pushbuild.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.pushbuild.com CN=YE2,O=Let's Encrypt,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA384 59dae6f2a7ebf6e7056f4f399a36c7999cd
SANs: api.pushbuild.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.pushbuild.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
pushbuild.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-frame-options ALLOWALL

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.pushbuild.com/mcp Verified 200
http (plaintext) http://api.pushbuild.com/mcp HTTPS enforced 301 https://api.pushbuild.com/mcp
MCP tools · 3 exposed · ~226 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call_api ~112

Run one API with parameters from describe_api. Returns JSON records (default 25; set maxItems up to 500). Billed per record from the account's free monthly allowance, then credit; asks you to sign in (free) the first time. Data via Pushbuild (pushbuild.com/contact).

NameTypeReqDescription
apistringyesAPI id.
paramsobjectyesInput parameters for that API, as describe_api lists them, e.g. {"postcode": "SW1A 1AA"}.

No output schema declared.

No examples provided.

describe_api ~44

Input parameters (JSON Schema), coverage and price for one API id from search_apis. Free.

NameTypeReqDescription
apistringyesAPI id, e.g. restaurant-inspections.

No output schema declared.

No examples provided.

search_apis ~70

Find Pushbuild data APIs by keyword (e.g. 'campaign contributions texas', 'restaurant inspections', 'sec 13f'). Returns api ids, what each covers and price per record. Free.

NameTypeReqDescription
limitinteger–Max results (default 10).
querystringyesKeywords.

No output schema declared.

No examples provided.

Install

How do I install the Pushbuild Data APIs MCP server?

Pushbuild Data APIs is a hosted endpoint at https://api.pushbuild.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.pushbuild.com

# add to Claude Code
claude mcp add --transport http com-pushbuild-data-apis 'https://api.pushbuild.com/mcp'
Common questions

What is the Pushbuild Data APIs MCP server?

Pushbuild Data APIs is an MCP server listed in the public MCP registry as com.pushbuild/data-apis. Search and call 422 official public-data APIs: elections, courts, permits, SEC filings. This page covers its hosted endpoint (https://api.pushbuild.com/mcp).

Is the Pushbuild Data APIs MCP server safe to use?

Pushbuild Data APIs scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Pushbuild Data APIs MCP server expose?

Pushbuild Data APIs exposes 3 tools: search_apis, describe_api, call_api. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.

Does the Pushbuild Data APIs MCP server require authentication?

No. We connected to Pushbuild Data APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pushbuild Data APIs MCP server still maintained?

Pushbuild Data APIs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.