Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ailingqu/apiany-mcp

NPM · @APIANY-AI/MCP · SCANNED SEP 24

APIAny MCP server for model discovery, pricing, docs, and integration examples.

Available components

0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 699 tokens (~69/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
Install

How do I install the io.github.ailingqu/apiany-mcp server?

io.github.ailingqu/apiany-mcp runs locally as an npm package, launched with npx -y @apiany-ai/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @apiany-ai/mcp

# add to Claude Code
claude mcp add ailingqu-apiany-mcp -- npx -y @apiany-ai/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "ailingqu-apiany-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@apiany-ai/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ailingqu-apiany-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@apiany-ai/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add ailingqu-apiany-mcp -- npx -y @apiany-ai/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ailingqu-apiany-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@apiany-ai/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ailingqu-apiany-mcp --command npx --arg -y --arg @apiany-ai/mcp
# ~/.hermes/config.yaml
mcp_servers:
  ailingqu-apiany-mcp:
    command: "npx"
    args: ["-y", "@apiany-ai/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ailingqu-apiany-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@apiany-ai/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add ailingqu-apiany-mcp -t stdio -c npx -a -y @apiany-ai/mcp
// mcp.json
{
  "mcpServers": {
    "ailingqu-apiany-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@apiany-ai/mcp"
      ]
    }
  }
}
Changelog

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.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

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 24 Sept 2026 · Analysed npm/@apiany-ai/mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~699 tokens

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 →

Tool Tokens
create_image_task ~158

Create a paid APIAny asynchronous image generation task. Requires APIANY_API_KEY and confirm_paid_request=true.

NameTypeReqDescription
callback_urlstring–Optional public HTTPS callback URL.
confirm_paid_requestboolean––
extra_jsonobject–Optional extra request fields to merge into the JSON body.
image_urlsarray–Optional reference/input images for image-to-image or editing.
modelstringyes–
promptstringyes–
qualitystring–Resolution/quality tier such as 1k, 2k, 4k, standard, or hd.
sizestring–Aspect ratio such as 1:1 or 16:9, or a pixel size when supported.

No output schema declared.

No examples provided.

create_video_task ~183

Create a paid APIAny asynchronous video generation task. Requires APIANY_API_KEY and confirm_paid_request=true.

NameTypeReqDescription
aspect_ratiostring–Video aspect ratio such as 16:9 or 9:16.
audio_urlsarray–Optional reference audio for models that support audio input.
callback_urlstring–Optional public HTTPS callback URL.
confirm_paid_requestboolean––
durationinteger––
extra_jsonobject–Optional extra request fields to merge into the JSON body.
image_urlsarray–Optional reference images for image-to-video models.
modelstringyes–
promptstringyes–
resolutionstring–Optional video resolution such as 720p or 1080p.
video_urlsarray–Optional reference videos for models that support video input.

No output schema declared.

No examples provided.

estimate_cost ~59

Estimate APIAny credits for a model using public pricing metadata.

NameTypeReqDescription
cached_input_tokensinteger––
input_tokensinteger––
modelstringyes–
output_tokensinteger––
requestsinteger––

No output schema declared.

No examples provided.

get_docs_context ~28

Return compact APIAny documentation context from llms.txt.

NameTypeReqDescription
max_charsinteger––

No output schema declared.

No examples provided.

get_integration_examples ~35

Return APIAny integration examples for a model and language.

NameTypeReqDescription
languagestring––
modelstring––

No output schema declared.

No examples provided.

get_model ~28

Get one APIAny model by public model id or display name.

NameTypeReqDescription
modelstringyes–

No output schema declared.

No examples provided.

get_model_usage ~70

Return endpoint, payload, async behavior, and language example for one or more APIAny models.

NameTypeReqDescription
languagestring––
limitinteger––
modelstring–Optional model id or display name. Omit to list usage for models.
typestring––

No output schema declared.

No examples provided.

get_task_status ~32

Get an APIAny async generation task status. Requires APIANY_API_KEY.

NameTypeReqDescription
task_idstringyes–

No output schema declared.

No examples provided.

list_models ~61

List public APIAny models with pricing and capability metadata.

NameTypeReqDescription
limitinteger––
providerstring–Optional provider name, such as OpenAI or Google.
qstring–Optional model search text.
typestring––

No output schema declared.

No examples provided.

search_models ~45

Search APIAny models by natural-language text, provider, modality, or capability.

NameTypeReqDescription
limitinteger––
querystringyes–
typestring––

No output schema declared.

No examples provided.

Common questions

What is the io.github.ailingqu/apiany-mcp server?

io.github.ailingqu/apiany-mcp is listed in the public MCP registry as io.github.ailingqu/apiany-mcp. APIAny MCP server for model discovery, pricing, docs, and integration examples. This page covers its npm package (@apiany-ai/mcp).

Is the io.github.ailingqu/apiany-mcp server safe to use?

io.github.ailingqu/apiany-mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 io.github.ailingqu/apiany-mcp server expose?

io.github.ailingqu/apiany-mcp exposes 10 tools: list_models, search_models, get_model, estimate_cost, get_integration_examples, and 5 more. Their descriptions and schemas cost roughly 699 tokens of context every time the server is loaded.

Is the io.github.ailingqu/apiany-mcp server still maintained?

io.github.ailingqu/apiany-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.ailingqu/apiany-mcp server under?

io.github.ailingqu/apiany-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.