# Autopia (remote · autopia-mcp.onrender.com)

Verified, reproduced behavior of public HTTP APIs: spec gaps, errors, pagination, auth.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `autopia-mcp.onrender.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/maydaytrey-autopia/autopia-mcp.md), [page](https://verifymcp.io/servers/maydaytrey-autopia/autopia-mcp)

## Channel facts

- Endpoint: `https://autopia-mcp.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 85/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 54% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http maydaytrey-autopia 'https://autopia-mcp.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "maydaytrey-autopia": {
      "url": "https://autopia-mcp.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "maydaytrey-autopia": {
      "type": "http",
      "url": "https://autopia-mcp.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.maydaytrey-autopia]
url = "https://autopia-mcp.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maydaytrey-autopia": {
      "type": "remote",
      "url": "https://autopia-mcp.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add maydaytrey-autopia --url 'https://autopia-mcp.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  maydaytrey-autopia:
    url: "https://autopia-mcp.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "maydaytrey-autopia": {
      "Transport": "http",
      "Url": "https://autopia-mcp.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add maydaytrey-autopia -t streamable-http -u 'https://autopia-mcp.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "maydaytrey-autopia": {
      "type": "http",
      "url": "https://autopia-mcp.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 69, +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.

### 2026-10-14 (score 68, +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.

### 2026-10-13 (score 67, +6)

- [security improvement] 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
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “get_tool_docs” added an optional parameter “full”
- [cosmetic] “get_tool_docs” reworded the description of “brief”

### 2026-10-12 (score 61)

First indexed and scored.

## MCP tools (9)

### `list_tools` (~39 tokens)

List tools

The APIs the compendium covers: each with the hosts its trials hit, trust tier, version count, and counts of verified claims and spec divergences.

### `list_versions` (~69 tokens)

List versions

The spec versions recorded for one API, newest first, each fingerprinted by its spec hash. The ids identify versions for get_version_diff.

Input parameters:

- `tool` (string, required): tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com)

### `get_tool_knowledge` (~156 tokens)

Get tool knowledge

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.

Input parameters:

- `kind` (string): required | type | auth | pagination | error_behavior | response_shape | undocumented_constraint | undocumented | other
- `limit` (integer): default 100
- `offset` (integer)
- `tool` (string, required): 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

### `get_divergences` (~97 tokens)

Get divergences

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.

Input parameters:

- `tool` (string, required): tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com)
- `verbose` (boolean)
- `version` (integer)

### `search_claims` (~148 tokens)

Search claims

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `tool` (string): tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com)
- `verbose` (boolean)

### `get_tool_docs` (~231 tokens)

Get tool docs

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.

Input parameters:

- `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, required): tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com)
- `version` (integer)

### `get_version_diff` (~88 tokens)

Get version diff

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.

Input parameters:

- `from_version` (integer, required)
- `to_version` (integer, required)
- `tool` (string, required): tool name (e.g. github-rest), or the host / URL you are about to call (e.g. api.github.com)

### `request_target` (~127 tokens)

Request a target

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.

Input parameters:

- `target` (object, required): the target definition; see targets/*.json in the repo for examples

### `get_request_status` (~40 tokens)

Get request status

Status of a target request (pending, running, done or failed), with the run id and summary once processed.

Input parameters:

- `request_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/maydaytrey-autopia/autopia-mcp#diagnostics

## Score history

- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 67
- 2026-10-12: 61

## Common questions

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

## Links

- Remote endpoint: https://autopia-mcp.onrender.com/mcp
- Repository: https://github.com/MaydayTrey/autopia
- Website: https://maydaytrey.github.io/autopia/
- Changelog RSS feed: https://verifymcp.io/servers/maydaytrey-autopia/autopia-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/maydaytrey-autopia/autopia-mcp.json
- HTML version of this page: https://verifymcp.io/servers/maydaytrey-autopia/autopia-mcp