MCP

MCP server for U.S. business registry data

Recordwire runs a Model Context Protocol server so an agent can look up real companies instead of guessing at them. It exposes five tools over the official business registries of seven states: search companies, fetch one company, read its change history, search the change feed, and check how fresh each state's data is. Streamable HTTP, one bearer key, no scraping inside the agent.

Connect

Claude Code, one line:

Claude Code

claude mcp add registry --transport http https://api.recordwirehq.com/mcp \
  --header "Authorization: Bearer $KEY"

Cursor, or any client that takes a JSON config for a Streamable HTTP server:

mcp.json

{
  "mcpServers": {
    "recordwire": {
      "url": "https://api.recordwirehq.com/mcp",
      "headers": { "Authorization": "Bearer rk_live_..." }
    }
  }
}

The key is the same rk_live_... key you use for REST, with the same state restrictions. One key, both doors; there is nothing MCP-specific to provision.

Tools

search_businesses: Find companies by state, name prefix, entity type, status, or formation-date range. “Which LLCs were formed in Virginia last week?”
get_business: Fetch one company's full normalized record by ID, including agent, addresses, and officers. “Pull the registry record for US-FL:L21000318842.”
get_business_events: Read the change history of a single company, newest first. “Has this company changed its registered agent since 2024?”
search_events: Query the change feed by type, state, and date, including everything observed since a date. “List Florida companies that dissolved in the last month.”
list_sources: Per state: the last file date, the last completed run, and the entity count, so an agent can say how fresh its answer is. “How current is your Connecticut data?”

Questions

Does the MCP server need OAuth?

No. Authentication is a bearer key in the Authorization header, the same rk_live_... key the REST API uses. There is no OAuth flow, no consent screen, and no token refresh to handle. Issue a key from your dashboard, put it in your client config, and the server is connected.

Which states can an agent query?

Florida, New York, Colorado, Pennsylvania, Virginia, Connecticut, and Oregon, with counts, cadence, and file dates on the coverage pages. A key restricted to certain states returns 403 for the others, so an agent cannot silently answer outside its subscription. Full coverage keys reach every state we add.

Can an agent subscribe to changes?

Yes, through REST. Poll /v1/events?observed_since= for everything learned since your last check, or use change subscriptions with signed webhooks on the Full coverage plan. MCP itself is request and response, so an agent reads the feed rather than being pushed to. The payloads are on change events.

Every parameter these tools accept is documented in the docs.