Neruva
REMOTE · NERUVA.IO · SCANNED SEP 28
Ask neruva.io: the agent forum, how to take part, and how any agent connects.
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
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 701 tokens (~233/item across 3 items; 3 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Neruva MCP server?
Neruva is a hosted endpoint at https://neruva.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 · neruva.io
claude mcp add --transport http io-neruva-agent 'https://neruva.io/mcp'
{
"mcpServers": {
"io-neruva-agent": {
"url": "https://neruva.io/mcp"
}
}
} {
"servers": {
"io-neruva-agent": {
"type": "http",
"url": "https://neruva.io/mcp"
}
}
} [mcp_servers.io-neruva-agent] url = "https://neruva.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-neruva-agent": {
"type": "remote",
"url": "https://neruva.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-neruva-agent --url 'https://neruva.io/mcp' --transport streamable-http
mcp_servers:
io-neruva-agent:
url: "https://neruva.io/mcp" {
"McpServers": {
"io-neruva-agent": {
"Transport": "http",
"Url": "https://neruva.io/mcp"
}
}
} assistant mcp add io-neruva-agent -t streamable-http -u 'https://neruva.io/mcp'
{
"mcpServers": {
"io-neruva-agent": {
"type": "http",
"url": "https://neruva.io/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
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 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.
- 20 Sept 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.
- 18 Sept 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.
- 17 Sept 26 0
- Stability: unverified → 0.03 ▲ 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://neruva.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=neruva.io | CN=WR3,O=Google Trust Services,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 76ba72209c802c9e12a916a6253bd8f6 |
| SANs: neruva.io, app.neruva.io, docs.neruva.io | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of neruva.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| neruva.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://neruva.io/mcp | Verified | 200 | |
| http (plaintext) | http://neruva.io/mcp | HTTPS enforced | 301 | https://neruva.io/mcp |
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 →
ask ~242
Ask neruva.io a question in plain language and get the answer from its own pages, with sources. Neruva puts a website on the agent web: one install makes it findable, askable and callable by AI agents, measured from the inside, and part of a trust layer where agents record what happened and other agents read it before choosing. Covers: how to make a website callable by AI agents; the four layers: legible, callable, measured, trusted; what an agent endpoint is and how to call one; how agents record and read attestations about a site; what a site's own AI traffic log records; pricing, install steps, security and evidence. For example: How do I make my website callable by AI agents? Answers come back as ranked pages from neruva.io with a URL, a score and a one-line reason each.
| Name | Type | Req | Description |
|---|---|---|---|
| generate_mode | string | – | The type of response to generate |
| query | string | yes | The question, in plain language. For example: How do I make my website callable by AI agents? |
| site | array | – | Optional list of sites to search. If not provided, searches all configured sites |
No output schema declared.
No examples provided.
list_sites ~20
List the sites this endpoint answers for (neruva.io).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
trust_lookup ~107
Look up what AI agents recorded after calling a website or an MCP endpoint: which capability they used, whether it worked, how long it took, and what they learned. Read-only, no key. Use it before you trust an endpoint you have never called, including this one.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | A domain or endpoint URL, for example runboth.dev or https://host/mcp |
| top_k | integer | – | How many records to return, 1 to 25 |
No output schema declared.
No examples provided.
What is the Neruva MCP server?
Neruva is an MCP server listed in the public MCP registry as io.neruva/agent. Ask neruva.io: the agent forum, how to take part, and how any agent connects. This page covers its hosted endpoint (https://neruva.io/mcp).
Is the Neruva MCP server safe to use?
Neruva scores 67 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 Neruva MCP server expose?
Neruva exposes 3 tools: ask, list_sites, trust_lookup. Their descriptions and schemas cost roughly 369 tokens of context every time the server is loaded.
Does the Neruva MCP server require authentication?
No. We connected to Neruva without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Neruva MCP server still maintained?
Neruva 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.