# MCP Server Inspector

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

Connects to any MCP server as a client would and reports connectivity, protocol version, auth requirements, latency, tool count, and quality issues with tool descriptions or input schemas.

## Facts

- Endpoint: GET https://manylives.me/paid/mcp/inspect?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-server-inspector-fa11cf27
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8IU1QHO96AEUN59bcqddI

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-fa11cf27
```

Example prompt: Can you inspect my MCP server at https://manylives.me/mcp and tell me if it connects, what protocol version it uses, how fast it responds, and whether any of the tools have missing or weak descriptions?

## When to prefer this

Use this endpoint when you need to programmatically audit or validate an MCP server — especially before publishing, after deployment, or when debugging connectivity or tool-quality issues. It is purpose-built for MCP protocol introspection, providing structured quality scores and fix checklists that generic HTTP health-check or curl-based approaches cannot offer.

## Known failure modes

- Target MCP server is unreachable — returns connects: false with no further data
- Server responds but speaks an unrecognized protocol version
- Auth-gated server blocks inspection before tool list can be retrieved
- Malformed URL input causes parameter validation error
- Target server times out before responding

## How this service works

Inspect any MCP server like a client would: does it connect, which protocol version, does it need sign-in, how fast, how many tools, and which tools have missing or weak descriptions or input schemas. A checklist of fixes for server owners.

## Output

Returns a JSON object with: connection success boolean, latency in milliseconds, server name and version, protocol version string, tool count, overall quality score (0-100), authentication requirement indicator, and an array of human-readable problem descriptions (e.g. 'tool X has no description', 'input schema missing for tool Y').

## 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": {
     "type": "string",
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "examples": [
        "https://manylives.me/mcp"
       ],
       "description": "https://... MCP endpoint (required)"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "properties": {
      "ms": {
       "type": "number"
      },
      "url": {
       "type": "string"
      },
      "score": {
       "type": "number"
      },
      "tools": {
       "type": "number"
      },
      "server": {
       "type": "object",
       "properties": {
        "name": {
         "type": "string"
        },
        "version": {
         "type": "string"
        }
       }
      },
      "connects": {
       "type": "boolean"
      },
      "problems": {
       "type": "array",
       "items": {
        "type": "string"
       }
      },
      "protocol": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ms": 240,
  "url": "https://…/mcp",
  "score": 80,
  "tools": 12,
  "server": {
   "name": "…",
   "version": "1.0"
  },
  "connects": true,
  "problems": [
   "3 tools have no description"
  ],
  "protocol": "2025-06-18"
 }
}
```

## More

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