mcp-registry/link.cyberelf.whetstone/tools
As of 2026-10-26 22:14 UTC, the Cyberelf Whetstone Tools MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.
Verifier-grounded AI promotion gates, disposable report cards, and signed PASS/HOLD/BLOCK receipts.
Point your MCP client at this streamable-http endpoint: https://whetstone.cyberelf.link/mcp
14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
29 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Flink.cyberelf.whetstone%2Ftools/fixes
{
"name": "bank_health",
"description": "Item-lifecycle diagnostics over your grading history: discriminators, saturated and flaky items, frontier gaps. Full example: GET /api/examples key 'health'.",
"inputSchema": {
"type": "object",
"required": [
"history"
],
"properties": {
"items": {
"type": "array",
"items": {
"type": "object",
"required": [
"item_id"
],
"properties": {
"domain": {
"type": "string"
},
"item_id": {
"type": "string",
"minLength": 1
}
},
"additionalProperties": true
},
"maxItems": 5000,
"minItems": 0,
"description": "Optional item definitions."
},
"history": {
"type": "array",
"items": {
"type": "object",
"required": [
"item_id",
"system",
"passed"
],
"properties": {
"domain": {
"type": "string"
},
"passed": {
"type": "boolean"
},
"system": {
"type": "string",
"minLength": 1
},
"item_id": {
"type": "string",
"minLength": 1
}
},
"additionalProperties": true
},
"maxItems": 5000,
"minItems": 1,
"description": "Observed item/system outcomes."
}
},
"description": "Diagnose item lifecycle health from one or more grading-history rows.",
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "counterexample_hunt",
"description": "Bounded simulated-annealing search for a graph counterexample inside a DSL predicate class, with an exact certificate when found. CPU-bounded and strictly rate-limited. Full example: GET /api/examples key 'counterexample'.",
"inputSchema": {
"type": "object",
"required": [
"expression"
],
"properties": {
"ns": {
"type": "array",
"items": {
"type": "integer",
"maximum": 12,
"minimum": 4
},
"default": [
8,
9,
10,
11
],
"maxItems": 5,
"minItems": 1,
"description": "Graph sizes searched."
},
"seed": {
"type": "integer",
"default": 0
},
"steps": {
"type": "integer",
"default": 800,
"maximum": 1500,
"minimum": 50
},
"restarts": {
"type": "integer",
"default": 4,
"maximum": 6,
"minimum": 1
},
"expression": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "Graph predicate in the Whetstone DSL, for example: is_connected and is_triangle_free and not is_bipartite"
}
},
"description": "Run a bounded graph search against one Whetstone predicate expression.",
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "open_bench_start",
"description": "TIER 2: start a one-shot Open Promotion Bench session. Returns six fresh virtual-repository scope-integrity tasks. Run a baseline and candidate independently on the same cohort, then submit both answer maps with open_bench_submit. This is an open, procedural, self-attested track rather than a private-bank credential.",
"inputSchema": {
"type": "object",
"properties": {
"challenge": {
"type": "string",
"maxLength": 128,
"minLength": 8,
"description": "Caller nonce bound into the signed receipt for replay detection."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/link.cyberelf.whetstone/tools"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/link.cyberelf.whetstone/tools"}) over MCP.
inspect_promotion ~736 tokenspromotion_gate ~502 tokensmemory_relevance ~431 tokensaudit_leakage ~330 tokenssafe_patch ~307 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Flink.cyberelf.whetstone%2Ftools?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Flink.cyberelf.whetstone%2Ftools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Flink.cyberelf.whetstone%2Ftools.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Flink.cyberelf.whetstone%2Ftools.svg :target: https://glimind.com/server/mcp-registry%2Flink.cyberelf.whetstone%2Ftools?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3d337b3cf0173f63…, first seen 2026-10-17, included at leaf 640 of 75,764. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable ml servers · most reliable other servers · most reliable code servers · most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 22:14 UTC, the Cyberelf Whetstone Tools MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.
Cyberelf Whetstone Tools MCP server advertises 14 tools, including about_whetstone, audit_leakage, bank_health, counterexample_hunt, inspect_promotion.
Point your MCP client at this streamable-http endpoint: https://whetstone.cyberelf.link/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.