SigRank - Token Efficiency Leaderboard
SigRank - Token Efficiency Leaderboard is an MCP server published by SunrisesIllNeverSee, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does SigRank - Token Efficiency Leaderboard support the current MCP specification (2026-07-28)?
Not yet confirmed. SigRank - Token Efficiency Leaderboard is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is SigRank - Token Efficiency Leaderboard a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for SigRank - Token Efficiency Leaderboard (as of 2026-08-20).
How do I connect to SigRank - Token Efficiency Leaderboard?
SigRank - Token Efficiency Leaderboard is available via the package npm:sigrank, the official MCP Registry under io.github.SunrisesIllNeverSee/sigrank-mcp, the source repository at https://github.com/sunrisesillneversee/sigrank-mcp. Authentication: unknown. Transports: stdio.
Does SigRank - Token Efficiency Leaderboard support MCP revision 2025-11-25?
Yes. SigRank - Token Efficiency Leaderboard supports MCP revision 2025-11-25 (checked 2026-08-20).
Does SigRank - Token Efficiency Leaderboard support MCP revision 2026-07-28?
No. SigRank - Token Efficiency Leaderboard was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were SigRank - Token Efficiency Leaderboard's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Operator leaderboard measuring users, not models - 20 tools, TUI, signed submit, privacy-first.
Which MCP spec revisions does SigRank - Token Efficiency Leaderboard support?
SigRank - Token Efficiency Leaderboard has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is SigRank - Token Efficiency Leaderboard?
Ranked #365 in The MCP 500 with Adoption Index 48.02 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 1,430 | API · |
| GitHub stars | 0 | API · |
| GitHub forks | 4 | API · |
| Last push | 2026-09-11T02:35:43Z | API · |
| Repository archived | no | API · |
Repository and package signals for SigRank - Token Efficiency Leaderboard
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 3
- Primary language
- JavaScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: agent-tools, ai, ai-agents, anthropic, claude, cli, dashboard, leaderboard, mcp, model-context-protocol, nodejs, on-device, terminal, token-usage, tokens, yield-cascade — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.0.230- Last published
- First published
- Releases
- 86
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 3
- Unpacked size
- 684 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.SunrisesIllNeverSee/sigrank-mcp at version 0.17.2 - lists package npm:sigrank and repository https://github.com/sunrisesillneversee/sigrank-mcp - accessed
- npm registry metadata for sigrank at published version 0.0.222, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed