Home / MCP registry index / com.signalaf/sigrank
SigRank — AI Operator Benchmarking
com.signalaf/sigrank in the official MCP registry.
Endpoint https://signalaf.com/api/mcp. Source: github.com/SunrisesIllNeverSee/sigrank-app.
The registry describes it as: SigRank benchmark MCP: cascade metrics, leaderboard, operator profiles, simulation, diagnostics.
We read its 16 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
rank_paste get_sigrank_standard_record get_leaderboard get_operator simulate_change diagnose_cascade suggest_improvements self_improve rank_windows benchmark_me rank_if operator_gap field_anomaly who_operates_like_me compare_to_field operator_signature
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-signalaf-sigrank)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.