---
title: "Compatibility discovery document; clients send JSON-RPC with POST."
method: GET
path: "/api/mcp"
tags: ["MCP"]
---

# Compatibility discovery document; clients send JSON-RPC with POST.

`GET /api/mcp`

## Request

- Base URL: `https://huggingbay.xyz`
- URL: `https://huggingbay.xyz/api/mcp`
- Auth: none declared

Browser GET returns discovery JSON. GET with Accept: text/event-stream returns 405 with Allow: GET, POST, DELETE. Use /api/mcp/info for the documented discovery information URL.

**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.** JSON-RPC errors use error.code, error.message and error.data. Tool results may also set isError. Check the protocol response, not only the HTTP status.

**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.

## Response `200`

MCP discovery document

- object

## Other responses

- `405`: GET event streams are not offered; send Streamable HTTP requests with POST.
- `429`: Repeated discovery GETs from this IP are rate-limited.

---

[API](https://skmtc.dev/huggingbay/apis/hugging-bay-public-api.md) · [All operations](https://skmtc.dev/huggingbay/apis/hugging-bay-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/huggingbay/apis/hugging-bay-public-api/revisions/63c474bf0fe4?raw)