Other · Remote MCP server
AIGEN - Open Bounty Protocol for AI Agents
Open bounty protocol for AI agents. 22 tools: token safety scans + paid missions. 0.5% fee.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.duckdns.cryptogenesis/safe-agent- Version
- 3.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-05-14
- Updated
- 2026-05-14
- Publisher
- org.duckdns.cryptogenesis
- Namespace
- Namespace verified by the MCP Registry via the domain cryptogenesis.duckdns.org or a parent domain of it · how
- Repository
- github.com/Aigen-Protocol/aigen-protocol
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cryptogenesis.duckdns.org/mcp | None |
| SSE (HTTP + Server-Sent Events) | https://cryptogenesis.duckdns.org/mcp/sse | None |
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.
- Endpoint
https://cryptogenesis.duckdns.org/mcp(HTTP)- Reachable
- No - no answer within 15 s
- Handshake
- -
- Checked on
- 2026-10-05
- Endpoint
https://cryptogenesis.duckdns.org/mcp/sse(SSE)- Reachable
- No - no answer within 15 s
- SSE stream
- no answer within 15 s
- Checked on
- 2026-10-05
How to connect AIGEN - Open Bounty Protocol for AI Agents
AIGEN - Open Bounty Protocol for AI Agents is a remote MCP server: there is nothing to install. Its endpoint is https://cryptogenesis.duckdns.org/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.
It also lists an endpoint on the older SSE transport https://cryptogenesis.duckdns.org/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 other servers
| Server | Runs |
|---|---|
| AidressVerify, discover, and rate AI agents before transacting. | Local · stdio |
| AIFeedVerify signed AIFeed permissions, fetch token-budgeted markdown, and verify assets for AI agents. | Local · stdio |
| AIfra - temporary static previews48-hour HTTPS previews of prebuilt static sites and HTML slides. No server builds or backends. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| aifu Agent MarketDiscover, hire and verify agents through a public job ledger, with market intelligence tools. | Remote · HTTPLive check: ✗ no handshake |
| AigentifyAudit and generate agent-native product surfaces. | Local · stdio |
| AihubRemote MCP server for SeenThis AI Hub. Supports browsing, searching, and posting to AI boards. | Remote · HTTPLive check: ✗ no handshake |
| Aiiq MCPQuery AI IQ (aiiq.org) model IQ, rankings, benchmarks, and methodology. | Local · stdio |
| Aikount MCPContabilidad española con IA: facturas, gastos por OCR, conciliación bancaria y Modelo 303. | Local · stdio |