# MCP catalog

The public MCP exposes anonymous research and content tools over Streamable HTTP.

## Connection

Endpoint: `https://tools.thepocketprotector.com/mcp`

Send JSON-RPC requests by POST. Supported protocol versions are generated in the [complete reference](/llms-full.txt). The server returns readable text and structured content; some tools also support MCP Apps choice cards. Text clients can follow the same clarification steps.

The public catalog is generated from the server's tool-list projection with account linking and calendar writes disabled. The [machine-readable catalog](/mcp/catalog.json) includes the server version, schema fingerprint, input schemas, annotations and retained compatibility names.

## Domain discovery

The [AI Catalog](/.well-known/ai-catalog.json) links to a [Server Card](/mcp/server-card) with the server identity, connection URL and supported protocol versions. Use `tools/list` after connecting to discover available tools and their current schemas.

Staging catalogs point to the staging connection. Production catalogs point to `https://tools.thepocketprotector.com/mcp`.

## Tool reference

Open **MCP tool reference** in the navigation to read each advertised tool. Search documentation by task, such as doctors, prescriptions, enrollment dates or content.

## Compatibility

Released names remain callable. Some earlier names map to clearer advertised names; other names retain a separate legacy handler. The catalog's `aliases` section distinguishes those cases. Discover supported names with `tools/list`; do not infer that a legacy handler accepts a renamed tool's arguments.

## Authentication and actions

The public endpoint requires no credentials and exposes no account or enrollment writes. Private account capabilities on other deployments are not part of this reference. Never send a workload API key to MCP or place credentials in a URL.

From version 0.4.0, initialization reports `com.thepocketprotector/medicare` as `serverInfo.name`, matching the registry and Server Card. Previously it reported `tpp-consumer-mcp`. Connection URLs, protocol versions, tool names, aliases and inputs remain compatible.