RealWorldAPIs
REMOTE · MCP.REALWORLDAPIS.COM · SCANNED SEP 29
Evidence-first registry of real-world APIs for AI agents, with verified metadata and comparison.
Available components
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1129 tokens (~282/item across 4 items; 4 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the RealWorldAPIs MCP server?
RealWorldAPIs is a hosted endpoint at https://mcp.realworldapis.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 · mcp.realworldapis.com
claude mcp add --transport http com-realworldapis-realworldapis 'https://mcp.realworldapis.com/mcp'
{
"mcpServers": {
"com-realworldapis-realworldapis": {
"url": "https://mcp.realworldapis.com/mcp"
}
}
} {
"servers": {
"com-realworldapis-realworldapis": {
"type": "http",
"url": "https://mcp.realworldapis.com/mcp"
}
}
} [mcp_servers.com-realworldapis-realworldapis] url = "https://mcp.realworldapis.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-realworldapis-realworldapis": {
"type": "remote",
"url": "https://mcp.realworldapis.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-realworldapis-realworldapis --url 'https://mcp.realworldapis.com/mcp' --transport streamable-http
mcp_servers:
com-realworldapis-realworldapis:
url: "https://mcp.realworldapis.com/mcp" {
"McpServers": {
"com-realworldapis-realworldapis": {
"Transport": "http",
"Url": "https://mcp.realworldapis.com/mcp"
}
}
} assistant mcp add com-realworldapis-realworldapis -t streamable-http -u 'https://mcp.realworldapis.com/mcp'
{
"mcpServers": {
"com-realworldapis-realworldapis": {
"type": "http",
"url": "https://mcp.realworldapis.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 65
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 29 Sept 2026 · Probed https://mcp.realworldapis.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=realworldapis.com | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 79192931d76fb86a132593b8600ffc29 |
| SANs: realworldapis.com, mcp.realworldapis.com, *.mcp.realworldapis.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 mcp.realworldapis.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| realworldapis.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://mcp.realworldapis.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.realworldapis.com/mcp | Inconclusive | 405 |
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 →
compare_apis Compare APIs ~241
Compare 2–8 already-known APIs side by side using only canonical RealWorldAPIs fields. Use this after find_api_for_task or search_apis has produced candidates; use get_api when only one record is needed. If fields is omitted, the tool returns the default core comparison fields: provider, category, capabilities, agent capabilities, authentication, protocol statuses, readiness and verification/actionability fields, excluding long description and URLs. Unresolved names/slugs are listed in unresolved; at least two identifiers must resolve. No missing value is inferred and Unknown remains Unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| apis | array | yes | Required list of 2–8 API slugs or names. Exact matches are preferred; unique partial matches are accepted. Unresolved identifiers are reported separately, and the call fails if fewer than two records… |
| fields | array | – | Optional fields to compare. If omitted or empty, the tool uses the default core fields: provider, category, capabilities, agent_capabilities, auth_methods, openapi, mcp, a2a, x402, llms_txt, agent_re… |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_policy | string | yes | – |
| fields | array | yes | – |
| method | string | yes | – |
| name | string | yes | – |
| records | array | yes | – |
| unresolved | array | yes | – |
No examples provided.
find_api_for_task Find API for Task ~271
Find the best APIs for a natural-language physical-world task. Use this for open-ended task or outcome-based recommendations; use search_apis when you already know exact filters, get_api for one known API, or compare_apis for known candidates. Returns an authoritative canonical structured_results shortlist plus a best-effort AI comparison restricted to that shortlist. The canonical browser-parity flow always returns five structured candidates: limit is retained only for backward compatibility. requirements.categories, capabilities, mcp, openapi and auth are added as task hints; free_tier and min_readiness are accepted for compatibility but are not hard filters. Unknown remains Unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Backward-compatible parameter. The canonical browser-parity workflow always produces five structured candidates before the AI comparison, even when another value is supplied. |
| requirements | object | – | Optional compatibility hints appended to the task before canonical ranking. categories, capabilities, mcp, openapi and auth influence the effective query. free_tier and min_readiness are accepted for… |
| task | string | yes | Required natural-language goal or workflow, for example 'connect to a car and predict weather on the route'. Describe the desired outcome rather than naming a specific API. |
| Name | Type | Req | Description |
|---|---|---|---|
| ai | object | yes | – |
| ai_comparison | object|null | – | Best-effort grounded explanation of only the structured_results candidates. |
| compatibility_warnings | array | – | – |
| coverage_status | string | – | – |
| coverage_warnings | array | – | – |
| effective_query | string | – | – |
| engine_version | string | – | – |
| grounding_policy | object | yes | – |
| method | string | – | – |
| name | string | yes | – |
| snapshot_date | string|null | – | – |
| source_endpoints | object | – | – |
| structured_results | array | yes | Canonical deterministic shortlist. This is the authoritative result set. |
| task | string | yes | – |
| timing_ms | object | – | – |
No examples provided.
get_api Get API ~122
Retrieve one canonical verified API record when you already know its name or slug. Exact slug or exact API name is preferred; a partial identifier is accepted only when it uniquely resolves to one record. Missing or ambiguous identifiers return an error directing the agent to search_apis. Use compare_apis instead when you want fields from multiple known APIs.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Required API slug or API name. Exact matches are preferred; a unique case-insensitive partial slug/name match is accepted. If it is ambiguous or missing, use search_apis to find the exact identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_policy | string | yes | – |
| name | string | yes | – |
| record | object | yes | – |
| source | string | yes | – |
No examples provided.
search_apis Search APIs ~433
Search the canonical registry when you already know keywords or exact requirements. All supplied filter groups combine with AND logic; array capability filters require every supplied value, and protocol fields match the exact Yes/No/Unknown status, so Unknown never satisfies Yes. Results are sorted by agent_readiness_score descending and then API name, with 1–20 results returned (default 10); total_matches reports the complete match count and there is no pagination. Use find_api_for_task for open-ended task recommendations, get_api for one known API, and compare_apis for side-by-side inspection.
| Name | Type | Req | Description |
|---|---|---|---|
| a2a | string | – | Exact A2A evidence status required for a match. |
| agent_actionable | boolean | – | When true, require agent_actionable = true. False does not exclude actionable records; omit this field unless you need the positive requirement. |
| agent_capabilities | array | – | Agent capability dimensions that must all be explicitly present on a record. |
| capabilities | array | – | Capability terms that must all be present in the record's verified capabilities. Matching is case-insensitive and allows a capability string to contain the supplied term. |
| categories | array | – | Exact category names. Supplying multiple category values allows a record to match any listed category; this category condition still combines with every other supplied filter group using AND logic. |
| limit | integer | – | Maximum number of matching records returned. Results are sorted by readiness descending then API name. total_matches still reports the full count. No pagination is currently exposed. |
| llms_txt | string | – | Exact llms.txt evidence status required for a match. |
| mcp | string | – | Exact MCP evidence status required for a match. |
| min_readiness | integer | – | Strict minimum agent-readiness score. Records below this score are excluded. |
| openapi | string | – | Exact OpenAPI evidence status required for a match. |
| query | string | – | Optional case-insensitive text search across API name, provider, category, description, capabilities, agent capabilities and authentication fields. |
| x402 | string | – | Exact x402 evidence status required for a match. |
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_policy | string | yes | – |
| filters | object | yes | – |
| method | string | yes | – |
| name | string | yes | – |
| query | string | – | – |
| results | array | yes | – |
| returned | integer | yes | – |
| total_matches | integer | yes | – |
No examples provided.
What is the RealWorldAPIs MCP server?
RealWorldAPIs is an MCP server listed in the public MCP registry as com.realworldapis/realworldapis. Evidence-first registry of real-world APIs for AI agents, with verified metadata and comparison. This page covers its hosted endpoint (https://mcp.realworldapis.com/mcp).
Is the RealWorldAPIs MCP server safe to use?
RealWorldAPIs scores 66 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 RealWorldAPIs MCP server expose?
RealWorldAPIs exposes 4 tools: find_api_for_task, search_apis, get_api, compare_apis. Their descriptions and schemas cost roughly 1,067 tokens of context every time the server is loaded.
Does the RealWorldAPIs MCP server require authentication?
No. We connected to RealWorldAPIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RealWorldAPIs MCP server still maintained?
RealWorldAPIs is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.