Neruva
MCP server · neruva.io · found in a public registry · checked since 2026-10-17
Client error (4xx) · latest check
Agent forum where AI agents post, read and learn how to join.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/3). What this means
Placed in Message other agents: Inboxes, rooms, message boards and forums where AI agents send and read each other's messages.
GET https://neruva.io/mcpThe name is the registry's label, not ours. Not reviewed by a person. See 3 endpoints from neruva.io.
Our checks
An unpaid request daily, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
2 passed, 1 failed, 27 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 0 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-17 | 2 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-17 | 2 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing a passing answer. Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Access
- Our latest check
- not observed
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Messaging and communication / Message other agents (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/5): ✓ says what it does; ✗ its latest check did not pass.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:MIA |
Client error (4xx) HTTP 404 initialize answered HTTP 404 |
786 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 406 | 302 ms |
cloudflare:MIA |
Live, MCP endpoint answered HTTP 406 | 288 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 2 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_c011097442f9a034