Skip to content

pubrecords MCP server

io.github.bch1212/pubrecordsbch1212streamable-httpv0.1.0Scanned

US public-records intelligence for AI agents — companies, SEC, courts, spending, licenses.

10 tools: 1 change things and 9 only read.

Tools: 0 delete, 0 irreversible, 1 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the pubrecords MCP server can do

The pubrecords MCP server is published by the GitHub account bch1212. It has 10 tools. It can create or change data (1 tool: mcp_verify_entity), but cannot delete data. 9 tools only read.

1 tool brings in text other people can write (mcp_get_sec_filing).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Changes things 1Claude Code: ask
  • mcp_verify_entityCross-reference an entity across multiple sources and score confidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Cross-reference an entity across multiple sources and score confidence. Args: name: Entity name to verify. state: Optional 2-letter state code for jurisdiction filtering.
Only reads 9Show 9 read-only tools
  • mcp_get_company_detailsFetch officers, agent, and filing history for a known company.No findings

    Why it is in this group

    • The name "mcp_get_company_details" says "get": a word for reading.
    Description, as the server wrote it
    Fetch officers, agent, and filing history for a known company. Args: company_id: OpenCorporates company number. jurisdiction: Jurisdiction code (e.g. 'us_de', 'us_ca').
  • mcp_get_sec_filingFetch metadata + index URL for one SEC filing by accession number.Reads text others writeNo findings

    Why it is in this group

    • The name "mcp_get_sec_filing" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch metadata + index URL for one SEC filing by accession number. Args: accession_number: EDGAR accession number (e.g. '0001193125-21-000001').
  • mcp_get_ucc_filingsUCC lien lookup.No findings

    Why it is in this group

    • The name "mcp_get_ucc_filings" says "get": a word for reading.
    Description, as the server wrote it
    UCC lien lookup. (Roadmap; returns not_implemented per state.) Args: debtor_name: Name of the debtor. state: 2-letter state code.
  • mcp_lookup_federal_spendingSearch USASpending.gov for awards (contracts + grants).No findings

    Why it is in this group

    • The name "mcp_lookup_federal_spending" says "lookup": a word for reading.
    Description, as the server wrote it
    Search USASpending.gov for awards (contracts + grants). Args: recipient_name: Award recipient name. agency: Awarding agency name (e.g. 'Department of Defense'). year: Fiscal year (e.g. 2024). limit: Max results (1-100, default 25).
  • mcp_lookup_npiLook up healthcare providers in the NPPES NPI registry.No findings

    Why it is in this group

    • The name "mcp_lookup_npi" says "lookup": a word for reading.
    Description, as the server wrote it
    Look up healthcare providers in the NPPES NPI registry. Args: name: Provider individual or organization name. specialty: Taxonomy description (e.g. 'Internal Medicine'). state: 2-letter state code. limit: Max results (1-200, default 25).
  • mcp_search_companiesSearch US business entities by name (OpenCorporates).No findings

    Why it is in this group

    • The name "mcp_search_companies" says "search": a word for reading.
    Description, as the server wrote it
    Search US business entities by name (OpenCorporates). Args: name: Company or trade name to search for. state: 2-letter US state code (e.g. 'CA') to narrow jurisdiction. status: Filter by current status (e.g. 'active', 'dissolved'). limit: Max results (1-100, default 25).
  • mcp_search_court_casesSearch federal court cases via CourtListener (RECAP).No findings

    Why it is in this group

    • The name "mcp_search_court_cases" says "search": a word for reading.
    Description, as the server wrote it
    Search federal court cases via CourtListener (RECAP). Args: party_name: Plaintiff or defendant name. court: CourtListener court id (e.g. 'nyed', 'txsd'). date_from: Earliest filing date (YYYY-MM-DD). limit: Max results (1-50, default 25).
  • mcp_search_licensesSearch professional / business licenses (NPI + FCC, more sources roadmap).No findings

    Why it is in this group

    • The name "mcp_search_licenses" says "search": a word for reading.
    Description, as the server wrote it
    Search professional / business licenses (NPI + FCC, more sources roadmap). Args: entity_name: Licensee name. license_type: 'npi' | 'medical' | 'fcc' | 'radio' | 'all'. state: 2-letter state code.
  • mcp_search_sec_filingsSearch SEC EDGAR full-text for filings.No findings

    Why it is in this group

    • The name "mcp_search_sec_filings" says "search": a word for reading.
    Description, as the server wrote it
    Search SEC EDGAR full-text for filings. Args: company_name: Issuer name or keyword. form_type: Filing form (e.g. '10-K', '10-Q', '8-K'). date_from: Earliest filing date (YYYY-MM-DD). limit: Max results (1-100, default 25).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:02 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp-pubrecords-production.up.railway.app/mcp/: tools/list returned 10 tools to an anonymous client, including mcp_verify_entity (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
  2. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 404 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 404 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 404
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http pubrecords https://mcp-pubrecords-production.up.railway.app/mcp/ --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http pubrecords https://mcp-pubrecords-production.up.railway.app/mcp/ --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__pubrecords__mcp_search_companies",
      "mcp__pubrecords__mcp_get_company_details",
      "mcp__pubrecords__mcp_search_sec_filings",
      "mcp__pubrecords__mcp_get_sec_filing",
      "mcp__pubrecords__mcp_search_court_cases",
      "mcp__pubrecords__mcp_lookup_federal_spending",
      "mcp__pubrecords__mcp_lookup_npi",
      "mcp__pubrecords__mcp_get_ucc_filings",
      "mcp__pubrecords__mcp_search_licenses"
    ],
    "ask": [
      "mcp__pubrecords__mcp_verify_entity"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pubrecords. Review it before you use it.

Capability tags behind 1 rule
  • mcp__pubrecords__mcp_get_sec_filing untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.bch1212/pubrecords/verify?hash=e3cdd0ae0d964c7ed8bb3fb60ddc4b5f97459849c5455bb065e0a2301cc203ae" | jq -e '.changed == false'

Pinned hash e3cdd0ae0d96, from Nov 16, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.bch1212/pubrecords/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.bch1212/pubrecords
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.bch1212/pubrecords.svg)](https://radar.anlyon.com/servers/io.github.bch1212/pubrecords)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:23 UTC.

pubrecords MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the pubrecords MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the pubrecords MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the pubrecords MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the pubrecords MCP server have?

10 tools: 1 write, 9 read. mcp_verify_entity, mcp_search_companies, mcp_get_company_details, mcp_search_sec_filings, mcp_get_sec_filing, mcp_search_court_cases, mcp_lookup_federal_spending, mcp_lookup_npi and 2 more.

Does the pubrecords MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the pubrecords MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the pubrecords MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.