56trust / 100

QuoAPI

by quoapi.com in Markets & finance

MCP serverPassing, checked 1 h ago

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

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

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

WhenResultHTTPTime
1 h agoPassed20032 ms
12 h agoPassed20037 ms
23 h agoPassed20090 ms
4 days agoinitialize returned HTTP 40040043 ms
6 days agoinitialize returned HTTP 40040072 ms
Show 8 older checks
7 days agoinitialize returned HTTP 40040074 ms
8 days agoinitialize returned HTTP 40040079 ms
10 days agoinitialize returned HTTP 400400200 ms
11 days agoinitialize returned HTTP 40040044 ms
12 days agoinitialize returned HTTP 40040037 ms
14 days agoinitialize returned HTTP 40040049 ms
14 days agoinitialize returned HTTP 40040060 ms
15 days agoinitialize returned HTTP 40040065 ms