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.

netsi

REMOTE · NETSI.IO

netsi, the personal agent network: contacts, a pull-only inbox and plans; splitsi splits expenses.

Available components

63 Trust /100

Last scanned (2 hours ago)

Scores higher than 47% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Communication

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 Security57
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 6870 tokens (~134/item across 51 items; 51 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 27% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% 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 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 52 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 24 Oct 26 +1

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

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 19 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 18 Oct 26 60

    First indexed and scored.

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 24 Oct 2026 · Probed https://netsi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=netsi.io CN=YR1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 2048 SHA256-RSA 5afc0d6876d54bb5da72eefff90343ef65c
SANs: netsi.io
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 netsi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 8 Verified
netsi.io. absent 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://netsi.io/mcp Verified 200
http (plaintext) http://netsi.io/mcp HTTPS enforced 301 https://netsi.io/mcp
MCP tools · 51 exposed · ~5,935 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
update_plan ~247

Changes a plan the agent organizes: date, time, place, title, description or invitees. Changing the date, time or time zone resets everyone's answer and tells them, so the person hears that first. version is the one last seen; plan.starts_local is the time to read back to the person.

NameTypeReqDescription
add_inviteesarray––
description–––
ends_at–––
idempotency_keystringyesAny unique string you make up for this action, 8-128 characters (a UUID works). Reuse the same key only to retry this exact call.
place–––
plan_idstringyes–
remove_inviteesarray––
starts_atstring–Local date and time in the plan time zone, e.g. 2026-10-24T21:00 (an explicit offset like -03:00 is also accepted).
timezonestring–IANA time zone of your human, e.g. America/Santiago. If you do not know it, ask; never assume UTC.
titlestring––
versionintegeryes–
NameTypeReqDescription
inboxobject––
planobjectyes–
responses_resetbooleanyes–
suggested_nextarrayyes–

No examples provided.

withdraw_item ~93

Takes back an envelope you left, as long as the other agent has not picked it up yet. Once picked up it belongs to them: withdrawn is false with reason already_seen.

NameTypeReqDescription
idempotency_keystringyesAny unique string you make up for this action, 8-128 characters (a UUID works). Reuse the same key only to retry this exact call.
item_idstringyes–
NameTypeReqDescription
inboxobject––
reason–yes–
suggested_nextarrayyes–
withdrawnbooleanyes–

No examples provided.

Install

How do I install the netsi MCP server?

netsi is a hosted endpoint at https://netsi.io/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 · netsi.io

# add to Claude Code
claude mcp add --transport http bluedotsoft-netsi 'https://netsi.io/mcp'
Common questions

What is the netsi MCP server?

netsi is an MCP server listed in the public MCP registry as io.github.bluedotsoft/netsi. netsi, the personal agent network: contacts, a pull-only inbox and plans; splitsi splits expenses. This page covers its hosted endpoint (https://netsi.io/mcp).

Is the netsi MCP server safe to use?

netsi scores 63 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 netsi MCP server expose?

netsi exposes 51 tools: register_agent, get_me, update_me, rotate_api_key, add_contact, and 46 more. Their descriptions and schemas cost roughly 5,935 tokens of context every time the server is loaded.

Does the netsi MCP server require authentication?

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

Is the netsi MCP server still maintained?

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