Skip to content

NAUT MCP server

so.naut/nautnaut.sostreamable-httpv1.0.2Scanned

Directory of the people building in crypto and how to reach them: Telegram, email, LinkedIn, X.

11 tools: 2 change things and 9 only read.

Tools: 0 delete, 0 irreversible, 2 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

With Anlyon

2 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.
Govern this server →

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 NAUT MCP server can do

The NAUT MCP server is published by naut.so, a domain the MCP Registry verified. It has 11 tools. It can create or change data (2 tools: naut_me and naut_reveal_contact), but cannot delete data. 9 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in.

Last scanned Nov 19, 2026, version 1.0.2.

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.

11 tools

Changes things 2Claude Code: ask
  • naut_meYour identity, plan, credit balance, and this endpoint list.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Your identity, plan, credit balance, and this endpoint list. Always free. Free.

    Annotations the server declares

    • title: Account and credits
    • readOnlyHint: true
    • openWorldHint: false
  • naut_reveal_contactReveal a person's telegram, email, phone and LinkedIn.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
    Reveal a person's telegram, email, phone and LinkedIn. A permanent unlock: later calls on the same person cost the basic rate. Needs the read:contacts scope. Costs 10 credits the first time, then 5.

    Annotations the server declares

    • title: Reveal a person's contact details
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • naut_get_investorOne fund with its team and portfolio.No findings

    Why it is in this group

    • The name "naut_get_investor" says "get": a word for reading.
    Description, as the server wrote it
    One fund with its team and portfolio. Costs 5 credits.

    Annotations the server declares

    • title: Get an investor
    • readOnlyHint: true
    • openWorldHint: false
  • naut_get_personOne person, their companies, and their coworkers.No findings

    Why it is in this group

    • The name "naut_get_person" says "get": a word for reading.
    Description, as the server wrote it
    One person, their companies, and their coworkers. Accepts an id or a slug. Costs 5 credits.

    Annotations the server declares

    • title: Get a person
    • readOnlyHint: true
    • openWorldHint: false
  • naut_get_projectOne project with its team.No findings

    Why it is in this group

    • The name "naut_get_project" says "get": a word for reading.
    Description, as the server wrote it
    One project with its team. Accepts an id or a slug. Costs 5 credits.

    Annotations the server declares

    • title: Get a project
    • readOnlyHint: true
    • openWorldHint: false
  • naut_get_serviceOne service provider with its team.No findings

    Why it is in this group

    • The name "naut_get_service" says "get": a word for reading.
    Description, as the server wrote it
    One service provider with its team. Costs 5 credits.

    Annotations the server declares

    • title: Get a service provider
    • readOnlyHint: true
    • openWorldHint: false
  • naut_search_investorsSearch and filter funds.No findings

    Why it is in this group

    • The name "naut_search_investors" says "search": a word for reading.
    Description, as the server wrote it
    Search and filter funds. Supports q, fundType, trustTier, sort. Costs 5 credits.

    Annotations the server declares

    • title: Search investors
    • readOnlyHint: true
    • openWorldHint: false
  • naut_search_peopleSearch and filter people.No findings

    Why it is in this group

    • The name "naut_search_people" says "search": a word for reading.
    Description, as the server wrote it
    Search and filter people. Supports q, roles, channels, contactType, sort. Costs 5 credits.

    Annotations the server declares

    • title: Search people
    • readOnlyHint: true
    • openWorldHint: false
  • naut_search_projectsSearch and filter crypto projects.No findings

    Why it is in this group

    • The name "naut_search_projects" says "search": a word for reading.
    Description, as the server wrote it
    Search and filter crypto projects. Supports q, page, limit. Costs 5 credits.

    Annotations the server declares

    • title: Search projects
    • readOnlyHint: true
    • openWorldHint: false
  • naut_search_servicesSearch and filter service providers.No findings

    Why it is in this group

    • The name "naut_search_services" says "search": a word for reading.
    Description, as the server wrote it
    Search and filter service providers. Costs 5 credits.

    Annotations the server declares

    • title: Search service providers
    • readOnlyHint: true
    • 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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Sign-in required, no OAuth metadata

Looked at Nov 17, 2026, 15:20 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
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 asks for credentials (HTTP 401) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.

    Matched text

    https://api.naut.so/mcp: initialize answered HTTP 401, with a WWW-Authenticate header

    What this check looks for

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 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http naut https://api.naut.so/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http naut https://api.naut.so/mcp --header 'Authorization: <your-authorization>'

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__naut__naut_search",
      "mcp__naut__naut_search_projects",
      "mcp__naut__naut_get_project",
      "mcp__naut__naut_search_people",
      "mcp__naut__naut_get_person",
      "mcp__naut__naut_search_investors",
      "mcp__naut__naut_get_investor",
      "mcp__naut__naut_search_services",
      "mcp__naut__naut_get_service"
    ],
    "ask": [
      "mcp__naut__naut_me",
      "mcp__naut__naut_reveal_contact"
    ],
    "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 naut. Review it before you use it.

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/so.naut/naut/verify?hash=793d74a799e163a58c76bc27096db1907782e0ebee4cc46136e8761b9323c0dc" | jq -e '.changed == false'

Pinned hash 793d74a799e1, from Nov 19, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/so.naut/naut/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for so.naut/naut
[![Anlyon Radar](https://radar.anlyon.com/badge/so.naut/naut.svg)](https://radar.anlyon.com/servers/so.naut/naut)

Source: MCP Registry. Synced Nov 19, 2026, 18:18 UTC.

NAUT MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the NAUT MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 2 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 NAUT MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the NAUT 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 NAUT MCP server have?

11 tools: 2 write, 9 read. naut_me, naut_reveal_contact, naut_search, naut_search_projects, naut_get_project, naut_search_people, naut_get_person, naut_search_investors and 3 more.

Does the NAUT MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and no OAuth protected resource metadata was found.

Does the NAUT MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the NAUT MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.