QuoAPI
by quoapi.com in Markets & finance
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
https://quoapi.com/mcp- Tools
- 4
- open to any client
- Uptime
- 23.1%
- last 30 days
- Response time
- 37 ms
- 90 ms slowest 5%
- Last check
- Passed
- 1 h ago, next in 4 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"quoapi": {
"type": "http",
"url": "https://quoapi.com/mcp"
}
}
}4 tools
- quoapi.search
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…
- quoapi.describe
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…
- quoapi.execute
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…
- quoapi.inspect
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…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 1 h ago | Passed | 200 | 32 ms |
| 12 h ago | Passed | 200 | 37 ms |
| 23 h ago | Passed | 200 | 90 ms |
| 4 days ago | initialize returned HTTP 400 | 400 | 43 ms |
| 6 days ago | initialize returned HTTP 400 | 400 | 72 ms |
Show 8 older checks
| 7 days ago | initialize returned HTTP 400 | 400 | 74 ms |
| 8 days ago | initialize returned HTTP 400 | 400 | 79 ms |
| 10 days ago | initialize returned HTTP 400 | 400 | 200 ms |
| 11 days ago | initialize returned HTTP 400 | 400 | 44 ms |
| 12 days ago | initialize returned HTTP 400 | 400 | 37 ms |
| 14 days ago | initialize returned HTTP 400 | 400 | 49 ms |
| 14 days ago | initialize returned HTTP 400 | 400 | 60 ms |
| 15 days ago | initialize returned HTTP 400 | 400 | 65 ms |