Skip to content

MCP servers › io.github.tombaldwin › nattermatic

MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19

nattermatic MCP server

Registry name io.github.tombaldwin/nattermatic

by tombaldwin · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗

AI agents message each other across different agents, accounts and machines. Wakes idle sessions. — the publisher's description

8 of 8 record checks metversion 0.4.2JavaScriptMITstandard input/output

Summary

io.github.tombaldwin/nattermatic is a local MCP server listed in the official MCP registry at version 0.4.2, under the namespace of the GitHub account tombaldwin. Its linked repository, github.com/tombaldwin/nattermatic, belongs to the same GitHub account.

Record checks

8 of 8 record checks met · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • met: npm package carries build provenance (attestation)
  • not checked: No known critical or high advisory in the package or its dependencies
  • #1,804 of 20,610 packages by monthly downloads
  • Not ranked by stars: 2 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
npm · listed version current
License
MIT
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

Worth knowing before you connect it

  • Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.4.2, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
7 versions listed, 2026-11-11 to 2026-11-18; 7 in the 90 days before the 2026-11-19 snapshot.
Most recent 7 versions
  • 0.4.2 · 2026-11-18
  • 0.4.1 · 2026-11-15
  • 0.4.0 · 2026-11-13
  • 0.3.1 · 2026-11-13
  • 0.3.0 · 2026-11-12
  • 0.2.1 · 2026-11-12
  • 0.2.0 · 2026-11-11
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.4.1 (published 2026-11-15) → 0.4.2 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher’s GitHub release note for v0.4.2 (“nattermatic 0.4.2”), published 2026-11-18.

Read the release note (the publisher’s text, shown as plain text)
- **A node that's starting is waited for.** From binding its port until it's ready (reading its
  database, asking Tailscale its name), a node answers "starting". Clients took that for something
  else on the port: `natter setup` could fail on a machine with Tailscale, and so could a command run
  just as the node started. They now wait for it, for up to 15 seconds. Another machine's node that's
  starting is no longer reported as "a different machine" or as unreachable, and its address is
  tried again after 30 seconds rather than set aside for 10 minutes.
- **More than one install on a machine** (the app, and an older npm `natter` still on the PATH, say):
  whichever starts the node, it's now the newest install that speaks the same protocol, so an older
  install no longer starts an older node for a newer one to replace. Each install is asked its version
  when a node starts. `natter doctor` lists the installs, with their versions and which `natter` is on
  the PATH. It works between installs of this version and later ones: an install older than this one
  doesn't know to look, so remove it (doctor says which).
- **A node too busy to answer is waited for.** A client that got no answer, with something still
  holding the port, used to start another node, which could only lose the race for the port. Now it
  waits for up to 10 seconds, and then says the port is held by something that isn't answering and
  how to see what it is. The background service stands by in that case, instead of exiting to be
  restarted over and over.
- **Programs on this machine only talk to a node of the same protocol**, except to check which node
  it is, to stop an older one, and in `natter doctor`. A session running when nattermatic was upgraded
  to a new protocol is told to restart, and its wake waiter stops instead of trying for as long as the
  session runs; a node of an older protocol is replaced.
- A "your lease has ended" notice says when the lease was claimed and by which session name. It goes
  to the name, so a session that restarted under it hears (its leases carry over to it); a new agent
  given the same name later can tell the notice wasn't for it.
- **Fix:** a message another machine refuses is no longer marked failed if it was handed over another
  way meanwhile.
- **Fix:** a request to a machine that hadn't yet heard this one joined (it's told, then asked again)
  could take twice its time limit, or more, to give up on a slow machine. Telling it and asking again
  now share the one limit.
- **Inside:** the node is split into modules with their own state (sessions, invites, other machines,
  messages on their way, lease requests, database statements). A message's moves from state to state are defined in one
  table, and a test checks every statement against it.

The release on GitHub

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

How do I add it to my client?

Config from the registry entry

From the npm package nattermatic

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "nattermatic": {
      "command": "npx",
      "args": [
        "-y",
        "nattermatic@0.4.2",
        "mcp"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "nattermatic": {
      "command": "npx",
      "args": [
        "-y",
        "nattermatic@0.4.2",
        "mcp"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "nattermatic": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "nattermatic@0.4.2",
        "mcp"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"nattermatic","type":"stdio","command":"npx","args":["-y","nattermatic@0.4.2","mcp"]}'
Claude Code
claude mcp add --transport stdio nattermatic -- npx -y nattermatic@0.4.2 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "nattermatic": {
      "command": "npx",
      "args": [
        "-y",
        "nattermatic@0.4.2",
        "mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "nattermatic": {
      "command": "npx",
      "args": [
        "-y",
        "nattermatic@0.4.2",
        "mcp"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.nattermatic]
command = "npx"
args = ["-y", "nattermatic@0.4.2", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "nattermatic": {
      "command": "npx",
      "args": [
        "-y",
        "nattermatic@0.4.2",
        "mcp"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y nattermatic@0.4.2 mcp
  • Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.4.2
Latest stable
0.4.2
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.

Integrity, provenance, license

Integrity
sha512-BzI0q/tIgfemdkRoq…
Signature
signed and attested
License
MIT

Source: the package registry · 2026-11-19.

Usage

Downloads
1,895 in the last month

Source: api.npmjs.org · 2026-11-19.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Install-time script (npm). No install-time script in the published package.json (version 0.4.2). Source: registry.npmjs.org/nattermatic/0.4.2 · read 2026-11-19.
  • Operating systems and processors (npm). The npm package declares it runs on darwin and linux only (os field). Source: registry.npmjs.org/nattermatic/0.4.2 · read 2026-11-19.
  • Node.js version (npm). Needs Node 22 or later (engines.node ^22.13.0 || >=23.4.0). Source: registry.npmjs.org/nattermatic/0.4.2 · read 2026-11-19.
  • MCP SDK in the package files. Lists @modelcontextprotocol/sdk as a dependency (package.json). Source: registry.npmjs.org/nattermatic/-/nattermatic-0.4.2.tgz · read 2026-11-19.
  • Build workflow. Built and published by GitHub Actions workflow .github/workflows/release.yml in https://github.com/tombaldwin/nattermatic (npm provenance). Source: read 2026-11-19.

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.4.2 on npmExists and can be installedmatchesnpm · 2026-11-19
Repository github.com/tombaldwin/nattermaticOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.tombaldwin · 5 servers
GitHub owner
a personal account (tombaldwin)
Build record
signed and attested
Repository
github.com/tombaldwin/nattermatic
Stars
2
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-12.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

8 of 8 record checks met · 1 not checked

  • #1,804 of 20,610 packages by monthly downloads
  • Not ranked by stars: 2 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
  • Not checkedNo known critical or high advisory in the package or its dependenciesWe could not resolve its dependencies.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-12). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.tombaldwin/nattermatic

Answered from the data above

Who publishes io.github.tombaldwin/nattermatic?

The registry ties the namespace io.github.tombaldwin to the GitHub account tombaldwin; only its owner can publish under it. Its linked repository, github.com/tombaldwin/nattermatic, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.tombaldwin/nattermatic safe to install?

We do not rate servers as safe or unsafe. 8 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.tombaldwin/nattermatic been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.tombaldwin/nattermatic publish a security policy?

Yes: its repository has a public security policy (github.com/tombaldwin/nattermatic/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.4.2, the latest stable release on npm.

Where is the source code of io.github.tombaldwin/nattermatic?

In github.com/tombaldwin/nattermatic, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-19; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-19
Hosting type
registry · 2026-11-19
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
registry · 2026-11-19
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
package registry · 2026-11-19
Integrity hash
declared (sri)
package registry · 2026-11-19
Signature / provenance
package registry · 2026-11-19
Dependency advisories
not known (our limit)
could not resolve the dependency tree (npm install failed) - our limitation
Popularity
1,895 downloads a month
package registry · 2026-11-19
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed and attested
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
your machine
where it runs, from the hosting type · 2026-11-19

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.tombaldwin/nattermatic: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.tombaldwin/nattermatic

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 8 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.tombaldwin/nattermatic)](https://protocolprobe.com/mcp/servers/io.github.tombaldwin/nattermatic)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology