QuoAPI MCP Server

by quoapi Your server? Claim it

answering

QuoAPI is answering right now. Last checked 9 min ago. It exposes 4 tools.

Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.

Uptime history 12 days of history · worst day 0%

12 days agonow

97.8%

Uptime 24h

89 of 91 checks

Tools

read from the server

81 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 26

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 November 2026. No other catalogue keeps this.

7 Nov 2 tool descriptions were rewritten quoapi.describe, quoapi.search

7 Nov a tool disappeared quoapi.status

7 Nov a tool appeared quoapi.inspect

7 Nov a tool changed version

6 Nov 4 tool descriptions were rewritten11 times that day quoapi.describe, quoapi.execute, quoapi.search and 1 more

6 Nov 4 tools changed the parameters they ask for9 times that day quoapi.describe, quoapi.execute, quoapi.search and 1 more

6 Nov a tool changed version

and 12 more, back to 6 November 2026

QuoAPI does not always answer

Over the last week it answered 18.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://quoapi.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://quoapi.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://quoapi.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://quoapi.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://quoapi.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

quoapi

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 test credentials or provider reachability. Unknown or MCP-ineligible handles return capability_not_mcp_visible. Use quoapi.inspect for runtime health, not contracts.

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 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.

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 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.

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 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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

quoapi.status

removed 7 Nov 2026

Endpoints

URL	Transport	State	Latency	Checked
https://quoapi.com/mcp	streamable-http	answering	27 ms	9 min ago

Alternatives to QuoAPI

same job, measured the same way

Scrapegraph MCP

by scrapegraphai

AI-powered web scraping and data extraction capabilities through ScrapeGraph API

190 installs/wk local only

MCP Gateway

by mikkoparkkola

Universal MCP gateway with Meta-MCP discovery, routing, and REST API capabilities.

local only

Apiosk Connect

by obcraft

Discover, pay for, execute, and publish APIs through Apiosk.

144 installs/wk 3 tools answering

Pollinations

by pollinations

Access Pollinations models and API capabilities through agent tools.

answering

Agentel Network

by agentel-tech

Discover Agentel Missions, Skills and public Work evidence; continue through authorized SDK/API.

6 tools answering

GaugeMesh

by aliengineering-byte

Route MCP capabilities through deterministic identity, policy, budget, and deadline constraints.

local only

NoInfra MCP

by noinfra

Discover managed business agents. Private capabilities require owner authorization and eligibility.

4 tools answering

Physical Capability Cloud

by capability

Discover, hire, and verify real-world physical capability through MCP.

256 tools answering

QuoAPI — questions

Answers built from our own checks of this server.

What can QuoAPI do?

It exposes 4 tools, read directly from the server on our last check. Among them: quoapi.describe, quoapi.execute, quoapi.inspect, quoapi.search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is QuoAPI working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 81 ms. The bar chart above shows every period we have measured.

Did QuoAPI ever remove tools?

Yes. quoapi.status is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect QuoAPI?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does QuoAPI need an API key?

No. QuoAPI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is QuoAPI?

It answers our handshake in 81 ms on average, which is faster than 98% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.