Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BizVerify

REMOTE · API.BIZVERIFY.CO · SCANNED SEP 20

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

Available components

0 this week 82 Trust /100
Trust breakdown (7 categories)

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 Security66
  • 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 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. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
Install

How do I install the BizVerify MCP server?

BizVerify is a hosted endpoint at https://api.bizverify.co/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.bizverify.co

# add to Claude Code
claude mcp add --transport http co-bizverify-mcp 'https://api.bizverify.co/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "co-bizverify-mcp": {
      "url": "https://api.bizverify.co/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "co-bizverify-mcp": {
      "type": "http",
      "url": "https://api.bizverify.co/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add co-bizverify-mcp --url 'https://api.bizverify.co/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  co-bizverify-mcp:
    url: "https://api.bizverify.co/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "co-bizverify-mcp": {
      "Transport": "http",
      "Url": "https://api.bizverify.co/mcp"
    }
  }
}
# add to Vellum
assistant mcp add co-bizverify-mcp -t streamable-http -u 'https://api.bizverify.co/mcp'
// mcp.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 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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 23 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://api.bizverify.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bizverify.co CN=WE1,O=Google Trust Services,C=US 31 Jul 2026 29 Oct 2026 ECDSA 256 ECDSA-SHA256 f6ef0e057d42d5740e2a28827c9b67b0
SANs: bizverify.co, *.bizverify.co
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 secure

Validation of api.bizverify.co. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
bizverify.co. present 2371 13 Verified
api.bizverify.co. Verified address RRset verified with the apex keys
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';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
www-authenticate Bearer resource_metadata="https://api.bizverify.co/.well-known/oauth-protected-resource"

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.bizverify.co/mcp Verified 200
http (plaintext) http://api.bizverify.co/mcp HTTPS enforced 301 https://api.bizverify.co/mcp
MCP tools · 9 exposed · ~1,163 tokens

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 →

Tool Tokens
check_job_status ~88

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.

NameTypeReqDescription
job_idstringyesJob ID returned by verify_business when it runs asynchronously

No output schema declared.

No examples provided.

get_account ~61

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_config ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_entity ~110

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.

NameTypeReqDescription
entity_idstringyesEntity ID returned by a prior verify_business or search_entities result

No output schema declared.

No examples provided.

get_entity_history ~112

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.

NameTypeReqDescription
entity_idstringyesEntity ID to retrieve history for
limitintegerMaximum number of history snapshots to return (1-100, default 10)
offsetintegerNumber of snapshots to skip for pagination (default 0)

No output schema declared.

No examples provided.

list_jurisdictions ~70

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

purchase_credits ~116

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

NameTypeReqDescription
package_idstringyesCredit package to purchase: credits_100, credits_500, credits_2000, or credits_10000

No output schema declared.

No examples provided.

search_entities ~179

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.

NameTypeReqDescription
entity_typestringFilter by entity type
jurisdictionstringJurisdiction code or name (omit to search all active)
limitintegerMaximum number of results to return (1-200, default 50)
offsetintegerNumber of results to skip for pagination (default 0)
querystringyesBusiness name search query

No output schema declared.

No examples provided.

verify_business ~357

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.

NameTypeReqDescription
entity_namestringyesBusiness entity name to verify
entity_typestringOptional entity type filter to narrow results
force_refreshbooleanReturn the most current result instead of a previously stored one. Applies to the deep tier only (adds 10 credits); ignored on quick.
jurisdictionstringyesJurisdiction code or name (e.g., "us-fl", "Florida", "FL")
levelstringVerification tier: quick (1 credit, always available) or deep (15 credits, availability varies by jurisdiction)
webhook_urlstringURL to receive async results. Must be a publicly reachable http(s) URL.

No output schema declared.

No examples provided.

Common questions

What is the BizVerify MCP server?

BizVerify is an MCP server listed in the public MCP registry as co.bizverify/mcp. KYB for AI agents: verify business registrations from MCP clients. This page covers its hosted endpoint (https://api.bizverify.co/mcp).

Is the BizVerify MCP server safe to use?

BizVerify scores 82 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 BizVerify MCP server expose?

BizVerify exposes 9 tools: get_config, list_jurisdictions, verify_business, search_entities, check_job_status, and 4 more. Their descriptions and schemas cost roughly 1,163 tokens of context every time the server is loaded.

Does the BizVerify MCP server require authentication?

No. We connected to BizVerify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BizVerify MCP server still maintained?

BizVerify is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.