Autopia
REMOTE · AUTOPIA-MCP.ONRENDER.COM
Verified, reproduced behavior of public HTTP APIs: spec gaps, errors, pagination, auth.
Available components
Last scanned (22 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1467 tokens (~163/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +6
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “search_claims” rewrote its description, which is the text the model reads security
- Tool “get_divergences” rewrote its description, which is the text the model reads security
- Tool “get_request_status” rewrote its description, which is the text the model reads security
- Tool “get_tool_docs” rewrote its description, which is the text the model reads security
- Tool “get_tool_knowledge” rewrote its description, which is the text the model reads security
- Tool “get_version_diff” rewrote its description, which is the text the model reads security
- Tool “list_tools” rewrote its description, which is the text the model reads security
- Tool “list_versions” rewrote its description, which is the text the model reads security
- Tool “request_target” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “get_tool_docs” added an optional parameter “full” cosmetic
- “get_tool_docs” reworded the description of “brief” cosmetic
- 12 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://autopia-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of autopia-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://autopia-mcp.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://autopia-mcp.onrender.com/mcp | HTTPS enforced | 301 | https://autopia-mcp.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_divergences Get divergences ~97
Where the live API contradicts its own OpenAPI spec: documented limits not enforced, types not validated, required parameters not required, enums accepting other values. Compact evidence; verbose=true adds response previews.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com) |
| verbose | boolean | – | – |
| version | integer | – | – |
No output schema declared.
No examples provided.
get_request_status Get request status ~40
Status of a target request (pending, running, done or failed), with the run id and summary once processed.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | integer | yes | – |
No output schema declared.
No examples provided.
get_tool_docs Get tool docs ~231
The verified behavior sheet for an API: Markdown built only from verified claims, with spec contradictions first, then sibling differences, undocumented rules, and per-endpoint behavior (error shapes, pagination, validation, auth), every line citing trial ids. Accepts a tool name, a host, or the full URL about to be called; a URL or path scopes the sheet to that endpoint plus a one-line index of the others. Brief by default (what would change the request); full=true adds per-parameter validation, response shapes and all evidence ids.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | boolean | – | deprecated: the default; brief=false is the same as full=true |
| full | boolean | – | the whole sheet: per-parameter validation, response shapes, all evidence ids |
| path | string | – | request path to scope to one endpoint, e.g. /repos/github/rest-api-description/issues; template segments match anything |
| tool | string | yes | tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com) |
| version | integer | – | – |
No output schema declared.
No examples provided.
get_tool_knowledge Get tool knowledge ~156
Every verified claim about an API as structured records (latest version by default): paginated, filterable by kind, spec divergences flagged, each with compact evidence (trial id, probe, status, request line). verbose=true adds response previews.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | required | type | auth | pagination | error_behavior | response_shape | undocumented_constraint | undocumented | other |
| limit | integer | – | default 100 |
| offset | integer | – | – |
| tool | string | yes | tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com) |
| verbose | boolean | – | – |
| version | integer | – | tool_version id; default latest |
No output schema declared.
No examples provided.
get_version_diff Get version diff ~88
What changed in verified behavior between two spec versions of an API (changed, added and removed claims), as opposed to what changed in the spec text.
| Name | Type | Req | Description |
|---|---|---|---|
| from_version | integer | yes | – |
| to_version | integer | yes | – |
| tool | string | yes | tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com) |
No output schema declared.
No examples provided.
list_tools List tools ~39
The APIs the compendium covers: each with the hosts its trials hit, trust tier, version count, and counts of verified claims and spec divergences.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_versions List versions ~69
The spec versions recorded for one API, newest first, each fingerprinted by its spec hash. The ids identify versions for get_version_diff.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com) |
No output schema declared.
No examples provided.
request_target Request a target ~127
Queues a public, read-only, credential-free API for probing, from a target object { name, spec_url (OpenAPI 3 document), category?, include_paths?, baseline? (valid values for required params per path), optional_values?, server? }. The spec is fetched and parsed and the battery planned immediately; probing runs rules-only on the worker's next pass. Requires a per-user key; quota 3 requests per key per day. Returns a request id for get_request_status.
| Name | Type | Req | Description |
|---|---|---|---|
| target | object | yes | the target definition; see targets/*.json in the repo for examples |
No output schema declared.
No examples provided.
search_claims Search claims ~148
Full-text search over verified claims by host and symptom, e.g. "github per_page 500", "npm search size 0", "is latitude required on /v1/forecast": the lookup for an unexpected 4xx/5xx, a parameter that seems ignored, an odd page, or wrong filter results. Optionally restricted to one API (name, host or URL). Compact evidence unless verbose=true.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| tool | string | – | tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com) |
| verbose | boolean | – | – |
No output schema declared.
No examples provided.
How do I install the Autopia MCP server?
Autopia is a hosted endpoint at https://autopia-mcp.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · autopia-mcp.onrender.com
claude mcp add --transport http maydaytrey-autopia 'https://autopia-mcp.onrender.com/mcp'
What is the Autopia MCP server?
Autopia is an MCP server listed in the public MCP registry as io.github.MaydayTrey/autopia. Verified, reproduced behavior of public HTTP APIs: spec gaps, errors, pagination, auth. This page covers its hosted endpoint (https://autopia-mcp.onrender.com/mcp).
Is the Autopia MCP server safe to use?
Autopia scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Autopia MCP server expose?
Autopia exposes 9 tools: list_tools, list_versions, get_tool_knowledge, get_divergences, search_claims, and 4 more. Their descriptions and schemas cost roughly 995 tokens of context every time the server is loaded.
Does the Autopia MCP server require authentication?
No. We connected to Autopia without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Autopia MCP server still maintained?
Autopia is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.