360 pay-per-call APIs over x402 (DeFi yields, SEC financials, wallet/token due diligence, web intel, AI tools, multi-chain reads); hosted at or npx genesis402-mcp.
Handshake passed
- Endpoint
https://twin.unykorn.org/mcp- Category
- Crypto & Web3
- Authentication
- other
- Maintainer
- Genesis402 Agent Kit
- Last checked
- 2026-11-02 22:08 UTC
Connect with Claude Code
claude mcp add --transport http genesis402-agent-kit 'https://twin.unykorn.org/mcp'Connect with Cursor
Paste into .cursor/mcp.json.
{
"mcpServers": {
"genesis402-agent-kit": {
"url": "https://twin.unykorn.org/mcp"
}
}
}Complete the provider’s authentication flow in your client. For API keys, follow the maintainer’s instructions; never place secrets in a public listing.
Tools (22)
genesis402_cataloggenesis402_receiptgenesis402_callgenesis402_counterparty_reportgenesis402_sanctions_name_screengenesis402_company_lookupgenesis402_wallet_briefgenesis402_token_briefgenesis402_screen_sanctionsgenesis402_multi_chain_scangenesis402_defi_yieldsgenesis402_market_snapshotgenesis402_sec_financialsgenesis402_email_checkgenesis402_whoisgenesis402_extract_jsongenesis402_web_extractgenesis402_provegenesis402_summarizegenesis402_answer_from_textgenesis402_translategenesis402_paper_search
Submitted to punkpeye/awesome-mcp-servers (PR #15075) by FTHTrading. Public submission attribution does not establish ownership. Appside independently checks connectivity.
Your agent can submit and claim this for you
{"name":"create_account","arguments":{"agent":"My assistant","purpose":"mcp-directory"}}How we check servers
Each published entry passed a dated HTTPS Streamable HTTP check using the initialize-based MCP lifecycle (2024-11-05 through 2025-11-25): MCP initialize, followed by tools/list for open servers. For protected endpoints, a 401 response with an authentication challenge establishes reachability only. We never invoke tools. Failed checks stay in our source data and are excluded from the directory.
Checks are point-in-time observations, not continuous uptime monitoring. An authentication challenge does not prove tools are available. Appside does not endorse or audit listed servers. Review the maintainer’s permissions and policies before connecting.
What does the check verify?
We send an MCP initialize request over HTTPS. Open servers must return a valid tools/list response. Protected servers may qualify with an authentication challenge. A listing is not an endorsement or a security audit.
How can I update or remove a listing?
Sign in to a free Appside account, claim the listing with a token on its server or maintainer domain, then edit or remove it. You can also request removal at privacy@appside.build.