QuoAPI MCP server
com.quoapi/mcpquoapi.comstreamable-httpv0.29.0Scanned
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
4 tools: 1 can delete or cancel things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 4 findings
Tools listed without sign-in. Remote posture
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the QuoAPI MCP server can do
The QuoAPI MCP server is published by quoapi.com, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: quoapi.execute). 3 tools only read.
2 tools bring in text other people can write (quoapi.search and quoapi.execute).
The fixed checks matched 4 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 21, 2026, version 0.29.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Deletes or cancels 1Claude Code: deny
quoapi.executeExecute an authorized handle using the inputSchema from quoapi.describe.Reads text others write2 findings
Why it is in this group
- The name "quoapi.execute" says "execute": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...am route; auth_mode selects a supported credential model—none bypasses access gates. Reuse..."
- Info
The input schema at properties.auth_mode.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.auth_mode.description: "Optional upstream credential mode: QUO_MANAGED (QuoAPI-managed), CON..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
quoapi.describeRead the DESIGN-TIME contract for an exact handle from quoapi.search (e.g.1 finding
Why it is in this group
- The name "quoapi.describe" says "describe": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...arges are performed; this does not test credentials or provider reachability. Unknown or MC..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
quoapi.inspectRead-only RUNTIME STATUS of the QuoAPI MCP gateway, not a provider execution.1 finding
Why it is in this group
- The name "quoapi.inspect" says "inspect": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...xecution, a live upstream health probe, credentials or tenant authorization. Use quoapi.des..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
quoapi.searchFind canonical QuoAPI capability handles by intent, ID or provider; catalog metadata are not upstream API results.Reads text others writeNo findings
Why it is in this group
- The name "quoapi.search" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://quoapi.com/.well-known/oauth-protected-resource
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://quoapi.com/mcp: tools/list returned 4 tools to an anonymous client, including quoapi.execute (destructive)
Posture changes
- Nov 11, 2026
- HTTP status of an anonymous initialize: 400 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
Findings
Matches of fixed checks, with the text they matched.
- Infoquoapi.describe
The description mentions "credentials".
What this check looks forMatched text
description: "...arges are performed; this does not test credentials or provider reachability. Unknown or MC..."
- Infoquoapi.execute
The description mentions "credential".
What this check looks forMatched text
description: "...am route; auth_mode selects a supported credential model—none bypasses access gates. Reuse..."
- Infoquoapi.execute
The input schema at properties.auth_mode.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.auth_mode.description: "Optional upstream credential mode: QUO_MANAGED (QuoAPI-managed), CON..."
- Infoquoapi.inspect
The description mentions "credentials".
What this check looks forMatched text
description: "...xecution, a live upstream health probe, credentials or tenant authorization. Use quoapi.des..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 400 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 1 more).View diff
- HTTP status of an anonymous initialize: 400 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
Tools1 added, 1 removed, 3 changed.+1 added−1 removed~3 changedView diff
- Added:quoapi.inspectOnly reads
- Removed:quoapi.status
- Changed:quoapi.describeOnly readsdescriptioninputSchema
- Changed:quoapi.executeDeletes or cancelsdescriptioninputSchema
- Changed:quoapi.searchOnly readsdescriptioninputSchema
Tools4 changed.~4 changedView diff
- Changed:quoapi.describeOnly readsdescriptioninputSchema
- Changed:quoapi.executeDeletes or cancelsdescriptioninputSchemaannotations
- Changed:quoapi.searchOnly readsdescriptioninputSchema
- Changed:quoapi.statusOnly readsdescriptioninputSchema
Install
Pinned to version 0.29.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http quoapi https://quoapi.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http quoapi https://quoapi.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__quoapi__quoapi_search",
"mcp__quoapi__quoapi_describe",
"mcp__quoapi__quoapi_inspect"
],
"ask": [],
"deny": [
"mcp__quoapi__quoapi_execute"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as quoapi. Review it before you use it.
Capability tags behind 2 rules
- mcp__quoapi__quoapi_search untrusted-input
- mcp__quoapi__quoapi_execute untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.quoapi/mcp/verify?hash=011b563abe121dfb448af54cbbc8692c79f0549a20d8df55fae0088bd1e64eb7" | jq -e '.changed == false'Pinned hash 011b563abe12, from Nov 21, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.quoapi/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.quoapi/mcp)Source: MCP Registry. Synced Nov 7, 2026, 00:17 UTC.
QuoAPI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the QuoAPI MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the QuoAPI MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: quoapi.execute.
Can the QuoAPI MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the QuoAPI MCP server have?
- 4 tools: 1 destructive, 3 read. quoapi.execute, quoapi.search, quoapi.describe and quoapi.inspect.
Does the QuoAPI MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the QuoAPI MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the QuoAPI MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 7, 2026. Every change is on this page and in its Atom feed.