# 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.

- Trust score: 79/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `registryverify.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify.md), [page](https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify)

## Channel facts

- Endpoint: `https://registryverify.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 12 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-registryverify-florida-sunbiz-business-kyb 'https://registryverify.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-registryverify-florida-sunbiz-business-kyb": {
      "url": "https://registryverify.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-registryverify-florida-sunbiz-business-kyb": {
      "type": "http",
      "url": "https://registryverify.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-registryverify-florida-sunbiz-business-kyb]
url = "https://registryverify.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-registryverify-florida-sunbiz-business-kyb": {
      "type": "remote",
      "url": "https://registryverify.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-registryverify-florida-sunbiz-business-kyb --url 'https://registryverify.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-registryverify-florida-sunbiz-business-kyb:
    url: "https://registryverify.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-registryverify-florida-sunbiz-business-kyb": {
      "Transport": "http",
      "Url": "https://registryverify.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-registryverify-florida-sunbiz-business-kyb -t streamable-http -u 'https://registryverify.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-registryverify-florida-sunbiz-business-kyb": {
      "type": "http",
      "url": "https://registryverify.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 79, +4)

- [security regression] Stability: 0.30 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “verify_california_business” was removed
- [security regression] Tool “verify_florida_business” was removed
- [security regression] Tool “verify_new_york_business” was removed
- [security improvement] Authorization: partial → pass
- [security] Tool “verify_us_business” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 1498 → 355
- [cosmetic] “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)

### 2026-11-18 (score 75, 0)

- [security] 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
- [functional regression] Schema quality: 1152 → 1498
- [functional] New tool “verify_us_business”

### 2026-11-17 (score 75, +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.

### 2026-11-14 (score 74, +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.

### 2026-11-13 (score 73, −7)

- [security regression] Authorization: pass → partial
- [security] Tool “verify_florida_business” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 388 → 1152
- [functional] New tool “verify_california_business”
- [functional] New tool “verify_new_york_business”

### 2026-11-12 (score 80, 0)

- [security] Tool “verify_florida_business” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 292 → 388

### 2026-11-10 (score 80, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-09 (score 79)

First indexed and scored.

## MCP tools (1)

### `verify_us_business` (~355 tokens)

Verify a US business (Florida, New York, California and Colorado records)

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.

Input parameters:

- `business_name` (string, required): 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.

Output parameters:

- `found_in` (array)
- `not_checked_in` (array)
- `not_found_in` (array)
- `price_note` (string)
- `query` (object)
- `states` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 80
- 2026-11-11: 80
- 2026-11-10: 80
- 2026-11-09: 79

## Common questions

### 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.

## Links

- Remote endpoint: https://registryverify.com/mcp
- Repository: https://github.com/ai-interact/registry-verify-agent-skill
- Website: https://registryverify.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify.json
- HTML version of this page: https://verifymcp.io/servers/com-registryverify-florida-sunbiz-business-kyb/registryverify
