Registry Verify: US business registry lookup
REMOTE · REGISTRYVERIFY.COM
Look up a US business in state records: Florida, New York, California, Colorado. 0.10 USDC via x402.
Available components
Last scanned (13 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 355 tokens (~355/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 12 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +4
- Stability: 0.30 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “verify_california_business” was removed ▼ security
- Tool “verify_florida_business” was removed ▼ security
- Tool “verify_new_york_business” was removed ▼ security
- Authorization: partial → pass ▲ security
- Tool “verify_us_business” rewrote its description, which is the text the model reads security
- Schema quality: 1498 → 355 ▲ functional
- “verify_us_business” added an optional parameter “state” cosmetic
- Tool “verify_us_business” changed its title: Verify a US business (Florida, New York and California records) → Verify a US business (Florida, New York, California and Colorado records) cosmetic
- 18 Nov 26 0
- Tool “verify_california_business” rewrote its description, which is the text the model reads security
- Tool “verify_florida_business” rewrote its description, which is the text the model reads security
- Tool “verify_new_york_business” rewrote its description, which is the text the model reads security
- Schema quality: 1152 → 1498 ▼ functional
- New tool “verify_us_business” functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 −7
- Authorization: pass → partial ▼ security
- Tool “verify_florida_business” rewrote its description, which is the text the model reads security
- Schema quality: 388 → 1152 ▼ functional
- New tool “verify_california_business” functional
- New tool “verify_new_york_business” functional
- 12 Nov 26 0
- Tool “verify_florida_business” rewrote its description, which is the text the model reads security
- Schema quality: 292 → 388 ▼ functional
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 79
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 21 Nov 2026 · Probed https://registryverify.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=registryverify.com | CN=YE2,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 52dcbbea2aef660f2d3e2fe12ae55c1075c |
| SANs: registryverify.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 registryverify.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| registryverify.com. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://registryverify.com/mcp | Verified | 200 | |
| http (plaintext) | http://registryverify.com/mcp | HTTPS enforced | 301 | https://registryverify.com/mcp |
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 →
verify_us_business Verify a US business (Florida, New York, California and Colorado records) ~355
Looks up a company by name in the public company records of Florida, New York, California and Colorado. With state (FL, NY, CA or CO) it checks that state only; without it, every state, for when the state the company is registered in is not known. This tool is free: it checks the name, lists the legal names of up to 3 candidate companies in each state it checks while the hourly free preview lasts (one free check per state from a shared allowance), says in which states a candidate was found, and returns each state's pay URL for that state's full lookup, with each state's data dates. Each state's full lookup costs 0.10 USDC over x402 v2 on Base, paid at that state's pay URL, and is charged even when nothing matches. A state whose data is out of date, or could not be read or searched just now, gets no pay URL. The buyer's own x402 wallet pays; this server never receives payment, signatures or keys. A no match result is not proof that a company does not exist. Not affiliated with the Florida Department of State, the New York Department of State, the California Secretary of State or the Colorado Department of State.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | The company name to look up, such as Publix Super Markets. 2 to 200 characters. |
| max_results | integer | – | How many candidate companies each state's paid lookup returns, 1 to 5. Default 5. |
| state | string | – | Optional. The state to check: FL (Florida), NY (New York), CA (California) or CO (Colorado). The state's name works too. Leave it out to check every state. |
| Name | Type | Req | Description |
|---|---|---|---|
| found_in | array | yes | – |
| not_checked_in | array | yes | – |
| not_found_in | array | yes | – |
| price_note | string | yes | – |
| query | object | yes | – |
| states | array | yes | – |
No examples provided.
How do I install the Registry Verify: US business registry lookup MCP server?
Registry Verify: US business registry lookup is a hosted endpoint at https://registryverify.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 · registryverify.com
claude mcp add --transport http com-registryverify-florida-sunbiz-business-kyb 'https://registryverify.com/mcp'
What is the Registry Verify: US business registry lookup MCP server?
Registry Verify: US business registry lookup is an MCP server listed in the public MCP registry as com.registryverify/florida-sunbiz-business-kyb. Look up a US business in state records: Florida, New York, California, Colorado. 0.10 USDC via x402. This page covers its hosted endpoint (https://registryverify.com/mcp).
Is the Registry Verify: US business registry lookup MCP server safe to use?
Registry Verify: US business registry lookup scores 79 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 Registry Verify: US business registry lookup MCP server expose?
Registry Verify: US business registry lookup exposes 1 tool: verify_us_business. Their descriptions and schemas cost roughly 355 tokens of context every time the server is loaded.
Does the Registry Verify: US business registry lookup MCP server require authentication?
No. We connected to Registry Verify: US business registry lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Registry Verify: US business registry lookup MCP server still maintained?
Registry Verify: US business registry lookup is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Registry Verify: US business registry lookup MCP server?
VerifyMCP ran 13 checks on Registry Verify: US business registry lookup, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.