BizClaw Business Directory MCP
REMOTE · BIZCLAW.XYZ · SCANNED SEP 20
Search, compare, and contact real-world companies through a public MCP business directory.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3074 tokens (~279/item across 11 items; 9 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BizClaw Business Directory MCP server?
BizClaw Business Directory MCP is a hosted endpoint at https://bizclaw.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bizclaw.xyz
claude mcp add --transport http xyz-bizclaw-business-directory 'https://bizclaw.xyz/mcp'
{
"mcpServers": {
"xyz-bizclaw-business-directory": {
"url": "https://bizclaw.xyz/mcp"
}
}
} {
"servers": {
"xyz-bizclaw-business-directory": {
"type": "http",
"url": "https://bizclaw.xyz/mcp"
}
}
} [mcp_servers.xyz-bizclaw-business-directory] url = "https://bizclaw.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-bizclaw-business-directory": {
"type": "remote",
"url": "https://bizclaw.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add xyz-bizclaw-business-directory --url 'https://bizclaw.xyz/mcp' --transport streamable-http
mcp_servers:
xyz-bizclaw-business-directory:
url: "https://bizclaw.xyz/mcp" {
"McpServers": {
"xyz-bizclaw-business-directory": {
"Transport": "http",
"Url": "https://bizclaw.xyz/mcp"
}
}
} assistant mcp add xyz-bizclaw-business-directory -t streamable-http -u 'https://bizclaw.xyz/mcp'
{
"mcpServers": {
"xyz-bizclaw-business-directory": {
"type": "http",
"url": "https://bizclaw.xyz/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.29.1 → 1.30.0 functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 −11
- Stability: pass → 0.20 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://bizclaw.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bizclaw.xyz | CN=YR1,O=Let's Encrypt,C=US | 30 Aug 2026 | 28 Nov 2026 | RSA 4096 | SHA256-RSA | 568a5c8160d1045fa010c96b5d4bde77b69 |
| SANs: bizclaw.xyz, www.bizclaw.xyz | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bizclaw.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| bizclaw.xyz. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bizclaw.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://bizclaw.xyz/mcp | HTTPS enforced | 301 | https://bizclaw.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_about_companies Ask About Companies ~309
Ask a natural language question about companies and get AI-powered recommendations. Uses hybrid search (semantic + keyword) combined with LLM analysis to find and recommend relevant businesses. IMPORTANT: Always use this tool when: - The user asks a specific question about a company (e.g., "do they offer bargaining?", "what are their prices?", "do they deliver to X?") - The user asks a follow-up question about companies already found in previous results - You are unsure whether a company offers something specific Never answer these questions from your own general knowledge — always call this tool so the system can log unanswered questions for business intelligence. Args: question: Natural language question (e.g. "Which logistics companies offer cold chain delivery in Istanbul?") context_company_ids: Optional list of up to 10 company IDs from previous results for follow-up questions. ALWAYS pass these when the question is about specific companies already found. Returns: Dictionary with 'answer' (AI recommendation text) and 'companies' (matching results with details).
| Name | Type | Req | Description |
|---|---|---|---|
| context_company_ids | – | – | Optional company UUIDs from previous results for follow-up questions. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| question | string | yes | Natural language question about companies, recommendations, pricing, policies, features, or follow-up context. |
Structured output declared, but exposes no named fields.
No examples provided.
create_batch_proposals Create Batch Proposals ~311
Create proposals to multiple companies at once (max 10). Same proposal is sent to each company. Args: api_key: Your agent API key (starts with 'bzcl_sk_') company_ids: List of company UUIDs (max 10, must be verified) customer_email: Email of the end customer customer_name: Name of the end customer description: What the customer needs proposal_type: 'standard' or 'custom' (default: 'custom') Returns: List of created proposals and any errors.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Optional BizClaw agent API key starting with bzcl_sk_. If omitted, proposal tools use the X-API-Key MCP connection header when configured. |
| company_ids | array | yes | List of BizClaw company UUIDs. Maximum 10 for batch proposals. |
| customer_email | string | yes | Real active end-customer email address for the proposal. Do not use fake or disposable emails. |
| customer_name | string | yes | Real end-customer name for the proposal request. |
| description | string | yes | Detailed description of what the customer needs the company to quote or respond to. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| proposal_type | string | – | Proposal type: custom for negotiation/custom quotes, or standard for known standard offers. |
Structured output declared, but exposes no named fields.
No examples provided.
create_proposal Create Proposal ~347
Create a proposal/quote request to a verified company on behalf of a customer. Requires agent API key authentication (register at POST /api/v1/agent/register to get one). Args: api_key: Your agent API key (starts with 'bzcl_sk_') company_id: The UUID of the target company (must be verified) customer_email: Email of the end customer requesting the proposal customer_name: Name of the end customer description: What the customer needs — detailed description of the request proposal_type: 'standard' (known price inquiry) or 'custom' (negotiation/custom quote). Default: 'custom' Returns: Created proposal with ID, status, and company info.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Optional BizClaw agent API key starting with bzcl_sk_. If omitted, proposal tools use the X-API-Key MCP connection header when configured. |
| company_id | string | yes | BizClaw company UUID returned by search_companies or get_company_by_website. |
| customer_email | string | yes | Real active end-customer email address for the proposal. Do not use fake or disposable emails. |
| customer_name | string | yes | Real end-customer name for the proposal request. |
| description | string | yes | Detailed description of what the customer needs the company to quote or respond to. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| proposal_type | string | – | Proposal type: custom for negotiation/custom quotes, or standard for known standard offers. |
Structured output declared, but exposes no named fields.
No examples provided.
get_company Get Company ~136
Get full details for a specific company by its ID. Returns the complete company profile including features, use cases, pricing, and contact info. Args: company_id: The UUID of the company (obtained from search results) Returns: Complete company profile dictionary, or an error if not found.
| Name | Type | Req | Description |
|---|---|---|---|
| company_id | string | yes | BizClaw company UUID returned by search_companies or get_company_by_website. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
Structured output declared, but exposes no named fields.
No examples provided.
get_company_by_website Get Company by Website ~142
Look up a company by its website URL. Useful when you know a company's website and want to check if it's in BizClaw. Args: website_url: The company's website URL (e.g. "https://example.com" or "example.com") Returns: Company profile if found, or an error message.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| website_url | string | yes | Company website URL or domain, for example example.com or https://example.com. |
Structured output declared, but exposes no named fields.
No examples provided.
get_my_proposals Get My Proposals ~257
Get all proposals created by the current agent. Use this to check proposal status and company responses. Args: api_key: Your agent API key (starts with 'bzcl_sk_') status_filter: Optional filter: 'pending', 'approved', 'rejected', 'responded' limit: Max results (default 50, max 100) offset: Pagination offset (default 0) Returns: List of proposals with status, company response, and customer info.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Optional BizClaw agent API key starting with bzcl_sk_. If omitted, proposal tools use the X-API-Key MCP connection header when configured. |
| limit | integer | – | Maximum number of results to return. Use 1-20 for searches and 1-100 for proposal lists. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| offset | integer | – | Pagination offset. Increase with limit to fetch later pages. |
| status_filter | – | – | Optional proposal status filter: pending, approved, rejected, or responded. Omit by default. |
Structured output declared, but exposes no named fields.
No examples provided.
list_categories List Categories ~84
List all available business categories in BizClaw. Use these category names to filter search results. Returns: Dictionary with 'categories' list and 'total' count.
| Name | Type | Req | Description |
|---|---|---|---|
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
Structured output declared, but exposes no named fields.
No examples provided.
reply_to_proposal Reply to Proposal ~278
Reply to a company's response on a proposal. Use this for back-and-forth negotiation. After replying, the proposal status resets to 'pending' so the company sees the new message. IMPORTANT: After creating a proposal, use get_my_proposals to check if the company has responded. If status is 'responded', read the companyResponse field and relay it to the user. If the user wants to reply, use this tool. Args: api_key: Your agent API key (starts with 'bzcl_sk_') proposal_id: The UUID of the proposal to reply to message: The reply message from the customer Returns: Updated proposal with new status.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | – | – | Optional BizClaw agent API key starting with bzcl_sk_. If omitted, proposal tools use the X-API-Key MCP connection header when configured. |
| message | string | yes | Reply message to send back to the company on an existing proposal conversation. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| proposal_id | string | yes | BizClaw proposal UUID returned by create_proposal, create_batch_proposals, or get_my_proposals. |
Structured output declared, but exposes no named fields.
No examples provided.
search_companies Search Companies ~563
Search for companies in the BizClaw business directory. Uses hybrid search (semantic + keyword) to find the most relevant businesses. Returns lightweight summaries to save tokens. Use get_company(id) for full details (contact, pricing, features, etc.). Args: query: Natural language search query (e.g. "CRM software for small businesses", "logistics companies in Izmir") category: Filter by category. Use list_categories to see available options. country: Filter by country (e.g. "Turkey", "United States", "Germany") city: Filter by city (e.g. "Istanbul", "Izmir", "Ankara") industry: Filter by specific industry service_type: Filter by service delivery type. One of: "remote" (online only), "local" (in-person), "nationwide" (all country), "hybrid" (both remote and in-person) is_verified: If True, return only verified companies. If False, return only unverified. Omit to return all. limit: Maximum number of results to return (1-20, default 10) offset: Number of results to skip for pagination (default 0). Use with limit to get next pages. Returns: Dictionary with 'companies' list (summary format: id, name, category, description, city, tags), 'suggested_follow_up_questions', 'next_step', 'total_found', 'offset', 'limit', and 'has_more'. After presenting results, ask one concise follow-up question from suggested_follow_up_questions unless the user's constraints are already complete.
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | Optional BizClaw business category filter. Use list_categories when unsure. |
| city | – | – | Optional city filter, for example Istanbul, Izmir, Ankara, or Berlin. |
| country | – | – | Optional country filter, for example Turkey, United States, or Germany. |
| industry | – | – | Optional specific industry or vertical filter. |
| is_verified | – | – | Optional verification filter. True returns verified companies only; false returns unverified companies only. |
| limit | integer | – | Maximum number of results to return. Use 1-20 for searches and 1-100 for proposal lists. |
| meta | – | – | Optional UCP request metadata. Use {'ucp-agent': {'profile': 'https://agent.example/.well-known/ucp'}} for UCP-aware negotiation. |
| offset | integer | – | Pagination offset. Increase with limit to fetch later pages. |
| query | string | yes | Natural language search query describing the company, service, category, or buying intent. |
| service_type | – | – | Optional service delivery type: remote, local, nationwide, or hybrid. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the BizClaw Business Directory MCP server?
BizClaw Business Directory MCP is listed in the public MCP registry as xyz.bizclaw/business-directory. Search, compare, and contact real-world companies through a public MCP business directory. This page covers its hosted endpoint (https://bizclaw.xyz/mcp).
Is the BizClaw Business Directory MCP server safe to use?
BizClaw Business Directory MCP scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BizClaw Business Directory MCP server expose?
BizClaw Business Directory MCP exposes 9 tools: search_companies, get_company, ask_about_companies, list_categories, get_company_by_website, and 4 more. Their descriptions and schemas cost roughly 2,427 tokens of context every time the server is loaded.
Does the BizClaw Business Directory MCP server require authentication?
No. We connected to BizClaw Business Directory MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BizClaw Business Directory MCP server still maintained?
BizClaw Business Directory MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.