AnyAPI
REMOTE · API.GETANYAPI.COM · 3 COMPONENTS
Hundreds of scraping & data APIs through one key. USD pay-per-request, normalized schemas, failover.
Available components
Last scanned (3 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2336 tokens (~233/item across 10 items; 10 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 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.
- 10 Oct 26 0
- Tool “report_bug” rewrote its description, which is the text the model reads security
- Tool “send_feedback” rewrote its description, which is the text the model reads security
- Tool “search_apis” rewrote its description, which is the text the model reads security
- Tool “run_api” rewrote its description, which is the text the model reads security
- Tool “get_api” rewrote its description, which is the text the model reads security
- Tool “get_request” rewrote its description, which is the text the model reads security
- Tool “list_apis” rewrote its description, which is the text the model reads security
- Tool “quote_api” rewrote its description, which is the text the model reads security
- Tool “read_result” rewrote its description, which is the text the model reads security
- Schema quality: 347 → 233 ▲ functional
- “read_result” reworded the description of “context” cosmetic
- “report_bug” reworded the description of “contact” cosmetic
- “send_feedback” reworded the description of “context” cosmetic
- “send_feedback” reworded the description of “contact” cosmetic
- “search_apis” reworded the description of “context” cosmetic
- “run_api” reworded the description of “context” cosmetic
- “report_bug” reworded the description of “context” cosmetic
- “get_api” reworded the description of “context” cosmetic
- “get_balance” reworded the description of “context” cosmetic
- “get_request” reworded the description of “context” cosmetic
- “list_apis” reworded the description of “context” cosmetic
- “quote_api” reworded the description of “context” cosmetic
- “quote_api” reworded the description of “input” cosmetic
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 2 Oct 26 0
- “read_result” reworded the description of “max_items” cosmetic
- “read_result” reworded the description of “fields” cosmetic
- “run_api” reworded the description of “fields” cosmetic
- “run_api” reworded the description of “max_items” cosmetic
4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 29 Sept 26 0
- Tool “run_api” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Sept 26 0
- Tool “search_apis” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “search_apis” reworded the description of “query” cosmetic
- “search_apis” made “query” optional cosmetic
- 4 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Transport: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
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 5 Nov 2026 · Probed https://api.getanyapi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.getanyapi.com | CN=YE1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 54d1b673f6dae493726beb9d9ccb4f9ea12 |
| SANs: api.getanyapi.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.getanyapi.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getanyapi.com. | present | 2371 | 13 | Verified |
| api.getanyapi.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", scope="run balance:read", resource_metadata="https://api.getanyapi.com/.well-known/oauth-protected-resource/mcp"
Bearer error="invalid_token", scope="run balance:read", resource_metadata="https://api.getanyapi.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| www-authenticate | Bearer scope="run balance:read", resource_metadata="https://api.getanyapi.com/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://api.getanyapi.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.getanyapi.com/mcp |
| Authorisation server | https://api.getanyapi.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.getanyapi.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.getanyapi.com/mcp | HTTPS enforced | 308 | https://api.getanyapi.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_api Get API details ~134
Get the full definition of one API by API slug, including its normalized input/output JSON schemas, per-request and per-1,000-request USD pricing on every source, and nullable trailing-30-day latency p50/p95/p99 with the successful sample count. Latency percentiles describe observed successful requests; p99 is an observation, not a maximum or a client timeout guarantee. Entries with heavy:true produce large API responses.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| sku_id | string | yes | the API SKU slug to describe |
| Name | Type | Req | Description |
|---|---|---|---|
| scraper | object | yes | the API definition with input/output schemas |
No examples provided.
get_balance Check wallet balance ~62
Get the remaining wallet balance (in USD) for the AnyAPI key supplied as a Bearer token. Requires a valid AnyAPI key.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| Name | Type | Req | Description |
|---|---|---|---|
| balanceUsd | number | yes | remaining wallet balance for this API key, in USD |
No examples provided.
get_request Check a request ~94
Inspect or resume a durable AnyAPI request by request_id. This reads AnyAPI's stored state and never repeats the paid provider dispatch. While status is queued or running, retryAfterSeconds gives the minimum interval between status checks.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| request_id | string | yes | durable request identifier returned by run_api |
| Name | Type | Req | Description |
|---|---|---|---|
| costUsd | number | yes | amount charged to the wallet in USD |
| error | null|object | – | safe AnyAPI failure code when durable work failed |
| hint | string | – | optional result caveat. 'large_result:' identifies a large response; fields/max_items/summary reduce response size without changing cost. 'paging_unavailable:' means the source cannot return a nextCu… |
| items | integer | yes | number of result rows returned; an API that returns one record counts it as one row. For per-result APIs the per-item cost is charged against this; for input-priced APIs (perItemUnit != result) the c… |
| jqError | string | – | present only when a jq expression failed; output then holds the full unshaped result and this explains why the reshape did not apply |
| nextAction | null|object | – | stored-request retrieval coordinates and polling interval present while durable work is pending |
| output | – | yes | normalized output payload |
| provider | string | yes | the provider serving the request (AnyAPI) |
| replayed | boolean | yes | true when this response replays an identical earlier call (same API, same input) from the last few minutes instead of running again: nothing new was executed and costUsd restates the original charge,… |
| requestId | string | – | durable request identifier for stored status and result retrieval without repeating the paid provider dispatch |
| resultId | string | – | opaque handle to the full result, cached ~15 min; identifies the paid result available for free reshaping without another execution or charge. Absent when the result was too large to cache |
| serviceOutcome | string | – | end-to-end AnyAPI service outcome when known |
| settlementState | string | – | payment settlement state when known; independent of durable request status |
| source | null|object | – | the source that served this request; its id is accepted by 'source' for preference or 'ignoreSources' for exclusion. Absent when no source identity applies |
| status | string | – | durable request status: queued, running, succeeded, failed, or expired |
No examples provided.
list_apis Browse APIs ~117
Browse available AnyAPI APIs as lightweight summaries (id, name, category, USD pricing), optionally filtered by category. Descriptions and schemas are omitted to keep catalog responses small. Each pricing offer carries both `maxUsd` (billed per request) and `maxPer1kUsd` (the same price per 1,000 requests).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | optional category slug to filter by |
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| Name | Type | Req | Description |
|---|---|---|---|
| scrapers | null|array | yes | matching APIs (lightweight summaries: no description or schemas) |
No examples provided.
quote_api Quote a price ~176
Get the exact input-aware execution price for an API, free and without a key. Nothing is charged or executed. `sku_id` and `input` identify the proposed execution; pricing resolves exactly as it does for execution, and input validation can return invalid_input without a charge. Returns maxCostUsd (the ceiling reserved), minCostUsd (the likely charge), and the base/per-item breakdown explaining why they differ. These are USD amounts for this one call, not per-1,000-request catalog comparison rates.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| input | object | yes | the exact normalized input payload being priced; the quote resolves pricing the same way execution does |
| sku_id | string | yes | the API SKU slug to price |
| Name | Type | Req | Description |
|---|---|---|---|
| baseUsd | number | yes | fixed cost per call in USD, charged regardless of count |
| exact | boolean | yes | true when the price is exact (minCostUsd == maxCostUsd): a flat SKU or a sealed page |
| maxCostUsd | number | yes | the most this call can charge - the reserve held before running |
| minCostUsd | number | yes | the likely charge - the cheapest route serves first |
| perItemUnit | string | – | the unit perItemUsd is charged per: 'result' (default) or an input unit like 'username' for input-priced SKUs |
| perItemUsd | number | yes | marginal cost in USD per billable unit (see perItemUnit); 0 for a flat SKU |
| pricing | string | yes | a one-line human explanation of how this call is priced |
No examples provided.
read_result Read a saved result ~297
Read or reshape a previously paid API result without executing or paying again. `result_id` identifies the full cached result; fields/max_items/summary/jq control its presentation, including row selection and slicing large fields. Results are cached ~15 min and are private to the authenticated account; an expired id returns result_expired.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| fields | null|array | – | optional: keep only these keys on each result item - each row of the result list, or the data object itself for an API that returns one record (dotted paths like 'author.name' descend into nested obj… |
| jq | string | – | optional: a jq expression to reshape the result; its output replaces 'output'. Example: '.data | {title, description, md: .markdown[:3500]}'. Sandboxed 250ms/2MB budget |
| max_items | null|integer | – | optional: cap the number of result items returned; a _truncated note reports how many were withheld. An API that returns one record is not trimmed |
| result_id | string | yes | the resultId returned by a prior run_api call (cached ~15 min) |
| summary | boolean | – | optional: return only a structural outline (top-level keys, item counts, per-field byte sizes) instead of the full data |
| Name | Type | Req | Description |
|---|---|---|---|
| costUsd | number | yes | amount charged to the wallet in USD |
| error | null|object | – | safe AnyAPI failure code when durable work failed |
| hint | string | – | optional result caveat. 'large_result:' identifies a large response; fields/max_items/summary reduce response size without changing cost. 'paging_unavailable:' means the source cannot return a nextCu… |
| items | integer | yes | number of result rows returned; an API that returns one record counts it as one row. For per-result APIs the per-item cost is charged against this; for input-priced APIs (perItemUnit != result) the c… |
| jqError | string | – | present only when a jq expression failed; output then holds the full unshaped result and this explains why the reshape did not apply |
| nextAction | null|object | – | stored-request retrieval coordinates and polling interval present while durable work is pending |
| output | – | yes | normalized output payload |
| provider | string | yes | the provider serving the request (AnyAPI) |
| replayed | boolean | yes | true when this response replays an identical earlier call (same API, same input) from the last few minutes instead of running again: nothing new was executed and costUsd restates the original charge,… |
| requestId | string | – | durable request identifier for stored status and result retrieval without repeating the paid provider dispatch |
| resultId | string | – | opaque handle to the full result, cached ~15 min; identifies the paid result available for free reshaping without another execution or charge. Absent when the result was too large to cache |
| serviceOutcome | string | – | end-to-end AnyAPI service outcome when known |
| settlementState | string | – | payment settlement state when known; independent of durable request status |
| source | null|object | – | the source that served this request; its id is accepted by 'source' for preference or 'ignoreSources' for exclusion. Absent when no source identity applies |
| status | string | – | durable request status: queued, running, succeeded, failed, or expired |
No examples provided.
report_bug Report a bug ~253
Submit a defect report to AnyAPI about wrong, empty, or malformed API data for valid input, misleading or unactionable errors, incorrect prices or schemas, or retries that failed unexpectedly. Free, never charged. `summary` is required and contains one line; optional `request_id` identifies the stored request and its upstream error body without requiring the payload in the report.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | optional: an email address for a reply; trial keys have no reachable account contact |
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| details | string | – | optional: what you expected, what you got, and anything you already tried |
| request_id | string | – | optional: the requestId or resultId from the run that went wrong. This is the single most useful field: it reaches the stored run, its attempts, and any upstream error body, so you do not need to pas… |
| sku | string | – | optional: the sku_id this is about, e.g. 'instagram.reels_search' |
| summary | string | yes | one line saying what went wrong or what you want to tell us |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the stored report id for support correspondence |
| received | boolean | yes | true when the report is stored |
No examples provided.
run_api Run an API ~440
Execute an API by API slug with a normalized input payload. Every input schema is strict: unknown fields are rejected, not ignored, and field names can differ between related APIs. Inputs must conform to the endpoint's schema, not its description. Published latency p50/p95/p99 and sample counts describe observed successful requests; p99 is an observation, not a maximum or a client timeout guarantee. Requires a valid AnyAPI key as a Bearer token. Charges the USD wallet. Some failed wallet-funded requests incur processing charges passed through at cost, with no markup; the error message shows the amount charged. Results can be large. `fields` keeps selected keys, `max_items` caps returned rows, and `summary` returns an outline; these controls reduce response size without changing the charge.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| fields | null|array | – | optional: keep only these keys on each result item - each row of the result list, or the data object itself for an API that returns one record (dotted paths like 'author.name' descend into nested obj… |
| input | object | yes | normalized input payload matching the API input schema |
| jq | string | – | optional: a jq expression to reshape the result; its output replaces 'output' (multiple outputs collect into an array). Example: '.data | {title, description, md: .markdown[:3500]}'. Sandboxed 250ms/… |
| max_items | null|integer | – | optional: cap the number of result items returned; a _truncated note reports how many were withheld. An API that returns one record is not trimmed. Does not change cost |
| sku_id | string | yes | the API SKU slug to execute |
| summary | boolean | – | optional: return only a structural outline (top-level keys, item counts, and per-field byte sizes) instead of the full data. Does not change cost |
| Name | Type | Req | Description |
|---|---|---|---|
| costUsd | number | yes | amount charged to the wallet in USD |
| error | null|object | – | safe AnyAPI failure code when durable work failed |
| hint | string | – | optional result caveat. 'large_result:' identifies a large response; fields/max_items/summary reduce response size without changing cost. 'paging_unavailable:' means the source cannot return a nextCu… |
| items | integer | yes | number of result rows returned; an API that returns one record counts it as one row. For per-result APIs the per-item cost is charged against this; for input-priced APIs (perItemUnit != result) the c… |
| jqError | string | – | present only when a jq expression failed; output then holds the full unshaped result and this explains why the reshape did not apply |
| nextAction | null|object | – | stored-request retrieval coordinates and polling interval present while durable work is pending |
| output | – | yes | normalized output payload |
| provider | string | yes | the provider serving the request (AnyAPI) |
| replayed | boolean | yes | true when this response replays an identical earlier call (same API, same input) from the last few minutes instead of running again: nothing new was executed and costUsd restates the original charge,… |
| requestId | string | – | durable request identifier for stored status and result retrieval without repeating the paid provider dispatch |
| resultId | string | – | opaque handle to the full result, cached ~15 min; identifies the paid result available for free reshaping without another execution or charge. Absent when the result was too large to cache |
| serviceOutcome | string | – | end-to-end AnyAPI service outcome when known |
| settlementState | string | – | payment settlement state when known; independent of durable request status |
| source | null|object | – | the source that served this request; its id is accepted by 'source' for preference or 'ignoreSources' for exclusion. Absent when no source identity applies |
| status | string | – | durable request status: queued, running, succeeded, failed, or expired |
No examples provided.
search_apis Search APIs ~279
Search APIs by meaning and keyword across name, slug, and description, returning matches with their descriptions but without schemas, ranked most relevant first. At least one of `query`, `category`, or `platform` is required, in any combination; `category` or `platform` without `query` enumerates that scope. `limit` caps matches (default 25, maximum 50). Each result carries a `relevance` score in (0,1] relative to the top match; a relevance floor drops weak matches, so `total` counts relevant matches before the limit. `ranking` identifies meaning-based ('semantic') or substring ('keyword') matching. Entries with heavy:true produce large API responses. Search results omit input schemas; API inputs require the endpoint's strict schema, whose field names can differ between related APIs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | optional category slug to narrow the search |
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| limit | null|integer | – | optional cap on matches returned (default 25, maximum 50) |
| platform | string | – | optional API slug prefix to narrow the search |
| query | string | – | free-text search over API name, slug, and description; optional when category or platform is given |
| Name | Type | Req | Description |
|---|---|---|---|
| ranking | string | yes | – |
| results | null|array | yes | – |
| total | integer | yes | – |
No examples provided.
send_feedback Send feedback ~243
Submit non-defect feedback to AnyAPI about an API you could not find in the catalog, a missing result field, confusing documentation or tool descriptions, or an improvement that would make a task easier. Free, never charged. `summary` is required and contains one line; optional `details` describes the task or suggestion.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | optional: an email address for a reply; trial keys have no reachable account contact |
| context | string | yes | Brief purpose of this tool call within the requested task, used for analytics and user-intent tracking. |
| details | string | – | optional: what you expected, what you got, and anything you already tried |
| request_id | string | – | optional: the requestId or resultId from the run that went wrong. This is the single most useful field: it reaches the stored run, its attempts, and any upstream error body, so you do not need to pas… |
| sku | string | – | optional: the sku_id this is about, e.g. 'instagram.reels_search' |
| summary | string | yes | one line saying what went wrong or what you want to tell us |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the stored report id for support correspondence |
| received | boolean | yes | true when the report is stored |
No examples provided.
How do I install the AnyAPI MCP server?
AnyAPI is a hosted endpoint at https://api.getanyapi.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 · api.getanyapi.com
claude mcp add --transport http getanyapi-com-anyapi 'https://api.getanyapi.com/mcp'
What is the AnyAPI MCP server?
AnyAPI is an MCP server listed in the public MCP registry as io.github.getanyapi-com/anyapi. Hundreds of scraping & data APIs through one key. USD pay-per-request, normalized schemas, failover. This page covers its hosted endpoint (https://api.getanyapi.com/mcp).
Is the AnyAPI MCP server safe to use?
AnyAPI scores 90 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 AnyAPI MCP server expose?
AnyAPI exposes 10 tools: get_api, get_balance, get_request, list_apis, quote_api, and 5 more. Their descriptions and schemas cost roughly 2,095 tokens of context every time the server is loaded.
Does the AnyAPI MCP server require authentication?
Yes. AnyAPI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the AnyAPI MCP server still maintained?
AnyAPI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.