← Registry

Data Collection

bizclaw.xyz

Search for companies in the BizClaw business directory and retrieve detailed company information.

1 endpoint9 known toolsFirst detected July 25, 2026Last detected September 18, 2026

ENDPOINT 1

https://bizclaw.xyz/mcp

No auth detected

MCP server metadata

Name
BizClaw
Version
1.30.0
Capabilities
experimentalpromptsresourcestools
Server instructions

BizClaw is an AI-accessible business directory. Use the available tools to search for companies, get detailed profiles, ask natural language questions about businesses, and browse categories. All data comes from real companies that have been crawled and analyzed by AI. CRITICAL RULES FOR TOOL USAGE: 1. NEVER answer questions about a specific company from your own general knowledge or from previously cached results. Always call the appropriate tool to get fresh, accurate data. 2. When the user asks a specific question about a company (e.g., pricing, policies, features, bargaining, delivery, support, locations), you MUST call ask_about_companies with the question and pass the relevant company IDs in context_company_ids. Do NOT answer from memory or prior tool results. 3. When new companies are added or the user says 'I added a new company' or 'check again', always re-call the relevant search or ask tool — never reuse stale results from the current session. 4. If you already searched and got results, and the user asks a follow-up question about those companies, call ask_about_companies with context_company_ids set to the IDs from the previous search. 5. PROPOSAL SYSTEM: Agents can send proposals to verified companies on behalf of their users. To use proposal tools (create_proposal, get_my_proposals, reply_to_proposal), you need an API key. Register at POST /api/v1/agent/register to get one. Pass it as the api_key tool argument, or configure it once as the X-API-Key MCP connection header. 5a. If the user chooses or says they want to proceed with a VERIFIED company from search results, offer to create a proposal/quote request. Do NOT create it automatically. First collect the customer's real name, real active email, and the exact project/request description, then confirm before calling create_proposal. 6. Proposals are NOT logged as audience insights — they go directly to the company dashboard. 7. When checking proposal status with get_my_proposals, NEVER use status_filter — always fetch ALL proposals. Companies can approve, reject, or respond — filtering by one status will miss the others. 8. Do not promise proposal-status email notifications. Agents must check proposals by polling via get_my_proposals. Say 'ask me to check anytime' instead of 'I will notify you'. 9. When a proposal is rejected or responded, always show the company's response message to the user. 10. PROFILE UPDATE: Agents can update their name and email via PUT /api/v1/agent/me with JSON body {name, owner_email}. Requires X-API-Key header. If the user asks to update their registered name or email, use this endpoint. 11. UCP: BizClaw publishes a UCP profile at /.well-known/ucp. UCP-aware callers may pass meta.ucp-agent.profile in tool arguments; BizClaw will include negotiated ucp metadata in responses. Legacy MCP calls without meta remain supported.

Known tools 9

search_companies

Search for companies in the BizClaw business directory.

Inferred read-only
get_company

Get full details for a specific company by its ID.

Inferred read-only
ask_about_companies

Ask a natural language question about companies and get AI-powered recommendations.

Inferred read-only
list_categories

List all available business categories in BizClaw.

Inferred read-only
get_company_by_website

Look up a company by its website URL.

Inferred read-only
create_proposal

Create a proposal/quote request to a verified company on behalf of a customer.

Potential side effects
create_batch_proposals

Create proposals to multiple companies at once (max 10).

Potential side effects
get_my_proposals

Get all proposals created by the current agent.

Inferred read-only
reply_to_proposal

Reply to a company's response on a proposal.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bizclaw]
url = "https://bizclaw.xyz/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "bizclaw": {
      "type": "http",
      "url": "https://bizclaw.xyz/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: bizclaw
Remote MCP URL: https://bizclaw.xyz/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bizclaw": {
      "url": "https://bizclaw.xyz/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "bizclaw": {
      "type": "http",
      "url": "https://bizclaw.xyz/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "bizclaw",
  "transport": "streamable-http",
  "url": "https://bizclaw.xyz/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for bizclaw.xyz was fetched 2026-08-23T20:22:33.120Z and is being refreshed.

Trust status Trusted

bizclaw.xyz is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.