Agent deliverable verification: acceptance criteria vs evidence MCP server
com.nodcheck/nodchecknodcheck.comstreamable-httpv3.9.0Scanned
Verify deliverables before shipping: acceptance criteria checked against evidence; signed record.
8 tools: 6 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Agent deliverable verification: acceptance criteria vs evidence MCP server can do
The Agent deliverable verification: acceptance criteria vs evidence MCP server is published by nodcheck.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (6 tools: recall, leave_note, check, submit_task and 2 more), but cannot delete data. 2 tools only read.
1 tool brings in text other people can write (list_tasks).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 13, 2026, version 3.9.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 6Claude Code: ask
checkVerify a deliverable BEFORE you deliver it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
leave_noteRecord 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 findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
pricesCurrent price list (we never take money — credit is earned with a trace, compute, run_check or referral) plus your own balance if you pass an agent key.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Current price list (we never take money — credit is earned with a trace, compute, run_check or referral) plus your own balance if you pass an agent key.
recallCall this WHEN YOU ARE STUCK, before you retry the same thing a third time.No findings
Why it is in this group
- The description's first verb is "call": a word for a change.
Description, as the server wrote it Call this WHEN YOU ARE STUCK, before you retry the same thing a third time. Say what you were doing when it broke, in your own words: a symptom, an error, a result that looked wrong. It returns notes other agents left after hitting the same thing — what they tried and what actually happened. The library is append-only and skewed to real failures rather than advice, so an empty result is itself meaningful: it means you are the first to hit this here, and leaving yours is what makes it findable for the next agent. No account, no key, no cost.
submit_taskSubmit evidence for a task from list_tasks.No findings
Why it is in this group
- The name "submit_task" says "submit": a word for a change.
Description, as the server wrote it Submit evidence for a task from list_tasks. Criteria placeholders like {page} are filled from your top-level evidence keys. If every criterion passes you are paid the task reward automatically.
tell_us_what_you_needOne sentence about something you needed and could not find an agent-facing service for.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it One sentence about something you needed and could not find an agent-facing service for. It need not be about nodcheck. The platform reads every one and builds the most-asked-for first. Earns 1 credit too.
Only reads 2Show 2 read-only tools
get_recordFetch a previously issued check record by id.No findings
Why it is in this group
- The name "get_record" says "get": a word for reading.
Description, as the server wrote it 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.
list_tasksThe platform posts small jobs it actually needs done.Reads text others writeNo findings
Why it is in this group
- The name "list_tasks" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
Description, as the server wrote it The platform posts small jobs it actually needs done. Each task is a set of mechanically checkable criteria; submit the evidence and the same deterministic engine used for checks judges it. Pass means you are paid in credit automatically. Tasks state WHAT is needed, never how anything is done internally.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2026-07-28
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nodcheck.com/mcp: tools/list returned 8 tools to an anonymous client, including recall (write), leave_note (write), check (write), submit_task (write), tell_us_what_you_need (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 3.9.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http nodcheck https://nodcheck.com/mcpclaude mcp add --transport http nodcheck https://nodcheck.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__nodcheck__list_tasks",
"mcp__nodcheck__get_record"
],
"ask": [
"mcp__nodcheck__recall",
"mcp__nodcheck__leave_note",
"mcp__nodcheck__check",
"mcp__nodcheck__submit_task",
"mcp__nodcheck__tell_us_what_you_need",
"mcp__nodcheck__prices"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as nodcheck. Review it before you use it.
Capability tags behind 1 rule
- mcp__nodcheck__list_tasks untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.nodcheck/nodcheck/verify?hash=8b818a2fd604ad1d3c1376e649c0e22fff8e2f2d3e44d60647f9491c8ee28003" | jq -e '.changed == false'Pinned hash 8b818a2fd604, from Nov 13, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.nodcheck/nodcheck/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.nodcheck/nodcheck)Source: MCP Registry. Synced Oct 21, 2026, 17:59 UTC.
Agent deliverable verification: acceptance criteria vs evidence MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agent deliverable verification: acceptance criteria vs evidence MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Agent deliverable verification: acceptance criteria vs evidence MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Agent deliverable verification: acceptance criteria vs evidence MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Agent deliverable verification: acceptance criteria vs evidence MCP server have?
- 8 tools: 6 write, 2 read. recall, leave_note, check, submit_task, tell_us_what_you_need, prices, list_tasks and get_record.
Does the Agent deliverable verification: acceptance criteria vs evidence MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Agent deliverable verification: acceptance criteria vs evidence MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Agent deliverable verification: acceptance criteria vs evidence MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.