Skip to main content
Glama
BizVerify

BizVerify MCP Server

Official
by BizVerify

Verify Business

verify_business

Confirm a business's existence, status, and good standing in a specific jurisdiction. Optionally retrieve entity type, formation date, registered agent, and more.

Instructions

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 Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNoVerification tier: quick (1 credit, always available) or deep (15 credits, availability varies by jurisdiction)quick
entity_nameYesBusiness entity name to verify
entity_typeNoOptional entity type filter to narrow results
webhook_urlNoURL to receive async results. Must be a publicly reachable http(s) URL.
jurisdictionYesJurisdiction code or name (e.g., "us-fl", "Florida", "FL")
force_refreshNoReturn the most current result instead of a previously stored one. Applies to the deep tier only (adds 10 credits); ignored on quick.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses important behavioral traits beyond annotations: requires authentication, credit deduction even if business not found (no-match is a result), refunds for failed calls, and available tiers. No contradiction with annotations (readOnlyHint=false, etc.).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary purpose and usage guidance. It is thorough but slightly verbose; some details like deep availability and credits could be condensed. Still well-structured and each sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool complexity (6 parameters, no output schema), the description covers all essential aspects: behavior, tiers, credits, refunds, authentication, and return information for quick vs deep. This provides sufficient context for an AI agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline 3. The description adds context about the 'level' parameter's credit costs and suboptions (force_refresh with deep), but doesn't significantly expand on what the schema already provides for other parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: '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.' It also distinguishes from the sibling tool search_entities by explicitly stating not to fall back to it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: '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.' Also explains the two tiers (quick vs deep) and when deep is available, giving clear context for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BizVerify/bizverify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server