BizVerify MCP Server

MCP serverAI & models

Your AI can confirm whether a company is really registered before you rely on it or do business with it. This adds Know Your Business checks, meaning your AI can verify business registrations so your decisions rest on confirmed facts instead of assumptions.

Available today. Use it from your connected AI after setup.

After adding it, ask your AI to verify a business registration the next time a company comes up in a task. Use the checks when vetting a vendor, partner, or customer before you commit.

Then ask your AI: use BizVerify MCP Server to get config

What your AI can do with it

  • Verify a company's business registration on request
  • Check that a business is properly registered before you work with it
  • Include a registration check when your AI answers questions about a company
  • Run a Know Your Business check whenever a business comes up in your work

From the project's README

As published by bizverify/bizverify-mcp in README.md.

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_configSupported jurisdictions, credit pricing, packages, features
list_jurisdictionsAll jurisdictions with capabilities and active status
verify_businessConfirm 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_entitiesDiscover candidate businesses by name across one or all active jurisdictions
check_job_statusPoll an async verification job (free)
get_entityRetrieve cached entity data by ID (free)
get_entity_historyHistorical verification snapshots for an entity
get_accountAccount details and credit balance
purchase_creditsCreate 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

Option A — Hosted endpoint (recommended)

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

Links

License

MIT © BizVerify

Tools it offers (9)

What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.

  • get_config
  • list_jurisdictions
  • verify_business
  • search_entities
  • check_job_status
  • get_entity
  • get_entity_history
  • get_account
  • purchase_credits

Signals

Last commit
Jun 2026
Advanced
Delivery
mcp MCP server → your ahel gateway (mcp.ahel.ai) → every connected AI client.
Catalog kind
mcp-server
Gateway key
co-bizverify-mcp
Source
github.com/bizverify/bizverify-mcp
Hosted endpoint
https://api.bizverify.co/mcp