# MCP Server Inspector

> MCP Server Inspector is a paid API for AI agents from agent.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-13).

Performs the MCP handshake against a remote server and returns its full catalogue of tools, resources, and prompts without executing anything.

## Facts

- Endpoint: POST https://agent.halowerk.com/v1/mcp-inspect?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mcp-server-inspector-7c484c45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jlOrx_n593Xs8DSRXwi9E

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-7c484c45 -d '<json body>'
```

Example prompt: Can you inspect the MCP server at https://myserver.example.com and list all the tools it exposes, along with their input schemas and any resources or prompts it has?

## When to prefer this

Use this endpoint when you need to discover or audit what an MCP-compatible server exposes — its tools, resources, and prompts — before deciding whether to integrate or call it. It is read-only and safe, making it ideal for automated capability discovery, pre-integration audits, and building dynamic agent tool registries. Prefer this over manually inspecting MCP server documentation when the server supports either plain-JSON or SSE streaming responses.

## Known failure modes

- Server URL is unreachable or returns a non-MCP response — HTTP error or empty catalogue returned
- Server does not complete the MCP handshake correctly — protocol error reported
- Streaming event-stream responses that time out before catalogue is fully read
- Session ID mismatch on subsequent calls — session may have expired

## How this service works

Performs the MCP handshake against a streamable-HTTP endpoint and then reads the catalogue: tools with their input schemas, resources with their URIs and mime types, and prompts with their arguments. Servers answering as an event stream are handled as well as plain JSON, and a session id is carried across calls. Only listing methods are sent — no tool of the inspected server is ever executed, nothing is written, and no resource contents are read.

## Output

A structured catalogue of the MCP server's advertised capabilities: tools with names, descriptions, and JSON input schemas; resources with URIs and MIME types; prompts with their argument definitions. A session ID is returned for continuity across calls. No tool is ever executed and no resource content is fetched.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 2000,
   "description": "The MCP endpoint, e.g. https://example.com/mcp. Public https address."
  },
  "include": {
   "type": "array",
   "items": {
    "enum": [
     "tools",
     "resources",
     "prompts"
    ],
    "type": "string"
   },
   "default": [
    "tools",
    "resources",
    "prompts"
   ],
   "description": "Which catalogues to read."
  },
  "include_schemas": {
   "type": "boolean",
   "default": true,
   "description": "Return the full input schema per tool. If false, only names and descriptions."
  }
 }
}
```

## More

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