HopBase Gateway Management
MCP server by HopBase · mcp
Read-only management tools scoped to the calling HopBase API key: balance, key quota, available models with effective pricing, and usage stats; plus search_docs (search the integration docs) and get_model_limits (endpoint, parameters and limits of one model, best-effort from the docs). The handshake and tools/list need no key; calling a tool requires a HopBase API key in the Authorization (or x-api-key) header, and results are scoped to that key. Inference traffic stays on the protocol-compatible endpoints described at https://hop-base.com/llms.txt.
Endpoint: https://api.hop-base.com/mcp
Verification: observed. Source: crawl.
Capabilities (6)
- get_balance
- get_key_info
- list_models
- get_usage
- search_docs
- get_model_limits