Skip to content
mcp/skillhub

Autopia MCP Server

by maydaytreyio.github.MaydayTrey/autopiav0.3.1

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

0remoteofficial registry

context tax

~1,921 tok/turn9 tools

security

97/100

cold start

hosted

freshness

Active1d ago

Our reading of Autopia, from the data

Autopia is an MCP server from maydaytrey, listed in the official MCP Registry.

Its 9 tools add about 1,921 tokens to every model turn (measured 2026-10-19).

Maintenance is active: the last public signal was in the last day (2026-10-17).

It runs as a hosted endpoint, so there is nothing to install.

Install Autopia MCP server

Install in Claude Code

claude mcp add --transport http autopia https://autopia-mcp.onrender.com/mcp

Remote endpoints

  • streamable-httphttps://autopia-mcp.onrender.com/mcp

Context tax

Connecting this server adds ~1,921 tokens of tool definitions to every model turn (moderate, 9 tools). Measured 2026-10-19 via its hosted endpoint; o200k tokenizer, worst case for clients that load all tools up front. How we measure

ModelPer 1,000 turnsWith prompt caching
Claude Opus 5.5$7.68$0.384
Claude Sonnet 5.5$3.84$0.384
Claude Haiku 5.5$0.192—

Input prices as of 2026-10-06. Excludes your own prompt and output.

Tools (9)

  • get_tool_docs278 tok

    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.

  • get_tool_knowledge214 tok

    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.

  • search_claims193 tok

    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.

  • request_target168 tok

    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.

  • get_divergences135 tok

    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.

  • get_version_diff132 tok

    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.

  • list_versions107 tok

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

  • get_request_status75 tok

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

  • list_tools65 tok

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

Security signals

97/100 — no known issues found as of 2026-10-19, from the checks below. This is not a guarantee of safety; review what a server can do before connecting it.

Deductions

  • No security policy (SECURITY.md)-3

Checks

  • ✓Repository hygiene (archived, activity, license, security policy)
  • ✓Tool descriptions (prompt-injection and hidden-text heuristics)
  • ○Package metadata (install scripts, provenance) — pending
  • ○Source scan (secrets, CVEs, risky code) by vectra-guard — pending

Scan it yourself before installing with vectra-guard, the open-source agent security CLI. Scoring rules

Freshness

Active — last maintenance signal 1d ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-10-17 · 1d ago · GitHub

  2. Latest release

    no data · GitHub

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-10-12 · 6d ago · official registry · v0.3.1

FAQ

›How do I install the Autopia MCP server in Claude Code?

Run: claude mcp add --transport http autopia https://autopia-mcp.onrender.com/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Autopia require an API key?

No required environment variables are declared in its published metadata.

›Can I use Autopia as a remote (hosted) MCP server?

Yes. It is a hosted MCP server; connect to its URL with any client that supports remote MCP.

›Is Autopia in the official MCP registry?

Yes, as io.github.MaydayTrey/autopia.

›How many tokens does Autopia add to my context?

Its tool definitions total about 1,921 tokens, resent on every turn.

Sources and method

Official MCP Registry entry
updated 2026-10-12
GitHub repository
fetched 2026-10-19
Last checked against all sources
2026-10-19

The description, packages and links come from the maintainer's own published metadata. Token cost, security signals, freshness and the reading above are MCPSkillHub's own measurements; see the methodology. Spot an error? Request a correction or claim the listing.