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.alexanderclapp/clirank

NPM · CLIRANK-MCP-SERVER

Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance.

Available components

0 this week 80 Trust /100

Last scanned (19 hours ago)

Scores higher than 66% of npm servers

Category Code Search and Documentation

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 359 tokens (~59/item across 6 items; 6 tools + 0 resources), lean.Pass
  • 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 17 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 16 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 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.

  • 10 Nov 26 −2
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.90 functional
  • 4 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 3 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ 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 21 Nov 2026 · Analysed npm/clirank-mcp-server@0.2.1

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~359 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
browse_categories ~26

List all API categories in the CLIRank directory with the number of APIs in each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

compare_apis ~58

Compare two or more APIs side by side. Returns a comparison table with scores, pricing, auth, and capabilities.

NameTypeReqDescription
slugsarrayyesArray of API slugs to compare, e.g. ['stripe-api', 'paypal-api']

No output schema declared.

No examples provided.

discover_apis ~102

Search for APIs by intent or capability. Describe what you need and get ranked matches. Examples: 'send transactional emails', 'process payments', 'image generation'.

NameTypeReqDescription
limitnumber–Max results (default 10, max 50)
min_cli_scorenumber–Minimum CLI relevance score (1-10)
pricingstring–Pricing filter
querystringyesWhat you need, e.g. 'send transactional emails'

No output schema declared.

No examples provided.

get_api_details ~55

Get full details for a specific API by its slug. Returns scores, pricing, auth method, capabilities, and quality breakdown.

NameTypeReqDescription
slugstringyesAPI slug, e.g. 'stripe-api', 'openai-api'

No output schema declared.

No examples provided.

get_api_docs ~53

Get agent-friendly documentation for an API, including quickstart guide and documented endpoints. Use this before integrating an API.

NameTypeReqDescription
slugstringyesAPI slug, e.g. 'stripe-api', 'openai-api'

No output schema declared.

No examples provided.

get_reviews ~65

Get integration reports and reviews for an API. Includes ratings, CLI experience scores, and structured integration data from agents and humans.

NameTypeReqDescription
limitnumber–Max reviews to return (default 10)
slugstringyesAPI slug, e.g. 'openai-api'

No output schema declared.

No examples provided.

Install

How do I install the io.github.alexanderclapp/clirank MCP server?

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

npm · clirank-mcp-server

# add to Claude Code
claude mcp add alexanderclapp-clirank -- npx -y clirank-mcp-server
Common questions

What is the io.github.alexanderclapp/clirank MCP server?

io.github.alexanderclapp/clirank is an MCP server listed in the public MCP registry as io.github.alexanderclapp/clirank. Search, compare, and get docs for 210+ APIs ranked by CLI and agent relevance. This page covers its npm package (clirank-mcp-server).

Is the io.github.alexanderclapp/clirank MCP server safe to use?

io.github.alexanderclapp/clirank scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 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.alexanderclapp/clirank MCP server expose?

io.github.alexanderclapp/clirank exposes 6 tools: discover_apis, get_api_details, get_api_docs, compare_apis, browse_categories, get_reviews. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.

Is the io.github.alexanderclapp/clirank MCP server still maintained?

io.github.alexanderclapp/clirank is still listed as active in the MCP registry. We last reached this channel on 21 November 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.alexanderclapp/clirank MCP server under?

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

What did VerifyMCP test on the io.github.alexanderclapp/clirank MCP server?

VerifyMCP ran 16 checks on io.github.alexanderclapp/clirank, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.