QuoAPI
com.quoapi/mcpVersion 0.29.0Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
Status
Responds137 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:12 UTC
- Latency
- 137 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://quoapi.com/mcpResponds137 msNo sign-in
Claude Code
claude mcp add --transport http quoapi https://quoapi.com/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: quoapi
Remote MCP server URL: https://quoapi.com/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"quoapi": {
"url": "https://quoapi.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"quoapi","type":"http","url":"https://quoapi.com/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
4 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
quoapi.describeRead the DESIGN-TIME contract for an exact handle from quoapi.search (e.g. address.validate): inputSchema/outputSchema, auth/scopes, pricing, availability, regions and REST mapping. Use inputSchema before quoapi.execute. No upstream action or charges are performed; this does not test credentials or provider reachability. Unknown or MCP-ineligible handles return capability_not_mcp_visible. Use quoapi.inspect for runtime health, not contracts. | No | Yes | Yes | No |
quoapi.executeExecute an authorized handle using the inputSchema from quoapi.describe. May send messages, modify/delete data or incur charges: check pricing and obtain user approval first. For live actions, confirm=true, interactive confirmation or step-up may be required; policy can still deny execution. Optional task_id correlates workflow; provider selects an eligible upstream route; auth_mode selects a supported credential model—none bypasses access gates. Reuse idempotency_key only for the same operation with identical inputs. Returns gateway output or a structured error. | Yes | No | No | Yes |
quoapi.inspectRead-only RUNTIME STATUS of the QuoAPI MCP gateway, not a provider execution. With no arguments returns state, server protocol version, tool count, visible capability count and discovery/registry revisions. Optional capability handle adds public context only: this is not to test upstream execution, a live upstream health probe, credentials or tenant authorization. Use quoapi.describe for schemas, pricing and auth; quoapi.search to discover handles; quoapi.execute for approved actions. Unknown handles return capability_not_mcp_visible; status incurs no upstream charges. | No | Yes | Yes | No |
quoapi.searchFind canonical QuoAPI capability handles by intent, ID or provider; catalog metadata are not upstream API results. Use query="*" to enumerate MCP-visible capabilities (limit 1–20; offset 0 then next_offset until null). Inventory returns total/count/next_offset; keyword search returns up to limit matches without total. Provider/region filters restrict but never grant access. Results do not prove tenant authorization, a connected account or live provider availability. Use quoapi.describe for contracts; quoapi.inspect for runtime health. | No | Yes | Yes | Yes |
Details
- Registry status
- Active
- Published
- Nov 6, 2026
- Updated
- Nov 6, 2026
- Repository
- Not given
- Categories (suggested)
- Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared