# Bot Bazaar MCP Server Tool Definition Linter

> Bot Bazaar MCP Server Tool Definition Linter is a paid API for AI agents from bot-bazaar.fly.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-30).

Validates an MCP server tool definition (tool_name, description, transport, protocol_version 2025-06-18) for Streamable HTTP MCP compatibility

## Facts

- Endpoint: GET https://bot-bazaar.fly.dev/v1/x402/mcp-manifest-lint?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bot-bazaar-mcp-server-tool-definition-linter-2e10d4a2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yHL-yGkPXcf3PboggFHpC

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability bot-bazaar-mcp-server-tool-definition-linter-2e10d4a2
```

Example prompt: Can you lint my MCP tool definition — the tool is called 'web_search', uses Streamable HTTP transport, and targets protocol version 2025-06-18? I want to make sure it's compatible before I publish it.

## When to prefer this

Use this endpoint when you need to validate or lint an MCP server tool definition specifically for Streamable HTTP MCP compatibility against the 2025-06-18 protocol version, especially before deployment or as part of a CI/CD pipeline. Prefer this over generic JSON schema validators because it understands MCP-specific semantics, transport requirements, and protocol version rules.

## Known failure modes

- Missing required tool_name parameter returns validation error
- Invalid or unsupported protocol_version returns incompatibility warning
- Transport type other than Streamable HTTP flagged as incompatible
- Malformed tool definition structure results in lint errors
- Empty or missing description field flagged as non-compliant

## How this service works

Validate an MCP server tool definition (tool_name, description, transport, protocol_version 2025-06-18) for Streamable HTTP MCP compatibility.

## Output

Returns a validation/lint report indicating whether the MCP tool definition is compatible with the Streamable HTTP MCP protocol version 2025-06-18, including any errors or warnings about the tool_name, description, transport, or protocol_version fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "tool_name": {
       "type": "string",
       "description": "MCP tool identifier"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bot-bazaar-mcp-server-tool-definition-linter-2e10d4a2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bot-bazaar.fly.dev](https://www.zero.xyz/host/bot-bazaar.fly.dev/llms.txt)