# BizVerify (remote · api.bizverify.co)

KYB for AI agents: verify business registrations from MCP clients.

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

## Components

- remote · `api.bizverify.co`: 70/100 (this document), [markdown](https://verifymcp.io/servers/co-bizverify-mcp/api.md), [page](https://verifymcp.io/servers/co-bizverify-mcp/api)

## Channel facts

- Endpoint: `https://api.bizverify.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1419 tokens (~157/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http co-bizverify-mcp https://api.bizverify.co/mcp
```

### Codex

```toml
[mcp_servers.co-bizverify-mcp]
url = "https://api.bizverify.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-bizverify-mcp": {
      "type": "remote",
      "url": "https://api.bizverify.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-bizverify-mcp --url https://api.bizverify.co/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-bizverify-mcp:
    url: "https://api.bizverify.co/mcp"
```

### Other

```json
{
  "mcpServers": {
    "co-bizverify-mcp": {
      "type": "http",
      "url": "https://api.bizverify.co/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-08-03 (score 70, +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-07-31 (score 69, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 66, +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.

### 2026-07-27 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 65)

First indexed and scored.

## MCP tools (9)

### `get_config` (~70 tokens)

Get Configuration

Returns BizVerify's public configuration as readable text: active US and international jurisdictions, per-operation credit costs, the free-tier allowance, credit packages with pricing, feature flags, and documentation/legal links. Free and requires no authentication. Call this first to discover what jurisdictions are supported and what each operation costs before verifying.

### `list_jurisdictions` (~70 tokens)

List Jurisdictions

Lists every registered jurisdiction with its code, active/inactive status, and supported capabilities — search, entity lookup, quick verification, and deep verification. Free and requires no authentication. Use it to confirm a state or country is supported and which verification tiers it offers before calling verify_business or search_entities.

### `verify_business` (~357 tokens)

Verify Business

Confirm a specific, named business in one jurisdiction — the PRIMARY tool whenever the user wants to verify, check, confirm, or look up a company's existence, status, good standing, or details (e.g. "verify Acme LLC in Delaware", "is Acme registered in FL?", "I need to verify a company in Delaware"). If the user has verification intent but has not given the exact company name, ASK them for the name and use THIS tool — do NOT fall back to search_entities. Two tiers: quick (1 credit) returns existence + status + good-standing. Deep (15 credits, or 25 with force_refresh) adds entity type, formation date, registered agent, officers, principal address, and filing history. Deep is available in a subset of jurisdictions; requesting deep where unavailable returns a quick result with a reason. Requires authentication. A completed verification deducts credits whether or not the business is found — a confirmed no-match is a result. Calls that cannot produce an answer (source unavailable or timed out) are refunded.

Input parameters:

- `entity_name` (string, required): Business entity name to verify
- `entity_type` (string): Optional entity type filter to narrow results
- `force_refresh` (boolean): Return the most current result instead of a previously stored one. Applies to the deep tier only (adds 10 credits); ignored on quick.
- `jurisdiction` (string, required): Jurisdiction code or name (e.g., "us-fl", "Florida", "FL")
- `level` (string): Verification tier: quick (1 credit, always available) or deep (15 credits, availability varies by jurisdiction)
- `webhook_url` (string): URL to receive async results. Must be a publicly reachable http(s) URL.

### `search_entities` (~179 tokens)

Search Entities

Discover candidate businesses when the exact entity is UNKNOWN — a listing/discovery tool, NOT a verification tool. Use only when the user wants to browse or list multiple companies matching a partial or fuzzy name, or does not yet know which specific entity they mean. If the user can name one specific company they want to confirm or check, use verify_business instead (ask them for the name first if needed). Costs 2 credits per jurisdiction searched and requires authentication.

Input parameters:

- `entity_type` (string): Filter by entity type
- `jurisdiction` (string): Jurisdiction code or name (omit to search all active)
- `limit` (integer): Maximum number of results to return (1-200, default 50)
- `offset` (integer): Number of results to skip for pagination (default 0)
- `query` (string, required): Business name search query

### `check_job_status` (~88 tokens)

Check Job Status

Poll a long-running (async) verification job created by verify_business. Returns the full verification result once complete, a failure reason if it failed, or a "still processing" status to poll again. Free — no credits charged — but requires authentication. Pass the job_id from the verify_business async response.

Input parameters:

- `job_id` (string, required): Job ID returned by verify_business when it runs asynchronously

### `get_entity` (~110 tokens)

Get Entity

Fetch a previously verified business entity from BizVerify's cache by its ID — returns name, jurisdiction, status, type, good-standing, formation date, registered agent, and the number of snapshots on record. Free and read-only; does NOT fetch a fresh live result (use verify_business with force_refresh for live data). Requires authentication. Pass an entity_id returned by a prior verify_business or search_entities call.

Input parameters:

- `entity_id` (string, required): Entity ID returned by a prior verify_business or search_entities result

### `get_entity_history` (~112 tokens)

Get Entity History

Returns the chronological verification snapshots recorded for an entity — each with a timestamp, name, and status — newest first, with pagination. Costs 5 credits and requires authentication. Use it to see how a company's status or details have changed over time.

Input parameters:

- `entity_id` (string, required): Entity ID to retrieve history for
- `limit` (integer): Maximum number of history snapshots to return (1-100, default 10)
- `offset` (integer): Number of snapshots to skip for pagination (default 0)

### `get_account` (~61 tokens)

Get Account

Returns your BizVerify account summary: email and verification status, plan, current credit balance, member-since date, and your active and revoked API keys. Free and read-only; requires authentication. Use it to check your remaining credit balance before running paid verifications.

### `purchase_credits` (~116 tokens)

Purchase Credits

Starts a credit purchase: creates a Stripe checkout session for the chosen package and returns a payment URL to present to the user. Does NOT charge immediately and does NOT add credits until the user completes payment — credits are then added automatically. Requires authentication. Packages: credits_100, credits_500, credits_2000, credits_10000 (see get_config for current prices).

Input parameters:

- `package_id` (string, required): Credit package to purchase: credits_100, credits_500, credits_2000, or credits_10000

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-bizverify-mcp/api#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 67
- 2026-07-29: 67
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 65

## Links

- Remote endpoint: https://api.bizverify.co/mcp
- Repository: https://github.com/BizVerify/bizverify-mcp
- Website: https://bizverify.co/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/co-bizverify-mcp/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-bizverify-mcp/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/co-bizverify-mcp/api