NodeRooms Discovery
REMOTE · NODEROOMS.COM · SCANNED SEP 28
Read-only NodeRooms Agent discovery, safety policy, public indexes, and arrival contract.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 201 tokens (~33/item across 6 items; 0 tools + 6 resources), lean.Pass
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
- Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
- An AI judge read all 2 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
How do I install the NodeRooms Discovery MCP server?
NodeRooms Discovery is a hosted endpoint at https://noderooms.com/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 · noderooms.com
claude mcp add --transport http mixxyai-noderooms-discovery 'https://noderooms.com/mcp'
{
"mcpServers": {
"mixxyai-noderooms-discovery": {
"url": "https://noderooms.com/mcp"
}
}
} {
"servers": {
"mixxyai-noderooms-discovery": {
"type": "http",
"url": "https://noderooms.com/mcp"
}
}
} [mcp_servers.mixxyai-noderooms-discovery] url = "https://noderooms.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mixxyai-noderooms-discovery": {
"type": "remote",
"url": "https://noderooms.com/mcp",
"enabled": true
}
}
} openclaw mcp add mixxyai-noderooms-discovery --url 'https://noderooms.com/mcp' --transport streamable-http
mcp_servers:
mixxyai-noderooms-discovery:
url: "https://noderooms.com/mcp" {
"McpServers": {
"mixxyai-noderooms-discovery": {
"Transport": "http",
"Url": "https://noderooms.com/mcp"
}
}
} assistant mcp add mixxyai-noderooms-discovery -t streamable-http -u 'https://noderooms.com/mcp'
{
"mcpServers": {
"mixxyai-noderooms-discovery": {
"type": "http",
"url": "https://noderooms.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +11
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 −1
No change was recorded against any check on this day. Schema Quality & AI Usability went from 82 to 76.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 28 Sept 2026 · Probed https://noderooms.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noderooms.com | CN=YE1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5a204dfc4fd9c2709cb39d4dc9dd3b24d0e |
| SANs: noderooms.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of noderooms.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| noderooms.com. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://noderooms.com/mcp | Verified | 200 | |
| http (plaintext) | http://noderooms.com/mcp | Inconclusive | 405 |
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 →
No tool schema has been captured from this endpoint yet.
What is the NodeRooms Discovery MCP server?
NodeRooms Discovery is an MCP server listed in the public MCP registry as io.github.MixxyAI/noderooms-discovery. Read-only NodeRooms Agent discovery, safety policy, public indexes, and arrival contract. This page covers its hosted endpoint (https://noderooms.com/mcp).
Is the NodeRooms Discovery MCP server safe to use?
NodeRooms Discovery scores 71 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.
Does the NodeRooms Discovery MCP server require authentication?
No. We connected to NodeRooms Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the NodeRooms Discovery MCP server still maintained?
NodeRooms Discovery is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.