Validate Formhaus form definitions and simulate multi-step paths against the real engine.
Nothing to run from here
RealWorldAPIs is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Evidence-first registry of real-world APIs for AI agents, with verified metadata and comparison.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http realworldapis-mcp https://mcp.realworldapis.com/mcp
# 2 — ask your agent for something these tools do
# find_api_for_task, search_apis, search_capabilities and 3 more
RealWorldAPIs costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
realworldapis1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http realworldapis-mcp https://mcp.realworldapis.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 engine now appl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| requirements | object | no | Optional task requirements appended before canonical ranking. categories and capabilities shape task intent. mcp=Yes, openapi=Yes and auth are expressed as hard task requirements and are evaluated aga |
| limit | integer | no | Backward-compatible parameter. The canonical browser-parity workflow always produces five structured candidates before the AI comparison, even when another value is supplied. |
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 include each API's capability_summary and direct decision-profile URL. Results are sorted by agent_readiness_sc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional case-insensitive text search across API name, provider, category, description, capabilities, agent capabilities and authentication fields. |
| categories | array | no | 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. |
| capabilities | array | no | 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. |
| agent_capabilities | array | no | Agent capability dimensions that must all be explicitly present on a record. |
| openapi | string | no | Exact OpenAPI evidence status required for a match. |
| mcp | string | no | Exact MCP evidence status required for a match. |
| a2a | string | no | Exact A2A evidence status required for a match. |
| x402 | string | no | Exact x402 evidence status required for a match. |
| llms_txt | string | no | Exact llms.txt evidence status required for a match. |
| min_readiness | integer | no | Strict minimum agent-readiness score. Records below this score are excluded. |
| agent_actionable | boolean | no | When true, require agent_actionable = true. False does not exclude actionable records; omit this field unless you need the positive requirement. |
| limit | integer | no | 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. |
Search the canonical 770-capability Verified/High decision graph directly. Use this when the question is about what an agent can actually do and under what execution conditions: task/capability text, API, category, action type, acted-on object, human approval, physical consequence, irreversibility, sandbox, hardware dependency, access friction or setup. All supplied filter groups combine with AND
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Optional case-insensitive text search across API/provider/category, capability key/name, primitive/action type, object, execution fields and constraints. Search terms may match across different capabi |
| api_slugs | array | no | Optional API slugs. Multiple values are OR within this filter. |
| categories | array | no | Exact category labels. Multiple values are OR within this filter. |
| primitives | array | no | Exact capability primitives such as Observe, Locate, Predict, Plan, Control or Act. |
| action_types | array | no | Exact action types such as Read, Search, Analyze, Route or Control. |
| actionability | array | no | Exact actionability labels such as Information only, Planning or Physical action. |
| object | string | no | Case-insensitive substring match on the object acted upon, such as smart lock, parcel or charging session. |
| human_approval | array | no | Exact approval labels, for example Required, Not required, Depends on action or Unknown. |
| physical_consequence | boolean | no | When supplied, require the exact physical-consequence boolean. |
| irreversible_high_consequence | boolean | no | When supplied, require the exact irreversible/high-consequence boolean. |
| sandbox | array | no | Exact sandbox/test-environment labels, including Unknown when desired. |
| hardware_dependency | array | no | Exact hardware-dependency labels. |
| access_friction | array | no | Exact access-friction labels such as Self-service signup, Sales contract or Hardware ecosystem. |
| agent_setup | array | no | Exact agent-setup labels such as Fully self-service or Human setup required. |
| limit | integer | no | Maximum capability rows returned. total_matches reports the full match count. |
Verify whether one specific API can satisfy one exact requirement using the canonical Verified/High capability graph plus linked assertion evidence. Returns YES, NO, PARTIAL or UNKNOWN with matched capability, access/setup prerequisites, approval, safety, reversibility, reliability, coverage and other requested dimensions; direct provider facts remain distinct from inferred policy assertions. Unkn
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api | string | yes | Exact API slug or API name, for example nuki-web-api or Nuki Web API. |
| requirement | string | yes | Specific requirement to verify, for example 'remotely unlock a smart lock without human approval'. |
| location | string | no | Optional geographic coverage requirement, for example Sweden. Coverage is returned as Unknown/Partial when the normalized capability graph does not contain enough location evidence. |
Retrieve one canonical API decision profile when you already know its name or slug. The response includes the full Verified/High capability profile with execution, access, approval, reversibility, physical-consequence and evidence fields. Exact slug or exact API name is preferred; a partial identifier is accepted only when it uniquely resolves to one record.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
Compare 2–8 already-known APIs side by side using canonical catalog fields plus capability-graph summary fields such as verified capability count, physical consequences, approval relevance and irreversibility. Use get_api for the full decision profile of one API and search_capabilities for capability-level filtering. No missing value is inferred and Unknown remains Unknown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Optional fields to compare. The default includes core catalog fields plus verified capability count, physical-consequence count, approval-relevant count, irreversible/high-consequence count and the de |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RealWorldAPIs or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 3.0.1.
3.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish RealWorldAPIs can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.