English Français العربية

BizVerify

Official registry Security

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http bizverify 'https://api.bizverify.co/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "bizverify": {
            "type": "http",
            "url": "https://api.bizverify.co/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. BizVerify MCP Server
  2. Tools
  3. Quick start
  4. Configuration
  5. Getting an API key
  6. Development
  7. Links
  8. License

BizVerify MCP Server

KYB for AI agents — verify and search business entities across US state and international company registries, straight from any MCP client.

BizVerify confirms a company's legal existence, status, good standing, registered agent, officers, and filing history by reading official government business registries in real time.

The canonical BizVerify MCP server is hosted as a Streamable HTTP endpoint:

https://api.bizverify.co/mcp

This repository packages that server as a local stdio bridge (plus a Docker image) for MCP clients and sandboxes that expect a local process. The bridge is a thin transparent proxy — tool definitions and results come directly from the hosted server, so it never drifts out of sync.

Tools

ToolAuthWhat it does
get_config–Supported jurisdictions, credit pricing, packages, features
list_jurisdictions–All jurisdictions with capabilities and active status
verify_business✅Confirm a named business in one jurisdiction — existence, status, good standing (quick), plus entity type, formation date, registered agent, officers, principal address and filings (deep)
search_entities✅Discover candidate businesses by name across one or all active jurisdictions
check_job_status✅Poll an async verification job (free)
get_entity✅Retrieve cached entity data by ID (free)
get_entity_history✅Historical verification snapshots for an entity
get_account✅Account details and credit balance
purchase_credits✅Create a Stripe checkout session for more credits

Tools marked ✅ require an API key (or OAuth token). get_config and list_jurisdictions are free and unauthenticated.

Quick start

If your client supports remote MCP servers, just point it at https://api.bizverify.co/mcp and send your key as an X-API-Key header (OAuth 2.1 Bearer tokens are also accepted).

For stdio-only clients, bridge the hosted endpoint with mcp-remote:

{
  "mcpServers": {
    "bizverify": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.bizverify.co/mcp",
        "--header", "X-API-Key:${BIZVERIFY_API_KEY}"
      ],
      "env": { "BIZVERIFY_API_KEY": "your-api-key" }
    }
  }
}
Option B — This bridge (from source)
git clone https://github.com/BizVerify/bizverify-mcp.git
cd bizverify-mcp
npm install
npm run build

Then register it with your client (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "bizverify": {
      "command": "node",
      "args": ["/absolute/path/to/bizverify-mcp/dist/index.js"],
      "env": { "BIZVERIFY_API_KEY": "your-api-key" }
    }
  }
}
Option C — Docker
docker build -t bizverify-mcp .
docker run -i --rm -e BIZVERIFY_API_KEY=your-api-key bizverify-mcp
{
  "mcpServers": {
    "bizverify": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "BIZVERIFY_API_KEY", "bizverify-mcp"],
      "env": { "BIZVERIFY_API_KEY": "your-api-key" }
    }
  }
}

Configuration

Env varRequiredDefaultDescription
BIZVERIFY_API_KEYFor authenticated tools–Your BizVerify API key, sent as X-API-Key. get_config and list_jurisdictions work without it.
BIZVERIFY_MCP_URLNohttps://api.bizverify.co/mcpOverride the upstream MCP endpoint.

Getting an API key

Create one in seconds — new accounts get 50 free credits:

# 1. Request an access code (sent by email)
curl -X POST https://api.bizverify.co/v1/auth/request-access \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com","accept_terms":true}'

# 2. Exchange the 6-digit code for an API key
curl -X POST https://api.bizverify.co/v1/auth/verify-access \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com","code":"123456","label":"mcp"}'

See the setup guide and docs for full details.

Development

npm install
npm run build        # compile to dist/
npm run typecheck    # type-check only
npm start            # run the stdio bridge

# Refresh the offline tool snapshot from the live endpoint
node scripts/gen-snapshot.mjs

The bundled src/tools-snapshot.ts is used only as an offline fallback for tools/list (e.g. during a sandboxed container check). Live calls always proxy to the hosted server.

License

MIT © BizVerify

Frequently asked questions

What is BizVerify?

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

How do I install BizVerify?

It runs as a remote server. In Claude Code: claude mcp add --transport http bizverify 'https://api.bizverify.co/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does BizVerify need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is BizVerify open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains BizVerify?

It is published by BizVerify. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.