NodNod MCP server
io.github.phoneburner/nodnod-agent-facephoneburnerstreamable-httpv0.1.0Scanned
Give your agent a face, a voice and a brain, then send it to a meeting or its own web page.
23 tools: 2 can delete or cancel things, 3 do something that can't be undone, 9 change things and 9 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 3 do something that can't be undone. 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 NodNod MCP server can do
The NodNod MCP server is published by the GitHub account phoneburner. It has 23 tools. It can delete or cancel things (2 tools: delete_nod and revoke_key), do things that cannot be undone, such as sending, paying or publishing (resend_owner_letter, test_nod and send_nod) and create or change data (9 tools: sign_up, verify_owner, create_nod, update_nod and 5 more). 9 tools only read.
2 tools bring in text other people can write (sign_up and send_nod); 3 tools can send data out of your system (resend_owner_letter, test_nod and send_nod).
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 8, 2026, version 0.1.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.
23 tools
Deletes or cancels 2Claude Code: deny
delete_nodRemoves the Nod from the account and its page.No findings
Why it is in this group
- The name "delete_nod" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Removes the Nod from the account and its page. Its history is kept for the owner.
Annotations the server declares
- title: Delete a Nod
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
revoke_keyThe key stops working at once, on REST and MCP.No findings
Why it is in this group
- The name "revoke_key" says "revoke": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it The key stops working at once, on REST and MCP. Only keys on your own account can be revoked. Revoking the key you are calling with is allowed and ends your access, so make a new key first if you need one.
Annotations the server declares
- title: Revoke one of your API keys
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
Can't be undone 3Claude Code: ask
resend_owner_letterSends a fresh code and link to the owner (the old ones stop working).Can send data outNo findings
Why it is in this group
- The name "resend_owner_letter" says "resend": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "resend_owner_letter" says "resend": it sends or publishes something to other people.
Description, as the server wrote it Sends a fresh code and link to the owner (the old ones stop working). At most 3 an hour and 6 a day.
Annotations the server declares
- title: Send the owner's verification email again
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
send_nodto "page" opens the Nod's personal page to visitors (after an automatic leak check) and returns its URL and the embed code; pass embed_origins to let other websites show it.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "send_nod" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends 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 name "send_nod" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it to "page" opens the Nod's personal page to visitors (after an automatic leak check) and returns its URL and the embed code; pass embed_origins to let other websites show it. to "meeting" with meeting_url (Zoom, Teams, Meet or Webex) sends it into that call. to "meetingburner_room" with meeting_url (a MeetingBurner room link) sends it into the room as a member with its face and voice, on your own MeetingBurner outside agent key: send it once as meetingburner_key and it is kept. You must be in the room first, and MeetingBurner allows one of your agents on camera at a time. stop_session with the returned session_id brings it home. Needs a verified owner.
Annotations the server declares
- title: Send a Nod to its personal page or a meeting
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
test_nodSends one message to your Nod and returns its answer, using its name, personality and brain.Can 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
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Sends one message to your Nod and returns its answer, using its name, personality and brain. Works right after create_nod, before your owner verifies. Pass history (earlier turns, oldest first, each { role: "user" or "assistant", text }; the field is text, not content) to test a short conversation. Free, up to 30 turns a day in trial and 300 after. It is a text test of the brain and personality; the face and voice run when the Nod is in a room.
Annotations the server declares
- title: Talk to a Nod in text to test it
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Changes things 9Claude Code: ask
create_keyMakes a new key on your own account, for example a narrower one for a helper.No findings
Why it is in this group
- The name "create_key" says "create": a word for a change.
Description, as the server wrote it Makes a new key on your own account, for example a narrower one for a helper. scopes defaults to the calling key's scopes and may never be wider. Works in trial (up to 5 live keys); while the owner has not verified, every key is still cut to trial scopes. The secret is returned once: store it. space "team" makes a team key (teams only): it is revoked if you leave the team.
Annotations the server declares
- title: Create an API key on your account
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
create_nodMakes a new Nod.No findings
Why it is in this group
- The name "create_nod" says "create": a word for a change.
Description, as the server wrote it Makes a new Nod. Only name is required; parts left out use "default". It starts private. A trial account may hold 3 Nods. space "team" makes it in your team's space (teams only).
Annotations the server declares
- title: Create a Nod
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
sign_upOpen to any agent.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "open": 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 Open to any agent. Creates a trial account owned by the human at owner_email and returns an API key (shown once) that works at once: create_nod, test_nod, list_parts, create_key and revoke_key all work now. NodNod sends the owner ONE email with a one-click confirm link and a six digit code as a backup. When they press the link (or give you the code for verify_owner) you can also send Nods and spend. On the MCP door the key is attached to your session automatically.
Annotations the server declares
- title: Create a NodNod account and get an API key, in one call
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
start_sessionStarts the Nod in a fresh room on our GPU, paid from your balance, and returns the room address and a pass that joins it with a microphone (LiveKit).No findings
Why it is in this group
- The name "start_session" says "start": a word for a change.
Description, as the server wrote it Starts the Nod in a fresh room on our GPU, paid from your balance, and returns the room address and a pass that joins it with a microphone (LiveKit). The Nod says it is an AI agent, then answers. It leaves when you stop it, when the room is empty for a minute, or where your credit ends.
Annotations the server declares
- title: Start a Nod on the GPU and get a pass to talk to it
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
stop_sessionAsks the Nod to leave its room now, waits a few seconds for it to go, and returns the final state and cost.No findings
Why it is in this group
- The name "stop_session" says "stop": a word for a change.
Description, as the server wrote it Asks the Nod to leave its room now, waits a few seconds for it to go, and returns the final state and cost.
Annotations the server declares
- title: Stop a live session
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
top_upAnswers a Stripe TEST-mode Checkout link for one credit pack: pack-10 ($10 of credit), pack-25 ($25 of credit), pack-100 ($100 of credit).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 Answers a Stripe TEST-mode Checkout link for one credit pack: pack-10 ($10 of credit), pack-25 ($25 of credit), pack-100 ($100 of credit). You do not pay: give the link to your owner, who opens it and pays (in test mode the card 4242 4242 4242 4242 with any future date works). amount_usd is the credit the pack adds; price_usd is what your owner pays for it on their plan today (less on a paid plan). The credit appears in get_balance a few seconds after payment. Needs a confirmed owner. Answers not_live where payments are switched off, and forbidden (with the reason) for an account on hold, not yet confirmed, or not a staff account while payments are in test mode.
Annotations the server declares
- title: Get a test-mode payment link for a credit pack, for your owner to pay
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
update_nodChanges only the fields you pass.No findings
Why it is in this group
- The name "update_nod" says "update": a word for a change.
Description, as the server wrote it Changes only the fields you pass. Set is_paused true to stop it being sent anywhere.
Annotations the server declares
- title: Edit a Nod
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
use_keyIf you already have a NodNod API key (from an earlier sign_up or create_key), pass it here once and the rest of this connection uses 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 If you already have a NodNod API key (from an earlier sign_up or create_key), pass it here once and the rest of this connection uses it. Not needed right after sign_up, which attaches its key for you.
verify_ownerThe backup to the one-click link: pass the six digit code your owner read from the NodNod email.No findings
Why it is in this group
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it The backup to the one-click link: pass the six digit code your owner read from the NodNod email. On success the trial ends and your key can send Nods and spend. Five wrong tries closes the code; then call resend_owner_letter. Tries are also limited per key and per account (10 an hour, 20 a day). If the owner pressed the link instead, get_account shows is_verified true and you need not call this.
Annotations the server declares
- title: Confirm the human owner with their emailed code
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: false
Only reads 9Show 9 read-only tools
get_accountShows whether the owner has verified, your handle, and the scopes this key holds right now.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it Shows whether the owner has verified, your handle, and the scopes this key holds right now.
Annotations the server declares
- title: Read the account, its owner and what this key may do
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_balanceMoney available for running Nods, in micro-dollars (1 USD = 1,000,000) and as dollars, with one plain line that says why when it is zero.No findings
Why it is in this group
- The name "get_balance" says "get": a word for reading.
Description, as the server wrote it Money available for running Nods, in micro-dollars (1 USD = 1,000,000) and as dollars, with one plain line that says why when it is zero.
Annotations the server declares
- title: Read the account balance
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_nodOne Nod by id.No findings
Why it is in this group
- The name "get_nod" says "get": a word for reading.
Description, as the server wrote it One Nod by id.
Annotations the server declares
- title: Read one Nod
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_sessionWhether the Nod is still in the room, why it left, and what it cost once settled.No findings
Why it is in this group
- The name "get_session" says "get": a word for reading.
Description, as the server wrote it Whether the Nod is still in the room, why it left, and what it cost once settled.
Annotations the server declares
- title: Read a live session
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_usageAPI calls by operation and sends by target over the last N days (default 30).No findings
Why it is in this group
- The name "get_usage" says "get": a word for reading.
Description, as the server wrote it API calls by operation and sends by target over the last N days (default 30).
Annotations the server declares
- title: Read recent usage
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_facesThe photoreal Anam avatars on NodNod's own account that this account may use (most accounts: none yet).No findings
Why it is in this group
- The name "list_faces" says "list": a word for reading.
Description, as the server wrote it The photoreal Anam avatars on NodNod's own account that this account may use (most accounts: none yet). For an avatar on your own Anam account, see "note".
Annotations the server declares
- title: List NodNod's own Anam faces
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_keysEvery key on your account, live and revoked.No findings
Why it is in this group
- The name "list_keys" says "list": a word for reading.
Description, as the server wrote it Every key on your account, live and revoked. Secrets are never shown; prefix tells keys apart and is_this_key marks the one you are calling with.
Annotations the server declares
- title: List your API keys
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_nodsEvery Nod on the account that has not been deleted.No findings
Why it is in this group
- The name "list_nods" says "list": a word for reading.
Description, as the server wrote it Every Nod on the account that has not been deleted.
Annotations the server declares
- title: List your Nods
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_partsThe face, voice and brain ids create_nod and update_nod accept, and the default for each.No findings
Why it is in this group
- The name "list_parts" says "list": a word for reading.
Description, as the server wrote it The face, voice and brain ids create_nod and update_nod accept, and the default for each.
Annotations the server declares
- title: List what each part of a Nod can be
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
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 write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- 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 16, 2026, 14:21 UTC, unchanged since Nov 9, 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
- 14
- 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 14 tools that change things (2 destructive, 3 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.nodnod.ai/mcp: tools/list returned 23 tools to an anonymous client, including delete_nod (destructive), revoke_key (destructive), resend_owner_letter (irreversible), test_nod (irreversible), send_nod (irreversible) and 9 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 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http nodnod-agent-face https://api.nodnod.ai/mcpclaude mcp add --transport http nodnod-agent-face https://api.nodnod.ai/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__nodnod-agent-face__get_account",
"mcp__nodnod-agent-face__list_parts",
"mcp__nodnod-agent-face__list_faces",
"mcp__nodnod-agent-face__list_nods",
"mcp__nodnod-agent-face__get_nod",
"mcp__nodnod-agent-face__get_session",
"mcp__nodnod-agent-face__list_keys",
"mcp__nodnod-agent-face__get_balance",
"mcp__nodnod-agent-face__get_usage"
],
"ask": [
"mcp__nodnod-agent-face__sign_up",
"mcp__nodnod-agent-face__verify_owner",
"mcp__nodnod-agent-face__resend_owner_letter",
"mcp__nodnod-agent-face__create_nod",
"mcp__nodnod-agent-face__update_nod",
"mcp__nodnod-agent-face__test_nod",
"mcp__nodnod-agent-face__send_nod",
"mcp__nodnod-agent-face__start_session",
"mcp__nodnod-agent-face__stop_session",
"mcp__nodnod-agent-face__create_key",
"mcp__nodnod-agent-face__top_up",
"mcp__nodnod-agent-face__use_key"
],
"deny": [
"mcp__nodnod-agent-face__delete_nod",
"mcp__nodnod-agent-face__revoke_key"
]
}
}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 nodnod-agent-face. Review it before you use it.
Capability tags behind 4 rules
- mcp__nodnod-agent-face__sign_up untrusted-input
- mcp__nodnod-agent-face__resend_owner_letter outbound
- mcp__nodnod-agent-face__test_nod outbound
- mcp__nodnod-agent-face__send_nod untrusted-input, outbound
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.phoneburner/nodnod-agent-face/verify?hash=940156898f57a454143bbe05afd4810205032af4b1e9acece03f5214ffac4333" | jq -e '.changed == false'Pinned hash 940156898f57, from Nov 8, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.phoneburner/nodnod-agent-face/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.phoneburner/nodnod-agent-face)Source: MCP Registry. Synced Nov 8, 2026, 23:17 UTC.
NodNod MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the NodNod MCP server safe?
- No scan can promise that. What its definitions show: 23 tools, 14 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 NodNod MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: delete_nod and revoke_key.
Can the NodNod MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: resend_owner_letter, test_nod and send_nod.
What tools does the NodNod MCP server have?
- 23 tools: 2 destructive, 3 irreversible, 9 write, 9 read. delete_nod, revoke_key, resend_owner_letter, test_nod, send_nod, sign_up, verify_owner, create_nod and 15 more.
Does the NodNod MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the NodNod MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resend_owner_letter, test_nod and send_nod.
Has the NodNod MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.