SigRank — AI Operator Benchmarking MCP Server

by signalaf Your server? Claim it

not responding

SigRank — AI Operator Benchmarking is listed as active in the registry but did not answer our last check. It exposes 16 tools. Last commit 21 Sep 2026.

SigRank benchmark MCP: cascade metrics, leaderboard, operator profiles, simulation, diagnostics.

Uptime history 26 days of history · worst day 14%

26 days agonow

14.3%

Uptime 24h

13 of 91 checks

Tools

read from the server

1144 ms

Response time

average over 24h

Stars

last commit 21 Sep 2026

What changed 18

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 28 August 2026. No other catalogue keeps this.

3 Sep 16 tools changed the parameters they ask for benchmark_me, compare_to_field, diagnose_cascade and 13 more

28 Aug a tool appeared get_sigrank_standard_record

28 Aug a tool description was rewritten operator_signature

What the code does

We read the source, 15 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a database query by concatenation components/marketing/FourDegreesChart.tsx:327, components/marketing/SignalIntegrity.tsx:605, _archived/workflows/sync-mcp-version.yml:91 и ещё 1

          to any outlier no matter how extreme. The trimmed mean (drop 5% each

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add sigrank --transport http https://signalaf.com/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "sigrank": {
      "url": "https://signalaf.com/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.sigrank]
url = "https://signalaf.com/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "sigrank": {
      "url": "https://signalaf.com/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "sigrank": {
      "url": "https://signalaf.com/api/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

operator

get_operator

Read one public operator profile by codename. Returns class tier, rank, percentile, Yield, Leverage, Velocity, and SNR.

operator_gap

Answers 'What specifically separates operator A from operator B?' — not just 'A has more Yield', but the primary cause, secondary cause, and offsetting weakness. Takes two codenames or two sets of pillars, computes both cascades, and decomposes the yield gap into leverage, velocity, SNR, and scale contributions. Returns the most explanatory factor.

operator_signature

Computes a normalized operating signature from 4 token pillars or a codename. Returns a signature code, a legacy six-label signature_label, dominant trait, and closest comparable operators from the live board. The deprecated archetype field is retained as a compatibility alias; these labels are not the 10-type Build Archetypes reference extension.

rank

rank_if

Answers 'What would it take to reach a target rank?' — takes your current 4 token pillars and a target percentile (e.g. 90 for top 10%), then simulates the smallest metric changes needed to reach that position. Returns: current rank/percentile, simulated rank/percentile, the specific pillar changes required, and the yield delta. This turns SigRank from a scoreboard into a simulator. Use it when someone asks 'what would move my rank?' or 'how do I get to top 10%?'.

rank_paste

Calculate SigRank cascade metrics from four non-negative token counts without submitting data. Returns Yield, Leverage, Velocity, SNR, and 10xDEV. No data is persisted.

rank_windows

Score up to 4 time windows (7d, 30d, 90d, all-time) in one call. Each window is scored independently with the full cascade (Υ, SNR, Leverage, Velocity, 10xDEV, class). Omit windows you don't have — partial input is allowed (1-4 windows). Does NOT submit to the board.

benchmark

benchmark_me

Answers 'How good am I?' — benchmarks your token cascade against the live field. Takes 4 token pillars (or a codename), computes your cascade, then compares against the live leaderboard: percentile, rank, distance from median, distance from top 10%, strongest metric, weakest metric, and a one-line interpretation. This is the human-question tool — use it when someone asks 'am I a power user?' or 'how do I compare?'.

compare

compare_to_field

Creates a 'YOU vs FIELD vs TOP 10% vs TOP 1%' comparison table for your cascade metrics. Takes 4 pillars or a codename, fetches the live leaderboard, and returns your metrics alongside field median, top quartile, top decile, and top percentile for yield, leverage, velocity, and SNR. Simple, useful, and immediately understandable.

diagnose

diagnose_cascade

Analyzes your token cascade and diagnoses where you're leaking efficiency. Takes 4 token pillars and produces a ranked list of efficiency leaks with severity (critical/warning/info), findings, recommendations, and estimated Υ impact. Checks: cache leverage, velocity, SNR, cache creation ratio, input bloat, and 10xDEV compounding. Use this before simulate_change to understand what's wrong.

field

field_anomaly

Finds unusual operators, metric relationships, and outliers in the live leaderboard — without user prompting. Returns: highest velocity among below-median leverage operators, only top-50 operator with near-zero cache write, largest 30-day yield improvement, rarest signature, and extreme divergence. Powers automated micro-marketing and field insights.

leaderboard

get_leaderboard

Read the current public SigRank operator leaderboard. Returns ranked operators with Yield, Leverage, class tier, and display name.

self

self_improve

Runs the full self-improvement cycle in one call: (1) computes your current cascade from 4 token pillars, (2) diagnoses efficiency leaks, (3) generates ranked improvement suggestions, (4) simulates the top suggestion, and (5) returns the complete cycle: diagnosis + suggestions + simulated impact of the best change. The 'one-click optimize' tool — call it at the end of a session to see what to improve next time.

sigrank

get_sigrank_standard_record

Build a SigRank Standard v0.1-draft portable operator record from available token telemetry. Input and output are required; unavailable cache telemetry remains null. Computes only the five-metric portable core through @sigrank/cascade and does not submit or persist data.

simulate

simulate_change

Prescriptive 'what if' tool — takes your current 4 token pillars and proposed changes, runs the cascade on both, returns the exact Υ Yield delta, class change, and per-metric diffs. Test proposed pillar changes and see the payoff before changing your workflow. Changes can be absolute numbers (replace) or strings starting with +/- for relative deltas.

suggest

suggest_improvements

Generates ranked, simulated improvement suggestions for your token cascade. Takes 4 token pillars, tests multiple strategies (increase cache reads, reduce input, increase output, optimize cache creation), simulates each, and returns them ranked by Υ yield impact. Each suggestion includes the action, pillar to change, projected Υ, yield delta, projected class, and rationale. Returns the single highest-impact change as best_single_change.

who

who_operates_like_me

Finds operators whose operating signature most resembles yours. Takes 4 pillars or a codename, computes your signature, then searches the live leaderboard for the nearest neighbors by signature distance. Returns: nearest operators, similarity %, where they outperform you, where you outperform them, and what separates you from the better operator. Makes the leaderboard feel like a network, not a list.

Endpoints

URL	Transport	State	Latency	Checked
https://signalaf.com/api/mcp	streamable-http	answering	166 ms	4 min ago

Alternatives to SigRank — AI Operator Benchmarking

same job, measured the same way

Hardware Probe

by yamaru-eu

Hardware probe for performance diagnostics, thermal monitoring, and LLM optimization.

41 installs/wk local only

Pensiata - Bulgarian Pension Fund Analytics

by nvasilevv

Bulgarian pension fund analytics — NAV data, metrics, rankings, and benchmarks.

26 tools answering

Google Business Profile MCP

by a1-x-tech

MCP server for Google Business Profile: locations, reviews, local posts and performance metrics.

233 installs/wk local only

P2Predict

by ahmed-khalil-hafsi

Local MCP server for parametric price benchmarking in procurement and engineering.

local only

ellmos ServerCommander

by ellmos-ai

Server operations MCP: HTTP health checks, log analysis, deploy dry-runs, mail diagnostics.

207 installs/wk local only

Statiko — Telegram trends & channel analytics

by statiko

Live Telegram data: trending topics, channel profiles & metrics, post history incl. edits/deletions.

10 tools answering

RTL Lint MCP

by jaspresi

Lint Verilog and SystemVerilog files and projects with structured diagnostics.

56 installs/wk local only

VMware Aria Operations

by zw008

VMware Aria Operations: metrics, alerts, capacity, anomaly detection — 18 MCP tools.

1 708 installs/wk local only

SigRank — AI Operator Benchmarking — questions

Answers built from our own checks of this server.

What can SigRank — AI Operator Benchmarking do?

It exposes 16 tools, read directly from the server on our last check. Among them: benchmark_me, compare_to_field, diagnose_cascade, field_anomaly, get_leaderboard, get_operator and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is SigRank — AI Operator Benchmarking mostly used for?

Its tools cluster around rank and operator. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is SigRank — AI Operator Benchmarking working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 13 of 91 checks got a reply (14.3%), average response time 1144 ms. The bar chart above shows every period we have measured.

The registry lists SigRank — AI Operator Benchmarking as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect SigRank — AI Operator Benchmarking?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SigRank — AI Operator Benchmarking need an API key?

No. SigRank — AI Operator Benchmarking completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is SigRank — AI Operator Benchmarking?

It answers our handshake in 1144 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is SigRank — AI Operator Benchmarking open source?

Yes — it is published under the MIT licence, written in TypeScript and 6 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.