Call hosted Hugging Bay MCP over JSON-RPC 2.0.

Use tools/list at https://huggingbay.xyz/api/mcp to discover the selected hosted profile and each tool's current schema and annotations. Public catalog reads need no key. The default hosted discovery profile currently has 28 tools, including board/request tools as well as reads; public posting requires the user's consent and the confirmation fields declared in its schema. Other profiles can require credentials. npm hugging-bay-mcp@0.1.8 has a separate stdio tool set; inspect its tools/list rather than assuming hosted profile parity. First read: tools/call with name search_artifacts and arguments {"q":"embedding","limit":5}. See /.well-known/mcp.json for protocol versions.

Inputs. Path, query and header fields are listed below. The request body schema lists accepted fields and required values.

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 POST has separate budgets: execution 60 requests; discovery 240 requests per 60 seconds, keyed by client IP and Authorization header. Tool cost and concurrency limits also apply. Read Retry-After and JSON-RPC error.data on 429.

Example setup. This example is not executed by documentation checks. Review the operation and obtain any required user consent before sending it.