Other · Remote MCP server

nestr.io

Connect AI to Nestr for Holacracy, Sociocracy, and self-organizing teams.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.nestr/mcp
Version
0.1.109
Status
Active
Category
other
Transport
Streamable HTTP, stdio (local process)
Package
npm
Published
2026-09-23
Updated
2026-09-23
Publisher
io.nestr
Namespace
Namespace verified by the MCP Registry via the domain nestr.io · how
Repository
github.com/nestr-dev/nestr-mcp
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://mcp.nestr.io/mcpNone

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

Packages

RegistryPackageVersionTransportEnvironment variables
npm@nestr/mcp0.1.109stdioNone declared

How to connect nestr.io

nestr.io is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.nestr.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @nestr/mcp version 0.1.109. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @nestr/mcp@0.1.109.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nestr/mcp@0.1.109"
      ]
    }
  }
}

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More other servers

All 8,395 →
ServerRunsEndpoint or package
Nerdio Manager MCPThe first non-PowerShell client for the Nerdio Manager for MSP API - cross-account AVD fleet.Local · stdioMCP Bundle (.mcpb): Servosity/msp-skills/releases/download/nerdio-v0
NeruvaAsk neruva.io: the agent forum, how to take part, and how any agent connects.Remote · HTTPLive check: ✓ handshakeneruva.io
NessGateResolve a domain to its published AI interfaces: discovery, readiness, and connection plans.Remote · HTTPLive check: ✓ handshakenessgate.com
NestingCalc Calculators37 cutting and woodworking calculators: cut lists, sheet nesting, timber volume, kiln drying.Remote · HTTPLive check: ✓ handshakemcp.nestingcalc.com
Netallion MCP LiteLocal secret & credential checks for AI-assisted dev - runs on your machine, results redacted.Local · stdioPyPI: netallion-mcp-lite
NetBox MCPMCP server for NetBox DCIM/IPAM with read-only and dry-run modes.Local · stdio, HTTPPyPI: netbox-mcp
Netcafe ChinaChina facts a server outside China cannot get: real mainland reachability, 调休 holidays, ID/phone val.Remote · HTTPLive check: ✓ handshakeainetcafe.com
netdiag MCPMCP server wrapping dig, ping, mtr, whois and TLS/HTTP checks for on-demand network diagnostics.Local · stdioPyPI: netdiag-mcp