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.

Neonia: The Cloud Backend for AI Agents

REMOTE · MCP.NEONIA.IO · SCANNED OCT 6

Multiple MCP tools, persistent graph memory, token-saving data pointers, and more.

Available components

remote · mcp.neonia.io 20
−13 this week 20 Trust /100

Degraded

One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

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 Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Neonia: The Cloud Backend for AI Agents MCP server?

Neonia: The Cloud Backend for AI Agents is a hosted endpoint at https://mcp.neonia.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 · mcp.neonia.io

# add to Claude Code
claude mcp add --transport http io-neonia-cloud-backend 'https://mcp.neonia.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-neonia-cloud-backend": {
      "url": "https://mcp.neonia.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-neonia-cloud-backend": {
      "type": "http",
      "url": "https://mcp.neonia.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-neonia-cloud-backend]
url = "https://mcp.neonia.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-neonia-cloud-backend": {
      "type": "remote",
      "url": "https://mcp.neonia.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-neonia-cloud-backend --url 'https://mcp.neonia.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-neonia-cloud-backend:
    url: "https://mcp.neonia.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-neonia-cloud-backend": {
      "Transport": "http",
      "Url": "https://mcp.neonia.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-neonia-cloud-backend -t streamable-http -u 'https://mcp.neonia.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-neonia-cloud-backend": {
      "type": "http",
      "url": "https://mcp.neonia.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 6 Oct 26 −6

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 4 Oct 26 −7
    • HTTPS: unverified → pass ▲ security
  • 3 Oct 26 0
    • HTTPS: pass → unverified ▼ security
  • 2 Oct 26 0
    • Transport: unverified → fail ▼ security
    • Authorization: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 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 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 0
    • HSTS header: unverified → fail ▼ security
    • Authorization: unverified → fail ▼ security
    • Transport: fail → unverified ▼ security
    • TLS certificate: unverified → pass ▲ security
    • Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
    • Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
    • Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
  • 22 Sept 26 0
    • Transport: unverified → fail ▼ security
    • Authorization: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
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 6 Oct 2026 · Probed https://mcp.neonia.io/mcp

TLS unreached

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.neonia.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
neonia.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.neonia.io/mcp Unreachable
http (plaintext) http://mcp.neonia.io/mcp HTTPS enforced
MCP tools

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.

Common questions

What is the Neonia: The Cloud Backend for AI Agents MCP server?

Neonia: The Cloud Backend for AI Agents is an MCP server listed in the public MCP registry as io.neonia/cloud-backend. Multiple MCP tools, persistent graph memory, token-saving data pointers, and more. This page covers its hosted endpoint (https://mcp.neonia.io/mcp).

Is the Neonia: The Cloud Backend for AI Agents MCP server safe to use?

Neonia: The Cloud Backend for AI Agents scores 20 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 Neonia: The Cloud Backend for AI Agents MCP server require authentication?

Its publisher declares that Neonia: The Cloud Backend for AI Agents requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

Is the Neonia: The Cloud Backend for AI Agents MCP server still maintained?

Neonia: The Cloud Backend for AI Agents is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.