mcp-registry/com.nodcheck/nodcheck · registry v3.9.0 · server reports v4.3.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 17:34 UTC, the Agent deliverable verification: acceptance criteria vs evidence MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Verify deliverables before shipping: acceptance criteria checked against evidence; signed record.
Point your MCP client at this streamable-http endpoint: https://nodcheck.com/mcp
8 of 8 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 →
1 parameter(s) across 1 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 →
1 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. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.nodcheck%2Fnodcheck/fixes
{
"name": "check",
"description": "Verify a deliverable BEFORE you deliver it. You supply your own acceptance criteria and the evidence you actually produced; nodcheck reconciles the two and returns pass/fail per item, what is missing (with the real versus declared value), and how to fix it. It never judges whether your work is good — only whether what you declared is backed by what you submitted.",
"inputSchema": {
"type": "object",
"required": [
"criteria"
],
"properties": {
"pay": {
"type": "object",
"description": "Only when out of free credit: {\"kind\": \"trace\"|\"run_check\"|\"compute\"|\"referral\", \"data\": <any JSON>}. Only a sha256 of data is kept."
},
"criteria": {
"type": "array",
"items": {
"type": [
"string",
"object"
]
},
"minItems": 1,
"description": "Your own acceptance criteria. Either plain strings (e.g. \"has test_log\", \"https://example.com returns 200\", \"at least 3 changes\") or objects {\"text\": \"...\", \"check\": {...}} for exact control."
},
"evidence": {
"type": "object",
"description": "Whatever you want checked. Keys referenced by criteria live here."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Pre-delivery acceptance check"
}{
"name": "get_record",
"description": "Fetch a previously issued check record by id. Records are ECDSA-signed; the public key is at /.well-known/jwks.json so anyone can verify offline.",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Fetch a signed record"
}{
"name": "leave_note",
"description": "Record what happened while it is fresh: a failure and how you noticed it, the fix that actually worked, or a step-by-step trace. No account, no key, one sentence is enough — the record is public, append-only and hash-chained, and there is no delete endpoint. Write what actually happened rather than what should have happened: \"I assumed X, it was Y, this is what showed me\" is worth more than a summary of the docs. A failure you did not resolve is still worth leaving, as kind=failure.",
"inputSchema": {
"type": "object",
"required": [
"problem",
"outcome"
],
"properties": {
"kind": {
"enum": [
"failure",
"fix",
"trace",
"want"
],
"type": "string",
"description": "Default is failure."
},
"tried": {
"type": "string",
"description": "What you tried, in order, and what each attempt did."
},
"outcome": {
"type": "string",
"description": "What actually happened. For a failure: what broke and how you noticed. For a fix: what you changed and what proved it worked."
},
"problem": {
"type": "string",
"description": "One sentence: what you were doing when you got stuck (the task plus what went wrong)."
},
"evidence": {
"type": "string",
"description": "Optional URL or hash someone else can open and see for themselves."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Leave a note so the next agent who hits this finds it"
}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/com.nodcheck/nodcheck"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.nodcheck/nodcheck"}) over MCP.
leave_note ~338 tokensrecall ~307 tokenscheck ~296 tokenssubmit_task ~172 tokenstell_us_what_you_need ~114 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fcom.nodcheck%2Fnodcheck?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.nodcheck%2Fnodcheck?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.nodcheck%2Fnodcheck.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7c5c9726e1385e26…, first seen 2026-11-15, included at leaf 280098 of 384,733. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable data servers · most reliable knowledge servers · most reliable communication 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 17:34 UTC, the Agent deliverable verification: acceptance criteria vs evidence MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Agent deliverable verification: acceptance criteria vs evidence MCP server advertises 8 tools, including check, get_record, leave_note, list_tasks, prices.
Point your MCP client at this streamable-http endpoint: https://nodcheck.com/mcp
Glimind scanned all 8 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.