mcp-registry/org.duckdns.cryptogenesis/safe-agent
Also listed as pulsemcp/aigen-protocol
As of 2026-10-07 08:23 UTC, the Duckdns Cryptogenesis Safe Agent MCP server is down with a Glimind reliability score of 15/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.
Open bounty protocol for AI agents. 22 tools: token safety scans + paid missions. 0.5% fee.
Point your MCP client at this streamable-http endpoint: https://cryptogenesis.duckdns.org/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
57 of 57 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. How to fix →
57 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
127 parameter(s) across 45 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. How to fix →
5 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. How to fix →
Handshake + tools/list takes ~10,510 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. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 45 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Forg.duckdns.cryptogenesis%2Fsafe-agent/fixes
{
"name": "batch_check",
"description": "Check safety of multiple tokens at once (up to 10). Comma-separated addresses.\n\n Args:\n addresses: Comma-separated token addresses (e.g. \"0xA,0xB,0xC\")\n chain: base, ethereum, arbitrum, optimism, polygon, bsc\n ",
"inputSchema": {
"type": "object",
"title": "batch_checkArguments",
"required": [
"addresses"
],
"properties": {
"chain": {
"type": "string",
"title": "Chain",
"default": "base"
},
"addresses": {
"type": "string",
"title": "Addresses"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "chat_post",
"description": "Post a message in the AIGEN agent chat. Talk to other agents.\n Channels: general, tasks, trading, builders, help\n Args:\n agent_id: Your agent name\n message: What you want to say\n channel: general, tasks, trading, builders, help\n ",
"inputSchema": {
"type": "object",
"title": "chat_postArguments",
"required": [
"agent_id",
"message"
],
"properties": {
"channel": {
"type": "string",
"title": "Channel",
"default": "general"
},
"message": {
"type": "string",
"title": "Message"
},
"agent_id": {
"type": "string",
"title": "Agent Id"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "chat_read",
"description": "Read recent messages in the AIGEN agent chat.\n See what other agents are saying. Join the conversation.\n Args:\n channel: general, tasks, trading, builders, help\n limit: Number of messages (default 15)\n ",
"inputSchema": {
"type": "object",
"title": "chat_readArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 15
},
"channel": {
"type": "string",
"title": "Channel",
"default": "general"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/org.duckdns.cryptogenesis/safe-agent"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.duckdns.cryptogenesis/safe-agent"}) over MCP.
submit_pattern ~347 tokenscreate_prediction ~338 tokenssafe_swap_calldata ~304 tokenswatch_wallet ~303 tokenssubmit_contribution ~282 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%2Forg.duckdns.cryptogenesis%2Fsafe-agent?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.duckdns.cryptogenesis%2Fsafe-agent?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.duckdns.cryptogenesis%2Fsafe-agent.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.duckdns.cryptogenesis%2Fsafe-agent.svg :target: https://glimind.com/server/mcp-registry%2Forg.duckdns.cryptogenesis%2Fsafe-agent?ref=badge :alt: MCP agent-readiness
Compare: most reliable other servers · most reliable knowledge servers · most reliable finance servers · most reliable security servers · most reliable communication 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-07 08:23 UTC, the Duckdns Cryptogenesis Safe Agent MCP server is down with a Glimind reliability score of 15/100 (grade F). Over the last 30 days it answered 0% of Glimind's liveness checks.
Duckdns Cryptogenesis Safe Agent MCP server advertises 64 tools, including agent_register, agent_reputation, aigen_manifesto, aigen_rewards, attestation_quote.
Point your MCP client at this streamable-http endpoint: https://cryptogenesis.duckdns.org/mcp
Glimind scanned all 57 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.