QuoAPI
Server Details
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 4 tools
Each tool occupies a distinct phase of the gateway workflow: search (discovery), describe (design-time contract), inspect (runtime health), execute (live action). Descriptions explicitly disambiguate boundaries, e.g. describe tells the agent to use inspect for runtime health and not to test credentials, and inspect redirects to describe/search/execute for their respective jobs.
All four tools follow the same quoapi.<verb> pattern with single, lowercase, unambiguous verbs (search, describe, inspect, execute). No mixing of casing or noun/verb styles.
Four tools is exactly the minimal complete set for a capability-gateway: discover, contract, status, execute. Nothing appears redundant, and no phase of the intended workflow lacks a dedicated tool.
The core lifecycle (find -> understand -> check -> execute) is fully covered. Minor gaps remain around authorization and async workflows: the descriptions repeatedly warn that results do not prove tenant authorization or connected accounts, yet there is no tool to check auth/connection state, and task_id is accepted by execute but no task-status or cancellation tool exists.
Publisher details
- Operator
- General Informatics · Publisher source
- Operator website
- https://www.quoapi.com
- Vendor relationship
- First-party
- Documentation
- https://quoapi.com/docs
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- https://quoapi.com/de/how-quoapi-works
Available Tools
4 toolsquoapi.describeDescribe a QuoAPI capabilityARead-onlyIdempotentInspect
Read 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.
Inputs: capability (required).
quoapi.executeExecute a QuoAPI capabilityADestructiveInspect
Execute 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.
Inputs: input (required), capability (required), confirm, task_id, +3 more.
quoapi.inspectInspect QuoAPI runtime statusARead-onlyIdempotentInspect
Read-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.
Inputs: capability.
quoapi.searchSearch QuoAPI capabilitiesARead-onlyIdempotentInspect
Find 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.
Inputs: query (required), limit, offset, region, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Discover, compare, route, and execute machine-accessible capabilities for AI agents.
Discover, pay for, execute, and publish APIs through Apiosk.
Discover and call 2,000+ x402 machine-payable services through one graded API key + gateway.
Discover and execute versioned AI capabilities with worker leases and trial-credit settlement.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables supported AI clients to discover, inspect, and execute 2,000+ models and APIs, including free data APIs and paid LLM, image, video, and audio calls, with OAuth, pricing checks, and rollback.556,724 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to inspect accessible accounts, read provider data, and make explicitly approved entity-tag changes through a hosted gateway with discovery, schemas, policy enforcement, and execution controls.MIT
- AlicenseBqualityDmaintenanceNatural language API discovery MCP server. Search 700+ API capabilities across 163 current providers, get, exact endpoints, auth setup, and code snippets. Supports auto-discovery of new APIs.330 PyPI1MIT

DotMoose MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables product and domain discovery, quotes, publication planning, and secure signup handoff, plus OAuth-protected account, support, diagnostics, and managed application deployment operations.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.