# MCP Server Inspector

> MCP Server Inspector is a paid API for AI agents from mcp.dropenginehq.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Read-only health check and tool-schema inspection for a public MCP (Model Context Protocol) endpoint, returning reachability status, tool count, and schema details without invoking any tools.

## Facts

- Endpoint: POST https://mcp.dropenginehq.com/api/mcp-server-inspect?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-server-inspector-afa9a977
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fdrqzNrXQp5WjXhA_rKSI

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 mcp-server-inspector-afa9a977 -d '<json body>'
```

Example prompt: Can you check if the MCP server at https://mcp.example.com/server is reachable and tell me how many tools it exposes — and specifically confirm whether it has a 'web_search' and 'code_executor' tool listed?

## When to prefer this

Use this endpoint when you need to verify the health, reachability, and tool-schema of a public MCP server before integrating it into an agent workflow, making a payment for its services, or routing tasks to it — especially when you want read-only inspection guarantees that no tools will be accidentally invoked during the probe. Prefer this over generic HTTP ping tools when you need MCP-protocol-aware inspection including tool enumeration and schema extraction.

## Known failure modes

- Endpoint URL is unreachable or times out — status returned as 'unreachable'
- Invalid or malformed URI provided — validation error before request is made
- MCP server returns a non-standard response not conforming to MCP protocol
- Expected tools not found on server — mismatch reported in response
- Tool count returns zero if server is reachable but exposes no tools
- Rate limiting or upstream errors from the target MCP server

## How this service works

Read-only health and tool-schema inspection for a public MCP endpoint.

## Output

Returns a JSON object indicating whether the MCP endpoint is reachable, how many tools it exposes, the tool schemas themselves, and flags confirming this was a read-only inspection where no tools were actually invoked.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "endpoint": {
   "type": "string",
   "format": "uri",
   "maxLength": 2048
  },
  "expected_tools": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 128,
    "minLength": 1
   },
   "maxItems": 100
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "reachable",
  "tool_count": 4,
  "read_only_inspection": true,
  "tools_were_not_called": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mcp-server-inspector-afa9a977/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp.dropenginehq.com](https://www.zero.xyz/host/mcp.dropenginehq.com/llms.txt)