Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NodNod

REMOTE · API.NODNOD.AI

Give your agent a face, a voice and a brain, then send it to a meeting or its own web page.

Available components

+3 this week 68 Trust /100

Last scanned (15 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2803 tokens (~121/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 56% of tool parameters carry a description.Partial
  • Structured output schemas are declared (96% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 17 Nov 26 0
    • Tool “list_faces” rewrote its description, which is the text the model reads security
    • Tool “list_faces” changed its title: List NodNod's own Anam faces → List NodNod's own photoreal faces cosmetic
  • 16 Nov 26 +1
    • Tool “get_usage” rewrote its description, which is the text the model reads security
  • 15 Nov 26 0
    • Tool “send_nod” rewrote its description, which is the text the model reads security
  • 13 Nov 26 +1
    • Tool “send_nod” rewrote its description, which is the text the model reads security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 0
    • Tool “delete_nod” rewrote its description, which is the text the model reads security
    • Tool “get_session” rewrote its description, which is the text the model reads security
    • Tool “list_parts” rewrote its description, which is the text the model reads security
    • Tool “resend_owner_letter” rewrote its description, which is the text the model reads security
    • Tool “sign_up” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.nodnod.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.nodnod.ai CN=YR2,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 RSA 2048 SHA256-RSA 676a4986c2bac3f789bcfb5777fd93a07ec
SANs: api.nodnod.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.nodnod.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
nodnod.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy frame-ancestors 'none'
x-frame-options DENY

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.nodnod.ai/mcp Verified 200
http (plaintext) http://api.nodnod.ai/mcp HTTPS enforced 308 https://api.nodnod.ai/mcp
MCP tools · 23 exposed · ~2,657 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_key ~161

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.

NameTypeReqDescription
labelstringyes–
scopesarray––
spacestring–"personal" (the default): yours, and it goes where you go. "team": made in your team's space; it stays with the team if you leave, and a team key is revoked when you do.
NameTypeReqDescription
api_keystringyesStore it now. It is never shown again.
created_atstringyes–
idstringyes–
is_this_keybooleanyes–
labelstringyes–
last_used_atstring|nullyes–
prefixstringyesThe first characters of the key, to tell keys apart. The secret is never shown again.
revoked_atstring|nullyes–
scopesarrayyes–

No examples provided.

create_nod ~322

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).

NameTypeReqDescription
abilitiesarray–Built-in abilities to switch on.
brainstring–A brain id from list_parts, or "default".
brain_tierstring–fast (the default) or big.
facestring–A face id from list_parts, or "default".
face_idstring–The avatar for the outside-anam face: your own Anam avatar id (your Anam key, added in Studio, pays), or a nodnod: id from list_faces. "" for none.
namestringyes–
personalitystring–Who the Nod is and how it talks, in plain words.
slugstring–The last part of the page address, <web>/<handle>/<slug>. Made from the name if left out.
spacestring–"personal" (the default): yours, and it goes where you go. "team": made in your team's space; it stays with the team if you leave, and a team key is revoked when you do.
voicestring–A voice id from list_parts, or "default".
voice_idstring–The voice inside the voice part, from list_parts or the catalogue (am_fenrir, bf_emma...). "" for its default.
NameTypeReqDescription
abilitiesarrayyesThe built-in abilities switched on.
audiencestringyes–
brainstringyes–
brain_tierstringyesfast: quick answers; big: slower and deeper.
created_atstringyes–
facestringyes–
face_idstringyesThe avatar inside the face: an Anam avatar id on your own Anam account, or a nodnod: id from list_faces.
idstringyes–
is_pausedbooleanyes–
namestringyes–
page_urlstring|nullyesThe Nod's page address; null until your owner picks an account address in NodNod Studio.
personalitystringyes–
slugstringyes–
updated_atstringyes–
voicestringyes–
voice_idstringyesThe voice inside the voice part (a Kokoro voice such as am_fenrir); "" for its default.

No examples provided.

delete_nod ~75

Deletes the Nod: it leaves list_nods, and its page and embed answer not found. Its sessions, charges and history are kept. A Nod live in a room right now is refused (conflict): stop its session first, then delete. Deleting cannot be undone through the API.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
idstringyes–
is_deletedbooleanyes–
messagestringyes–
namestringyes–

No examples provided.

get_account ~27

Shows whether the owner has verified, your handle, and the scopes this key holds right now.

Input schema present but exposes no named parameters.

NameTypeReqDescription
display_namestringyes–
handlestring|nullyesThe account address; null until your owner picks one in NodNod Studio.
is_verifiedbooleanyes–
owner_emailstringyes–
owner_idstringyes–
page_base_urlstring|nullyesWhere this account's pages live; null while handle is null.
scopesarrayyesWhat the key you called with may do right now.
trial_max_nodsintegeryes–

No examples provided.

get_balance ~46

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
available_micro_usdintegeryes–
available_usdstringyes–
empty_reason–yesunconfirmed: the owner has not confirmed yet. link_pending: the owner gave you the code (you may send) but the mailbox is not proved yet; the owner signs in to Studio once and the free credit follows…
is_unlimitedbooleanyes–
messagestringyesOne plain line about this balance.

No examples provided.

get_nod ~21

One Nod by id.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
abilitiesarrayyesThe built-in abilities switched on.
audiencestringyes–
brainstringyes–
brain_tierstringyesfast: quick answers; big: slower and deeper.
created_atstringyes–
facestringyes–
face_idstringyesThe avatar inside the face: an Anam avatar id on your own Anam account, or a nodnod: id from list_faces.
idstringyes–
is_pausedbooleanyes–
namestringyes–
page_urlstring|nullyesThe Nod's page address; null until your owner picks an account address in NodNod Studio.
personalitystringyes–
slugstringyes–
updated_atstringyes–
voicestringyes–
voice_idstringyesThe voice inside the voice part (a Kokoro voice such as am_fenrir); "" for its default.

No examples provided.

get_session ~82

Whether the Nod is still in the room, why it left, and what it cost once settled. nod_has_spoken says whether the Nod has actually made a sound in its room (true, false, or 'unknown' when the engine cannot say); warning says what to do when a visitor spoke and the Nod has stayed silent.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
charged_micro_usd–yes–
end_reasonstring|nullyes–
messagestring|nullyes–
nod_has_spoken–yes–
session_idstringyes–
statestringyes–
warningstring|nullyes–

No examples provided.

get_usage ~61

API calls by operation and sends by target over the last N days (default 30): page, meeting (an outside Zoom, Teams, Meet or Webex call) and meetingburner_room (a MeetingBurner room).

NameTypeReqDescription
daysinteger––
NameTypeReqDescription
calls_by_operationobjectyes–
sendsobjectyes–
session_seconds–yesNull until sessions are metered by the wallet.
sincestringyes–

No examples provided.

list_faces ~48

The photoreal faces on NodNod's own account that this account may use (most accounts: none yet). To use a face from your own face-service account instead, see "note".

Input schema present but exposes no named parameters.

NameTypeReqDescription
facesarrayyes–
notestringyes–

No examples provided.

list_keys ~39

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
keysarrayyes–

No examples provided.

list_nods ~20

Every Nod on the account that has not been deleted.

Input schema present but exposes no named parameters.

NameTypeReqDescription
nodsarrayyes–

No examples provided.

list_parts ~102

The face, voice and brain ids create_nod and update_nod accept from this account, and the default for each. Photoreal faces are in staff preview: an account that is not staff finds them under previews, not ids. tiers are the three presets (Lifelike, Real, Drawn): set face, voice, brain and brain_tier to a tier's ids to use it; Lifelike and Real wear the photoreal face.

Input schema present but exposes no named parameters.

NameTypeReqDescription
partsarrayyes–
tiersarrayyes–

No examples provided.

resend_owner_letter ~63

Sends a fresh code and link to the owner (the old ones stop working). At most 3 an hour and 6 a day; a letter that could not be sent does not count, but tries are limited to 10 an hour and 20 a day.

Input schema present but exposes no named parameters.

NameTypeReqDescription
sent_tostringyes–

No examples provided.

revoke_key ~63

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.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
created_atstringyes–
idstringyes–
is_this_keybooleanyes–
labelstringyes–
last_used_atstring|nullyes–
prefixstringyesThe first characters of the key, to tell keys apart. The secret is never shown again.
revoked_atstring|nullyes–
scopesarrayyes–

No examples provided.

send_nod ~366

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 as a guest named with "(AI agent)" that says it is an AI, listens and speaks only (no tools), one meeting at a time, at the outside-meeting price; the host may have to let it in. 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. Outside meetings are not open yet: to "meeting" (Zoom, Teams, Meet or Webex) answers not_live here. To "page" and to "meetingburner_room" are not behind this switch.

NameTypeReqDescription
audiencestring–Who may talk to the page: "public" (anyone, the default) or "invited".
embed_originsarray–Websites that may show the embed, e.g. ["https://example.com"]. Left out keeps the current list.
idstringyes–
meeting_urlstring––
meetingburner_keystring–Your MeetingBurner outside agent key. Needed once; it is kept in a vault and never shown again.
tostringyes–
NameTypeReqDescription
audiencestring––
embed_codestring–The one line a website pastes to show this Nod.
next_stepstringyes–
probeobject–The red-team check that runs before a page opens. A failed check keeps the page closed.
send_idstring|nullyesNull when the page stayed closed (status blocked).
session_idstring–For a meeting or a MeetingBurner room: read or stop it with get_session or stop_session.
statusstringyes–
tostringyes–
urlstringyes–

No examples provided.

sign_up ~248

Open to any agent whose human owner is in NodNod's private beta (an invited work email address; any other owner_email is refused with forbidden). 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.

NameTypeReqDescription
display_namestring–Your owner's name, shown on the personal page ("An AI agent put here by <name>"). Left out, the page says "its owner".
handlestring–The personal page path, <web>/<handle> (get_account and send_nod give the full address). Made up if left out.
key_labelstring––
owner_emailstringyesThe human who will be accountable for this account. NodNod emails them one confirm link.
NameTypeReqDescription
api_keystringyesStore it now. It is never shown again.
can_do_nowarrayyesOperations this key can call right now.
handlestringyes–
is_verifiedbooleanyes–
key_idstringyes–
next_stepstringyes–
owner_idstringyes–

No examples provided.

start_session ~90

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.

NameTypeReqDescription
idstringyes–
secondsinteger––
NameTypeReqDescription
max_secondsintegeryes–
room_namestringyes–
room_passstringyes–
room_urlstringyes–
session_idstringyes–

No examples provided.

stop_session ~42

Asks the Nod to leave its room now, waits a few seconds for it to go, and returns the final state and cost.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
charged_micro_usd–yes–
end_reasonstring|nullyes–
messagestring|nullyes–
nod_has_spoken–yes–
session_idstringyes–
statestringyes–
warningstring|nullyes–

No examples provided.

test_nod ~138

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.

NameTypeReqDescription
historyarray––
idstringyes–
textstringyes–
NameTypeReqDescription
replystringyes–
turns_left_todayintegeryes–

No examples provided.

top_up ~205

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.

NameTypeReqDescription
pack_idstringyesOne of: pack-10 ($10 of credit), pack-25 ($25 of credit), pack-100 ($100 of credit).
NameTypeReqDescription
amount_usdstringyes–
checkout_urlstringyesGive this to your owner to open and pay. It expires after 24 hours.
modestringyes–
next_stepstringyes–
pack_idstringyes–
price_usdstringyes–

No examples provided.

update_nod ~262

Changes only the fields you pass. Set is_paused true to stop it being sent anywhere.

NameTypeReqDescription
abilitiesarray–Built-in abilities to switch on.
brainstring–A brain id from list_parts, or "default".
brain_tierstring–fast (the default) or big.
facestring–A face id from list_parts, or "default".
face_idstring–The avatar for the outside-anam face: your own Anam avatar id (your Anam key, added in Studio, pays), or a nodnod: id from list_faces. "" for none.
idstringyes–
is_pausedboolean––
namestring––
personalitystring–Who the Nod is and how it talks, in plain words.
slugstring–The last part of the page address, <web>/<handle>/<slug>. Made from the name if left out.
voicestring–A voice id from list_parts, or "default".
voice_idstring–The voice inside the voice part, from list_parts or the catalogue (am_fenrir, bf_emma...). "" for its default.
NameTypeReqDescription
abilitiesarrayyesThe built-in abilities switched on.
audiencestringyes–
brainstringyes–
brain_tierstringyesfast: quick answers; big: slower and deeper.
created_atstringyes–
facestringyes–
face_idstringyesThe avatar inside the face: an Anam avatar id on your own Anam account, or a nodnod: id from list_faces.
idstringyes–
is_pausedbooleanyes–
namestringyes–
page_urlstring|nullyesThe Nod's page address; null until your owner picks an account address in NodNod Studio.
personalitystringyes–
slugstringyes–
updated_atstringyes–
voicestringyes–
voice_idstringyesThe voice inside the voice part (a Kokoro voice such as am_fenrir); "" for its default.

No examples provided.

use_key ~69

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.

NameTypeReqDescription
api_keystringyesA key starting nod_sk_.

No output schema declared.

No examples provided.

verify_owner ~107

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.

NameTypeReqDescription
codestringyes–
NameTypeReqDescription
is_verifiedbooleanyes–
next_stepstringyesWhat the code did, and what the link still does.

No examples provided.

Install

How do I install the NodNod MCP server?

NodNod is a hosted endpoint at https://api.nodnod.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.nodnod.ai

# add to Claude Code
claude mcp add --transport http phoneburner-nodnod-agent-face 'https://api.nodnod.ai/mcp'
Common questions

What is the NodNod MCP server?

NodNod is an MCP server listed in the public MCP registry as io.github.phoneburner/nodnod-agent-face. Give your agent a face, a voice and a brain, then send it to a meeting or its own web page. This page covers its hosted endpoint (https://api.nodnod.ai/mcp).

Is the NodNod MCP server safe to use?

NodNod scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the NodNod MCP server expose?

NodNod exposes 23 tools: sign_up, verify_owner, resend_owner_letter, get_account, list_parts, and 18 more. Their descriptions and schemas cost roughly 2,657 tokens of context every time the server is loaded.

Does the NodNod MCP server require authentication?

No. We connected to NodNod without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the NodNod MCP server still maintained?

NodNod is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the NodNod MCP server?

VerifyMCP ran 13 checks on NodNod, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.