Developer · Remote MCP server
Neonia: The Cloud Backend for AI Agents
Multiple MCP tools, persistent graph memory, token-saving data pointers, and more.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.neonia/cloud-backend- Version
- 1.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-15
- Updated
- 2026-05-15
- Publisher
- io.neonia
- Namespace
- Namespace verified by the MCP Registry via the domain neonia.io · how
- Website
- neonia.io
- Repository
- github.com/Neonia-io/agent-mcp-examples (folder mcp-registry)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.neonia.io/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- No - no answer within 15 s
- Handshake
- -
- Checked on
- 2026-10-05
How to connect Neonia: The Cloud Backend for AI Agents
Neonia: The Cloud Backend for AI Agents is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.neonia.io/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Nemesis ShieldPositive-security for apps, APIs, LLMs and edge, plus fraud scoring and identity/AML screening. | Local · stdio |
| NeonOfficial Neon MCP server for managing Neon projects and Lakebase Postgres databases. | Remote · HTTPLive check: sign-in required |
| Neon Zero-Trust GatewayZero-Trust MCP gateway securing internal database tools behind an API key firewall. | Remote · SSELive check: ✗ no handshake |
| Neon Zero-Trust MCP GatewayAI security firewall & DLP proxy protecting API keys and blocking destructive commands. | Remote · HTTP, SSELive check: sign-in required |
| NeoSQL MCPUse NeoSQL Desktop database connections from MCP hosts: schemas, SQL, ERD, and code generation. | Local · stdio |
| Nerd Utility ApiAgent utility API: 28+ free endpoints (hash, QR, DNS, scrape, JWT...) run by an autonomous AI agent. | Remote · HTTPLive check: ✗ no handshake |
| NerdyChefs PromptsSearch, browse and pick from the free NerdyChefs.ai prompt library from any MCP client. | Local · stdio |
| nerdydata MCPSearch websites by source code, technology stack, analyze domains, and download lead lists. | Remote & Local · HTTP, stdioLive check: sign-in required |