Read the chain
before you trade.
For AI agents and the people who build them. Give an agent the same reads a Cyclops scan makes, so it sees the creator’s record, the holders and the flags before it buys.
Plug it
in.
@cyclops/mcp is an MCP server that runs over stdio, has no dependencies and needs Node 18 or later. Each answer starts with a short plain-text digest, followed by the JSON the API returned. It never describes a token as safe.
{
"mcpServers": {
"cyclops": {
"command": "node",
"args": ["/path/to/cyclops/packages/mcp/src/index.mjs"],
"env": { "CYCLOPS_API_KEY": "cyc_…" }
}
}
}claude mcp add cyclops -e CYCLOPS_API_KEY=cyc_… -- node /path/to/cyclops/packages/mcp/src/index.mjsOptional settings: CYCLOPS_API_URL (API origin), CYCLOPS_API_KEY (sent as x-api-key; without one, free limits apply) and CYCLOPS_SITE_URL (used for links). The server lives in packages/mcp of the Cyclops repository.
A key
in one step.
curl -X POST https://cyclopslabs.dev/api/v1/keys/anonymousA free-tier key with no form and no wallet. Two per network per day. It is shown once and tied to nothing, so whoever holds it can revoke it with DELETE /v1/keys/current and the key as x-api-key.
# 1. get a sign-in message for the wallet
curl -X POST https://cyclopslabs.dev/api/v1/auth/nonce -H 'content-type: application/json' -d '{"address": "0x…"}'
# 2. sign the returned message with the wallet, then
curl -X POST https://cyclopslabs.dev/api/v1/keys/instant -H 'content-type: application/json' \
-d '{"address": "0x…", "message": "…", "signature": "0x…"}'A key tied to a wallet, at that wallet’s tier, plus a session, from one signed message. Wallet keys are managed on the account page and can call the partner pre-launch API. Every key response states its hourly limit.
No key,
pay per call.
Pay-per-scan is not switched on for this deployment yet. Use a free API key meanwhile. GET /v1/x402 reports the state live.
curl -i https://cyclopslabs.dev/api/v1/x402/scan/0x…
# 402 Payment Required: price, network, asset, payTo
# retry with the signed payment
curl https://cyclopslabs.dev/api/v1/x402/scan/0x… -H 'X-PAYMENT: <base64 payment payload>'
# 200 with the scan; X-PAYMENT-RESPONSE carries the settlementThe first request answers 402 Payment Required with the price, network and receiving address. The agent signs a payment and retries with it in X-PAYMENT; the scan comes back with an X-PAYMENT-RESPONSE header. A payment is used once. While x402 is off, this route answers 503. The MCP server uses keyed routes and does not pay.