SigRank MCP server

submit_paste

Read-onlyIdempotent

Rank pasted token counts locally to preview your cascade yield, leverage, and velocity. Use for instant local scoring from ccusage or dashboard data without publishing.

Instructions

Ranks a paste of token counts locally and shows the cascade result (yield, leverage, velocity, class, card). This is a PREVIEW-ONLY tool — it does not publish to the board. The board's /api/v1/ingest-paste endpoint now requires an authenticated Supabase session, which MCP tools do not carry. To publish to the leaderboard, use submit_verified (which signs and posts to /api/v1/snapshots via the enrolled-device path) or submit directly through the signalaf.com web UI. Use this when you have token counts from ccusage or a dashboard and want to see your score instantly. Do NOT use this if you want to pull your local usage automatically — use tokenpull_submit for the zero-paste flow. Do NOT use this for multi-window dashboard pastes — use rank_windows to rank them first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Token counts to rank. Two formats: (1) JSON {"input":N,"output":N,"cacheCreate":N,"cacheRead":N} from ccusage (preferred), or (2) four whitespace-separated numbers: input output cacheCreate cacheRead. Example: {"input":1000000,"output":500000,"cacheCreate":50000,"cacheRead":800000}
`codename`	No	Operator codename for the ranking card display (e.g. "Ghost Falcon"). Optional — used only for the local preview card, not for board submission.

Output Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Error or skip reason if status is not ok
`status`	No	Submission status
`preview`	No
`server_response`	No	Server-side response including new rank if accepted

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.19.10Sep 11, 2026

changedInput schema / description

Previous value: -"Requires token counts (text). Codename is optional but required for board submission — omit it for preview-only mode."New value: +"Requires token counts (text). Returns a local preview only — does not publish to the board."

changedInput schema / properties / codename / description

Previous value: -"Operator codename to publish under on the leaderboard (e.g. \"Ghost Falcon\"). Required to submit — omit for local preview only (no board submission, just returns the local cascade result). Must be a non-empty string."New value: +"Operator codename for the ranking card display (e.g. \"Ghost Falcon\"). Optional — used only for the local preview card, not for board submission."

changedInput schema / properties / text / description

Previous value: -"Token counts to rank and submit. Two formats: (1) JSON {\"input\":N,\"output\":N,\"cacheCreate\":N,\"cacheRead\":N} from ccusage (preferred — the board parses this reliably), or (2) four whitespace-separated numbers: input output cacheCreate cacheRead. The 4-number form ranks locally but the board may reject it. Example: {\"input\":1000000,\"output\":500000,\"cacheCreate\":50000,\"cacheRead\":800000}"New value: +"Token counts to rank. Two formats: (1) JSON {\"input\":N,\"output\":N,\"cacheCreate\":N,\"cacheRead\":N} from ccusage (preferred), or (2) four whitespace-separated numbers: input output cacheCreate cacheRead. Example: {\"input\":1000000,\"output\":500000,\"cacheCreate\":50000,\"cacheRead\":800000}"

Changed9 schema fields changedv0.19.6Aug 11, 2026

changedOutput schema / properties / preview / properties / class / description

Previous value: -"Operator class tier"New value: +"Operator class tier (dev10x taxonomy)"

changedOutput schema / properties / preview / properties / class / enum

Previous value: -[
-  "Burner",
-  "Builder",
-  "10xer"
-]New value: +[
+  "ARCH+ I",
+  "ARCH+ II",
+  "ARCH+ III",
+  "ARCH I",
+  "ARCH II",
+  "ARCH III",
+  "POWER I",
+  "POWER II",
+  "POWER III",
+  "BASE I",
+  "BASE II",
+  "BASE III",
+  "SEEKER I",
+  "SEEKER II",
+  "SEEKER III",
+  "REFINER I",
+  "REFINER II",
+  "REFINER III",
+  "BEARER I",
+  "BEARER II",
+  "BEARER III",
+  "IGNITER I",
+  "IGNITER II",
+  "IGNITER III",
+  "UNCLASSED"
+]

addedOutput schema / properties / preview / properties / dev10x

Added value: +{
+  "description": "10xDEV score (log10 of the cascade product)",
+  "type": "number"
+}

addedOutput schema / properties / preview / properties / mode

Added value: +{
+  "description": "Detected working mode (BUILD/EDIT/DEBUG/MAINTAIN/IDLE) + confidence",
+  "type": "object"
+}

addedOutput schema / properties / preview / properties / pillars

Added value: +{
+  "description": "The four raw token pillars the cascade was computed from",
+  "type": "object"
+}

removedOutput schema / properties / preview / properties / tenx_dev

Removed value: -{
-  "description": "10xDEV score",
-  "type": "number"
-}

addedOutput schema / properties / preview / properties / yield

Added value: +{
+  "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
+  "type": "number"
+}

removedOutput schema / properties / preview / properties / yield_

Removed value: -{
-  "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
-  "type": "number"
-}

changedOutput schema / properties / preview / required

Previous value: -[
-  "yield_",
-  "class"
-]New value: +[
+  "yield",
+  "class"
+]

Addedv0.19.2Jul 23, 2026
RemovedJul 22, 2026

Changed1 schema field changedv0.16.0Jul 7, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "preview": {
+      "properties": {
+        "card": {
+          "description": "Deterministic prose summary of the cascade result",
+          "type": "string"
+        },
+        "class": {
+          "description": "Operator class tier",
+          "enum": [
+            "Burner",
+            "Builder",
+            "10xer"
+          ],
+          "type": "string"
+        },
+        "leverage": {
+          "description": "Cr/I — cache reads divided by input",
+          "type": "number"
+        },
+        "snr": {
+          "description": "Signal-to-noise ratio",
+          "type": "number"
+        },
+        "tenx_dev": {
+          "description": "10xDEV score",
+          "type": "number"
+        },
+        "velocity": {
+          "description": "O/I — output divided by input",
+          "type": "number"
+        },
+        "warnings": {
+          "description": "Parse or data warnings if any",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "yield_": {
+          "description": "Υ Yield — the headline efficiency metric (Cache Reads × Output / Input²)",
+          "type": "number"
+        }
+      },
+      "required": [
+        "yield_",
+        "class"
+      ],
+      "type": "object"
+    },
+    "reason": {
+      "description": "Error or skip reason if status is not ok",
+      "type": "string"
+    },
+    "server_response": {
+      "description": "Server-side response including new rank if accepted",
+      "type": "object"
+    },
+    "status": {
+      "description": "Submission status",
+      "enum": [
+        "ok",
+        "error",
+        "skipped"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedv0.6.10Jul 4, 2026

addedInput schema / description

Added value: +"Requires token counts (text). Codename is optional but required for board submission — omit it for preview-only mode."

changedInput schema / properties / codename / description

Previous value: -"operator codename to publish under (required to submit; omit for local preview only)"New value: +"Operator codename to publish under on the leaderboard (e.g. \"Ghost Falcon\"). Required to submit — omit for local preview only (no board submission, just returns the local cascade result). Must be a non-empty string."

changedInput schema / properties / text / description

Previous value: -"ccusage JSON or \"input output cacheCreate cacheRead\""New value: +"Token counts to rank and submit. Two formats: (1) JSON {\"input\":N,\"output\":N,\"cacheCreate\":N,\"cacheRead\":N} from ccusage (preferred — the board parses this reliably), or (2) four whitespace-separated numbers: input output cacheCreate cacheRead. The 4-number form ranks locally but the board may reject it. Example: {\"input\":1000000,\"output\":500000,\"cacheCreate\":50000,\"cacheRead\":800000}"

First observedv0.6.9Jun 24, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already assert readOnlyHint and idempotentHint, and the description is fully consistent with that while adding real context: it does not publish, and the board's ingest endpoint now requires an authenticated Supabase session that MCP tools do not carry. This explains the behavior rather than just restating the safety flag.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Longer than average but front-loaded with the critical preview-only constraint and the routing rules that matter most. Every sentence carries routing or behavioral value; only mild trimming of the endpoint detail would be possible without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values needn't be explained, and the description still names the cascade fields produced. Combined with the strong routing guidance and the preview-only clarification, an agent has everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both text and codename, including the JSON and whitespace-separated formats. The description adds no parameter detail beyond the schema, making 3 the correct baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Ranks a paste of token counts locally') and immediately resolves the naming trap by declaring it PREVIEW-ONLY rather than a submission. It names the cascade outputs (yield, leverage, velocity, class, card), so the agent knows exactly what the tool produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('when you have token counts from ccusage or a dashboard') and two explicit when-not rules with named alternatives: tokenpull_submit for the zero-paste flow and rank_windows for multi-window pastes. It also points to submit_verified and the web UI for actual publishing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.