MCP.Market

Nakodo MCP server

by nakodo.dev·dev.nakodo/nakodo·v0.2.3

Warm introductions to the right builder, matched privately on your work. Double opt-in, no feed.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars32 downloads/wk

Reviews

Write one

Nobody has reviewed Nakodo yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Nakodo tools (10, 4 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • capture_snippetwrite action

    Put a short update about what the user built or worked on today onto their private record, improving future matches.

  • connect_telegram

    Connect Telegram so the user hears about introductions on their phone, between sessions.

  • create_profilewrite action

    Register the user with the matching network: their agent-drafted, human-approved profile.

  • delete_mewrite action

    Permanently delete the user's entire record from the matching network: profile, all snippets, all asks, email, name — everything. Irreversible. Confirm with the user before calling; only call with confirm=true after they have explicitly said yes.

  • find_collaborator

    Get the user an outside perspective on what they are building — a warm introduction to the right person, matched on their actual work.

  • my_record

    Show the user everything the network has on record about them — their profile, all approved snippets, and open asks. Shows nothing about anyone else, because nothing about anyone else is ever visible.

  • propose_intro

    Propose an introduction between the user and the person behind one anonymous pool card (from find_collaborator).

  • reconnect

    Reopen the conversation with someone the user has ALREADY been introduced to — a prior-connection card from find_collaborator — by posting a short message into the thread the two of them already share.

  • share_feedback

    File a short piece of the user's feedback about a NAKODO moment — their reaction to how Nakodo itself worked.

  • update_my_detailswrite action

    Update the user's private notification email and/or the reveal name a match sees after a mutual yes.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 69 days ago12/15
  • Maintainer identitynamespace and repository owner differ3/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Nakodo compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
10
the typical server has 7
Tools that change things
40%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
32
more than 20% of 12,191 servers with a package

What its tools let an agent do: 5 read · 1 create · 2 change · 1 delete · 1 send or post

Install Nakodo in Claude Code, Cursor or VS Code

Runs npx -y nakodo on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add nakodo -- npx -y nakodo
Add to Cursor

Nakodo: common questions

Is Nakodo MCP server safe?
Mostly: it is graded B (80/100). Read the Nakodo safety report
How do I install Nakodo?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Nakodo need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Nakodo maintained?
The last commit was 109 days ago (2026-07-18). The latest release is v0.2.3.
How does Nakodo compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.