Recordwire
REMOTE · API.RECORDWIREHQ.COM
U.S. business-registry data and change events from official state sources, for agents.
Available components
Last scanned (7 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 18 Oct 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 425 tokens (~53/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_subscription" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 53
First indexed and scored.
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 18 Oct 2026 · Probed https://api.recordwirehq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recordwirehq.com | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3ade44e1d7100dee0ec7e58cd3b87128 |
| SANs: recordwirehq.com, api.recordwirehq.com, *.api.recordwirehq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.recordwirehq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| recordwirehq.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.recordwirehq.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.recordwirehq.com/mcp | Inconclusive | 406 |
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 →
create_subscription ~64
Subscribe an HTTPS endpoint to new registry changes. Save the returned secret; it is shown once.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_ids | array | – | – |
| event_types | array | – | – |
| jurisdictions | array | – | – |
| name | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
delete_subscription ~20
Revoke your subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_business ~38
Returns one business by an ID like US-VA:11406679, with dates in YYYY-MM-DD format.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_business_events ~58
Returns events for a business ID like US-VA:11406679; dates use YYYY-MM-DD and next_cursor pages through more results.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_sources ~21
Returns available registry sources and their latest verified YYYY-MM-DD dates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_subscriptions ~16
List your subscriptions without signing secrets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_businesses ~97
Returns matching businesses; IDs look like US-VA:11406679, dates use YYYY-MM-DD, and next_cursor pages through more results.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| entity_type | string | – | – |
| formed_after | string | – | – |
| formed_before | string | – | – |
| jurisdiction | string | – | – |
| limit | integer | – | – |
| q | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
search_events ~111
Returns business.created, business.name_changed, business.status_changed, business.address_changed, business.agent_changed, or business.officers_changed events; dates use YYYY-MM-DD, business IDs look like US-VA:11406679, and next_cursor pages through more results.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| jurisdiction | string | – | – |
| limit | integer | – | – |
| observed_since | string | – | – |
| since | string | – | – |
| type | string | – | – |
| until | string | – | – |
No output schema declared.
No examples provided.
How do I install the Recordwire MCP server?
Recordwire is a hosted endpoint at https://api.recordwirehq.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.recordwirehq.com
claude mcp add --transport http brianvia-recordwire 'https://api.recordwirehq.com/mcp'
What is the Recordwire MCP server?
Recordwire is an MCP server listed in the public MCP registry as io.github.BrianVia/recordwire. U.S. business-registry data and change events from official state sources, for agents. This page covers its hosted endpoint (https://api.recordwirehq.com/mcp).
Is the Recordwire MCP server safe to use?
Recordwire scores 54 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 Recordwire MCP server expose?
Recordwire exposes 8 tools: search_businesses, get_business, get_business_events, search_events, list_sources, and 3 more. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.
Does the Recordwire MCP server require authentication?
No. We connected to Recordwire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Recordwire MCP server still maintained?
Recordwire is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.