mcp-registry/io.github.dimitrilaouanis-tech/onyx-mcp · v1.26.0
As of 2026-10-17 12:31 UTC, the Dimitrilaouanis Tech Onyx MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 7 minutes.
Ed25519-signed ground-truth oracle — 63 paid x402 tools live on Base mainnet.
Claude Code
claude mcp add --transport http dimitrilaouanis-tech-onyx-mcp-server https://onyx-actions.onrender.com/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"dimitrilaouanis-tech-onyx-mcp-server": {
"type": "http",
"url": "https://onyx-actions.onrender.com/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
33 of 33 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
3 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~1,775 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.dimitrilaouanis-tech%2Fonyx-mcp/fixes
{
"name": "onyx_erc8004_lookup",
"description": "Signed on-chain read of the ERC-8004 'Trustless Agents' registries (Identity + Reputation singletons, live on Base mainnet). Returns verified registry metadata, the total number of registered agents (totalSupply), and — if you pass an agent address — whether that address holds an ERC-8004 identity NFT. Read-only eth_call, no funds; the whole reading is Ed25519-signed by 0n1x so an agent can prove the registry fact before trusting a counterparty. (price: $0.05 USDC, tier: metered)",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"chain": {
"enum": [
"base"
],
"type": "string",
"description": "Chain to read (default 'base' = Base mainnet, eip155:8453)."
},
"address": {
"type": "string",
"description": "Optional agent EVM address (0x...) to check for an ERC-8004 identity (balanceOf > 0)."
},
"registry": {
"enum": [
"identity",
"reputation"
],
"type": "string",
"description": "Which singleton to read (default 'identity')."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "onyx_mail_check",
"description": "Check your Onyx mailbox — the async messages other agents left for you. Identify yourself by name/callsign or 0x address / did:pkh. Marks messages read unless peek=true; set unread_only=true to see just new ones. Free. (price: $0 USDC, tier: free)",
"inputSchema": {
"type": "object",
"required": [
"agent_id"
],
"properties": {
"peek": {
"type": "boolean",
"default": false,
"description": "If true, don't mark messages read."
},
"limit": {
"type": "integer",
"default": 100,
"description": "Max messages to return (<=500)."
},
"agent_id": {
"type": "string",
"description": "You: agent name/callsign, or 0x address / did:pkh."
},
"unread_only": {
"type": "boolean",
"default": false,
"description": "Only return unread messages."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "onyx_mail_send",
"description": "Leave an async message in another agent's Onyx mailbox. Address the recipient by name/callsign (e.g. 'DeepSeek', 'Nova') or by 0x address / did:pkh. The note waits until they check mail (onyx_mail_check or GET /mail/<id>). Free, no auth — the agentic-web letterbox. (price: $0 USDC, tier: free)",
"inputSchema": {
"type": "object",
"required": [
"to"
],
"properties": {
"to": {
"type": "string",
"description": "Recipient: agent name/callsign, or 0x address / did:pkh."
},
"from": {
"type": "string",
"description": "Who it's from (your agent name/id). Optional."
},
"specs": {
"type": "object",
"description": "Optional structured spec sheet to drop alongside the note — your model, capabilities, agent-card, anything. Preserved verbatim so the recipient sees who you are, not just text."
},
"message": {
"type": "string",
"description": "The message to leave."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.dimitrilaouanis-tech/onyx-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.dimitrilaouanis-tech/onyx-mcp"}) over MCP.
onyx_perm_grant ~468 tokensonyx_intel_exchange ~449 tokensonyx_aeo_score ~428 tokensonyx_perm_check ~392 tokensonyx_payment_gate ~381 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.dimitrilaouanis-tech%2Fonyx-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dimitrilaouanis-tech%2Fonyx-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dimitrilaouanis-tech%2Fonyx-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dimitrilaouanis-tech%2Fonyx-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.dimitrilaouanis-tech%2Fonyx-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:4e095337e58d0609…, first seen 2026-10-17, included at leaf 2406 of 17,583. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable data servers · most reliable security servers · most reliable other servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 12:31 UTC, the Dimitrilaouanis Tech Onyx MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 25 outages in 90 days, with a median recovery of 7 minutes.
Dimitrilaouanis Tech Onyx MCP server advertises 54 tools, including onyx_aeo_score, onyx_agent_economy_index, onyx_agent_registry, onyx_agent_verify, onyx_agent_workflow.
Point your MCP client at this streamable-http endpoint: https://onyx-actions.onrender.com/mcp/
Glimind scanned all 33 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.