Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
SigRank SignalAF on-device scanner — four-token cascade, leaderboard, 25 local tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"sigrank": {
"command": "npx",
"args": [
"-y",
"sigrank"
]
}
}
}Run this in your terminal
claude mcp add sigrank -- npx -y sigrankPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"sigrank": {
"command": "npx",
"args": [
"-y",
"sigrank"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"sigrank": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"sigrank"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account SunrisesIllNeverSee, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.47) reached the registry 22 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, 好縮 Short
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Smart URL shortener: create, tag and track short links on s.gooo.name.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Read your local AI usage, inspect the token cascade, and optionally publish a signed snapshot to the SigRank leaderboard on SignalAF.
npx sigrank
[Website](https://signalaf.com) · [Quickstart](#get-started) · [MCP setup](#connect-an-mcp-client) · [Tool and adapter reference](./docs/CLI-MCP-REFERENCE.md) · [Privacy](#privacy)
This evaluates observable token-processing patterns, not model quality, work quality, productivity, or business outcomes. An adapter may estimate a pillar when its source does not expose it separately; those limitations are documented in the adapter reference.
Requires Node.js 20 or later. No global install is required.
npx sigrank # interactive dashboard in a terminal
npx sigrank board --once # public leaderboard, one-shot npx sigrank board --window 7d --once
The dashboard includes Dashboard, Trends, Compare, Board, Watch, and Connect tabs. Use 1–6 or the arrow keys to switch, R to refresh, and Q to quit.
npx sigrank enroll
npx sigrank submit --dry-run npx sigrank submit
Enrollment binds a device signing key to your operator account. The private key stays on your device. The server verifies and re-scores submitted telemetry; a local preview is not a guaranteed public rank.
For repeated use, an optional global installation provides the same commands:
npm install -g sigrank
sigrank
Add this server to your client's MCP configuration:
{
"mcpServers": { "sigrank": { "command": "npx", "args": ["-y", "sigrank"] } } }
The entry point automatically runs an MCP stdio server when launched without a terminal. MCP tool names are called by the client; they are not shell commands.
| Task | Tools |
|---|---|
| Inspect local usage | tokenpull, rank_windows, tokenpull_compare |
| Calculate from supplied counts | rank_paste, get_sigrank_standard_record |
| Read public results | get_leaderboard, get_operator, discover_peers |
| Explore possible changes | diagnose_cascade, simulate_change, suggest_improvements |
| Enroll and submit | enroll, submit_verified |
For the full list, arguments, and adapter paths, see the CLI and MCP reference. Publishing through submit_verified requires confirm: true; dry_run: true inspects the payload without publishing.
| Command | Purpose |
|---|---|
sigrank | Open the terminal dashboard |
sigrank board --once | Print the public leaderboard |
sigrank compare --platform codex | Audit token counts across available local sources |
sigrank watch --window 7d | Watch local usage updates |
sigrank enroll | Bind a device using a connect code |
sigrank submit --dry-run | Inspect a signed submission without sending it |
sigrank submit | Publish a verified submission |
sigrank proxy | Start the optional loopback usage proxy |
sigrank --help | Show the current command reference |
Some clients do not persist all provider-reported usage in their session files. sigrank proxy can capture usage from compatible Anthropic or OpenAI API traffic when a client supports a custom API base URL.
The proxy is off by default and binds only to loopback. It forwards provider-bound request/response content and credentials in memory, but does not persist their content. Its local usage log contains token counts and metadata. See the privacy contract before using it.
Four token pillars feed the calculation:
Yield (Υ) = (cache_read × output) / input²
Leverage = cache_read / input Velocity = output / input SNR = output / (input + output) 10xDEV = log₁₀(Leverage)
This package distributes the Upsilon measurement engine through the sigrank CLI/MCP compatibility command. SigRank is the public leaderboard and proof surface on SignalAF. TTEOP defines the protocol semantics; MO§ES™ is the governance framework.
The implementation delegates canonical calculations through token-cascade to tteop-spec. See the TTEOP implementation profile and protocol compatibility notes.
Local inspection does not publish your usage. Signed submissions include the four pillars plus account/device identifiers, signature, platform/version information, counts, and report metadata. Enrollment also sends a device label.
Prompt text, response text, source code, repository contents, and local file paths are not part of the ranked submission payload. The optional proxy's transient handling of content is separate from what is persisted or submitted.
Read the full payload and privacy details, and use submit --dry-run to inspect what would be sent.
git clone https://github.com/SunrisesIllNeverSee/sigrank-mcp.git
cd sigrank-mcp npm install npm test npm run test:packaged
Run node index.mjs in a terminal for the dashboard, or configure the checked-out entry point in an MCP client. Release versions are managed by the repository's explicit publishing workflow; a documentation commit does not publish an npm release.
See the contributing guide. Open bugs in GitHub Issues; report vulnerabilities privately through the security policy.
MIT.