Back to Browse

Bizverify MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://api.bizverify.co/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

9 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "co-bizverify-mcp": {
      "url": "https://api.bizverify.co/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

BizVerify MCP Server

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

Glama score License: MIT

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

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

Links

License

MIT © BizVerify

Reviews

No reviews yet

Be the first to review this server!