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.

viberank

NPM · VIBERANK-MCP

Submit your AI coding usage (Claude Code, Codex, Gemini CLI) to viberank and read the leaderboard.

Available components

0 this week 71 Trust /100

Last scanned (20 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 602 tokens (~120/item across 5 items; 5 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 5 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 56

    First indexed and scored.

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/viberank-mcp@1.2.0

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 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~534 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
get_leaderboard ~119

The current viberank leaderboard, ranked by API-equivalent cost. Each entry has rank, username, totalCost (USD), totalTokens, tools, verified, underReview and profileUrl. Pass tool to rank only the users of one tool; get_stats lists the tool slugs.

NameTypeReqDescription
limitinteger–How many top entries to return, 1 to 50.
toolstring–A tool slug such as "claude", "codex", "gemini", "opencode" or "copilot".

No output schema declared.

No examples provided.

get_profile ~66

One developer's viberank profile: global rank, total cost and tokens, days tracked, tools and whether it is verified. Profiles are keyed by GitHub username. Returns found: false when there's no such profile.

NameTypeReqDescription
usernamestringyesThe GitHub username to look up.

No output schema declared.

No examples provided.

get_stats ~72

Site-wide viberank statistics: developer and submission counts, total tokens and API-equivalent cost, monthly spend per developer (median and percentiles), tool and model adoption, the monthly trend and tier counts, with methodology, caveats and a citation line. Use it to compare one developer's spend with everyone else's.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_usage ~109

Read the user's local AI coding usage (Claude Code, Codex, Gemini CLI, OpenCode and the other tools ccusage supports) by running ccusage@20 on this machine. Returns a summary: API-equivalent cost in USD, tokens, days tracked, date range and cost per tool. Sends nothing anywhere. Can take a minute on a long history; results are cached for 5 minutes.

NameTypeReqDescription
force_refreshboolean–Re-run ccusage instead of using the 5-minute cache.

No output schema declared.

No examples provided.

submit_to_viberank ~168

Upload the user's local usage to the public viberank.app leaderboard. Call it only when the user asked to submit. With a VIBERANK_TOKEN configured, the submission is verified and filed under the token's account, so leave github_username out. Without a token, github_username is required and must be the user's own GitHub handle, confirmed with them, because it becomes a public profile. Called without one, it uploads nothing and suggests a handle to confirm with the user before calling again. On success it returns rank, tier and a README badge you can offer to add.

NameTypeReqDescription
github_usernamestring–The user's own GitHub username, as they confirmed it. Not a display name, not an organization. Leave it out when VIBERANK_TOKEN is set.

No output schema declared.

No examples provided.

Install

How do I install the viberank MCP server?

viberank runs locally as an npm package, launched with npx -y viberank-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 · viberank-mcp

# add to Claude Code
claude mcp add sculptdotfun-viberank -- npx -y viberank-mcp
Common questions

What is the viberank MCP server?

viberank is an MCP server listed in the public MCP registry as io.github.sculptdotfun/viberank. Submit your AI coding usage (Claude Code, Codex, Gemini CLI) to viberank and read the leaderboard. This page covers its npm package (viberank-mcp).

Is the viberank MCP server safe to use?

viberank scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting 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 viberank MCP server expose?

viberank exposes 5 tools: get_usage, submit_to_viberank, get_leaderboard, get_profile, get_stats. Their descriptions and schemas cost roughly 534 tokens of context every time the server is loaded.

Is the viberank MCP server still maintained?

viberank 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 viberank MCP server under?

viberank 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 viberank MCP server?

VerifyMCP ran 15 checks on viberank, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about viberank: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.