Read hosted MCP profiles, tools and connection metadata.

Inputs. No path or query fields are required. No request body is required.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. API JSON failures use the documented response schema. Read code, message and next; retry only when the response allows it. Auth, invalid input and missing records need a caller change.

Rate limits. MCP discovery GET uses a separate per-IP token bucket: capacity 5, refilling one token every 30 seconds. A 429 includes Retry-After. Use tools/list over POST for protocol discovery.