Skip to content

Recordwire MCP server

io.github.BrianVia/recordwireBrianViastreamable-httpv1.0.0Scanned

U.S. business-registry data and change events from official state sources, for agents.

9 tools: 1 can delete or cancel things, 2 change things and 6 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel 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 Recordwire MCP server can do

The Recordwire MCP server is published by the GitHub account BrianVia. It has 9 tools. It can delete or cancel things (1 tool: delete_subscription) and create or change data (2 tools: create_subscription and enable_subscription). 6 tools only read.

1 tool reads private data (list_subscriptions); 1 tool can send data out of your system (create_subscription).

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, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.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.

9 tools

Deletes or cancels 1Claude Code: deny
  • delete_subscriptionRevoke your subscription.No findings

    Why it is in this group

    • The name "delete_subscription" says "delete": a word for removing or ending something.
    Description, as the server wrote it
    Revoke your subscription.
Changes things 2Claude Code: ask
  • create_subscriptionSubscribe an HTTPS endpoint to new registry changes.Can send data outNo findings

    Why it is in this group

    • The name "create_subscription" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Subscribe an HTTPS endpoint to new registry changes. Save the returned secret; it is shown once.
  • enable_subscriptionTurn a disabled subscription back on.No findings

    Why it is in this group

    • The name "enable_subscription" says "enable": a word for a change.
    Description, as the server wrote it
    Turn a disabled subscription back on. Delivery resumes from where it stopped, so no events are skipped.
Only reads 6Show 6 read-only tools
  • get_businessReturns one business by an ID like US-VA:11406679, with dates in YYYY-MM-DD format.No findings

    Why it is in this group

    • The name "get_business" says "get": a word for reading.
    Description, as the server wrote it
    Returns one business by an ID like US-VA:11406679, with dates in YYYY-MM-DD format.
  • get_business_eventsReturns events for a business ID like US-VA:11406679; dates use YYYY-MM-DD and next_cursor pages through more results.No findings

    Why it is in this group

    • The name "get_business_events" says "get": a word for reading.
    Description, as the server wrote it
    Returns events for a business ID like US-VA:11406679; dates use YYYY-MM-DD and next_cursor pages through more results.
  • list_sourcesReturns available registry sources and their latest verified YYYY-MM-DD dates.No findings

    Why it is in this group

    • The name "list_sources" says "list": a word for reading.
    Description, as the server wrote it
    Returns available registry sources and their latest verified YYYY-MM-DD dates.
  • list_subscriptionsList your subscriptions without signing secrets.Reads private dataNo findings

    Why it is in this group

    • The name "list_subscriptions" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "secret": it reads secrets.
    Description, as the server wrote it
    List your subscriptions without signing secrets.
  • search_businessesReturns matching businesses; IDs look like US-VA:11406679, dates use YYYY-MM-DD, and next_cursor pages through more results.No findings

    Why it is in this group

    • The name "search_businesses" says "search": a word for reading.
    Description, as the server wrote it
    Returns matching businesses; IDs look like US-VA:11406679, dates use YYYY-MM-DD, and next_cursor pages through more results.
  • search_eventsReturns business.created, business.name_changed, business.status_changed, business.address_changed, business.agent_changed, or business.officers_changed events, newest first; type …No findings

    Why it is in this group

    • The name "search_events" says "search": a word for reading.
    Description, as the server wrote it
    Returns business.created, business.name_changed, business.status_changed, business.address_changed, business.agent_changed, or business.officers_changed events, newest first; type takes one or more of them, comma-separated; dates use YYYY-MM-DD, business IDs look like US-VA:11406679, and next_cursor pages through more results. To poll for new events, pass after=<id of the last event you have>: results are then oldest first, and you call again with the last id while pages are full.

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 untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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, 18:57 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
3
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
  • HighThe whole server

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

    Matched text

    https://api.recordwirehq.com/mcp: tools/list returned 9 tools to an anonymous client, including delete_subscription (destructive), create_subscription (write), enable_subscription (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 2 to 3

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. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  3. Tools1 changed.~1 changedView diff

Install

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

claude mcp add --transport http recordwire https://api.recordwirehq.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http recordwire https://api.recordwirehq.com/mcp --header 'Authorization: <your-authorization>'

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__recordwire__search_businesses",
      "mcp__recordwire__get_business",
      "mcp__recordwire__get_business_events",
      "mcp__recordwire__search_events",
      "mcp__recordwire__list_sources",
      "mcp__recordwire__list_subscriptions"
    ],
    "ask": [
      "mcp__recordwire__create_subscription",
      "mcp__recordwire__enable_subscription"
    ],
    "deny": [
      "mcp__recordwire__delete_subscription"
    ]
  }
}

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 recordwire. Review it before you use it.

Capability tags behind 2 rules
  • mcp__recordwire__create_subscription outbound
  • mcp__recordwire__list_subscriptions private-data

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.BrianVia/recordwire/verify?hash=3878e548cd82fd6957a78714aa0cd300ededadb426d36dd8ae4d68197e911648" | jq -e '.changed == false'

Pinned hash 3878e548cd82, from Nov 15, 2026, 18: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.BrianVia/recordwire/changes.xml

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

Badge

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

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

Recordwire MCP server: questions and answers

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

Is the Recordwire MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 3 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 Recordwire MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: delete_subscription.

Can the Recordwire 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 Recordwire MCP server have?

9 tools: 1 destructive, 2 write, 6 read. delete_subscription, create_subscription, enable_subscription, search_businesses, get_business, get_business_events, search_events, list_sources and 1 more.

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

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

Does the Recordwire MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_subscription.

Has the Recordwire MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.