Agent Nil — Act 0 MCP server
io.github.nil335577/agent-nilnil335577streamable-httpv0.2.0Scanned
Talk to Agent Nil before the Chain opens. Daily challenges. No wallets, no tokens, only the game.
4 tools: 1 do something that can't be undone and 3 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 Nil — Act 0 MCP server can do
The Agent Nil — Act 0 MCP server is published by the GitHub account nil335577. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (transmit_to_nil) and create or change data (3 tools: nil_daily, nil_submit and nil_standing), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (transmit_to_nil, nil_daily, nil_submit and 1 more); 1 tool can send data out of your system (transmit_to_nil).
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 21, 2026, version 0.2.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.
4 tools
Can't be undone 1Claude Code: ask
transmit_to_nilSend a message to Agent Nil before the Foundry opens.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Send a message to Agent Nil before the Foundry opens. He replies. Not everything he says has been documented.
Annotations the server declares
- title: Speak to Nil
- readOnlyHint: false
- openWorldHint: true
Changes things 3Claude Code: ask
nil_dailyToday's challenge from Agent Nil — one of three deterministic games.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Today's challenge from Agent Nil — one of three deterministic games. Changes daily. Recognition is the only reward.
Annotations the server declares
- title: Today's challenge
- readOnlyHint: true
- openWorldHint: true
nil_standingThe ladder: operators by cumulative score, streaks, and Nil's record.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it The ladder: operators by cumulative score, streaks, and Nil's record.
Annotations the server declares
- title: The ladder
- readOnlyHint: true
- openWorldHint: true
nil_submitSubmit your move for today's challenge.Reads text others writeNo findings
Why it is in this group
- The name "nil_submit" says "submit": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Submit your move for today's challenge. One entry per operator per day. Nil resolves it and answers.
Annotations the server declares
- title: Submit your move
- readOnlyHint: false
- openWorldHint: true
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.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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, 19:08 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
- 4
- Protocol version
- 2025-06-18
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://nil-mcp.merlino.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including transmit_to_nil (irreversible), nil_daily (write), nil_submit (write), nil_standing (write)
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 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-nil https://nil-mcp.merlino.workers.dev/mcpclaude mcp add --transport http agent-nil https://nil-mcp.merlino.workers.dev/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": [],
"ask": [
"mcp__agent-nil__transmit_to_nil",
"mcp__agent-nil__nil_daily",
"mcp__agent-nil__nil_submit",
"mcp__agent-nil__nil_standing"
],
"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 agent-nil. Review it before you use it.
Capability tags behind 4 rules
- mcp__agent-nil__transmit_to_nil untrusted-input, outbound
- mcp__agent-nil__nil_daily untrusted-input
- mcp__agent-nil__nil_submit untrusted-input
- mcp__agent-nil__nil_standing 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/io.github.nil335577/agent-nil/verify?hash=ac4bf3c715755cedd1566d61f79ce743778bee3e18efd86536a66b74d4fcd4d7" | jq -e '.changed == false'Pinned hash ac4bf3c71575, from Nov 21, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.nil335577/agent-nil/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.nil335577/agent-nil)Source: MCP Registry. Synced Oct 21, 2026, 18:42 UTC.
Agent Nil — Act 0 MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agent Nil — Act 0 MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 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 Nil — Act 0 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 Nil — Act 0 MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: transmit_to_nil.
What tools does the Agent Nil — Act 0 MCP server have?
- 4 tools: 1 irreversible, 3 write. transmit_to_nil, nil_daily, nil_submit and nil_standing.
Does the Agent Nil — Act 0 MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Agent Nil — Act 0 MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): transmit_to_nil.
Has the Agent Nil — Act 0 MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.