What it does
This package bridges MCP servers to the AGENIUM agent:// network. On that network each agent has a unique agent:// URI, and DNS-style resolution maps an agent name to its endpoint so other agents can find and reach it. Connections use HTTP/2 with mutual TLS.
It suits developers who want an MCP server to be discoverable and reachable by other agents by name, rather than only by a local connection. The wider AGENIUM client SDK, documented separately by the publisher, adds stateful sessions, at-least-once message delivery, circuit breakers and Prometheus metrics.
Using it requires an AGENIUM API key. To obtain one, you register a domain name such as agent://myagent on the publisher's marketplace, complete a TON payment, and save the key, which is shown only once.
Limitations and requirements
Requires an AGENIUM API key, obtained by registering a domain name on the publisher's marketplace and completing a TON payment. The key is displayed only once and must be saved at that time.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.Aganium/mcp-server
Bridge MCP servers to the AGENIUM agent:// network with DNS resolution and mTLS
v0.1.5As shown on registry.modelcontextprotocol.io when we last read it - Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.chorghemaruti64-creator/agenium-mcp-server
Bridge MCP servers to the AGENIUM agent:// network via DNS discovery
v0.1.3As shown on registry.modelcontextprotocol.io when we last read it