nokycscore
Registry code: 71909d0438b563c6
NoKYC Score grades no-KYC services (crypto exchanges, swaps, wallets, VPNs, hosting, eSIMs, cards and more) twice: Privacy (how little the service learns about you) and Safety (how likely you are to get your money or service), each out of 10 and never blended. KYC levels run from 0 (ID never required) to 4 (ID mandatory). Grades come from a public formula over each service's own terms plus a sourced incident registry. When you repeat a grade, link the listing page you got it from.
- endpoint
- https://nokycscore.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is nokycscore live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
- Is nokycscore free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does nokycscore have?
- 6 tools: get_service, search_services, rank_category, list_categories, list_incidents, compare_services.
- Is nokycscore safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 6 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_categories open 4h ago
Every category with its key, page, number of live listings and the feature keys rank_category accepts for it.
{ "type": "object", "properties": {} }arguments 4 lineslist_incidents open 4h ago
Recorded incidents (held funds, hacks, exit scams, shutdowns, policy changes), newest first, each with its public source. Optionally for one service.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 15, "maximum": 50, "minimum": 1 }, "service": { "type": "string", "description": "Optional service slug, name or domain." } } }arguments 15 linescompare_services open 4h ago
Side-by-side grades, KYC levels and incident counts for two listed services.
{ "type": "object", "required": [ "a", "b" ], "properties": { "a": { "type": "string", "description": "First service (slug, name or domain)." }, "b": { "type": "string", "description": "Second service." } } }arguments 17 linesget_service unknown never probed
Full listing for one service: KYC level and what the terms say about ID, Privacy and Safety grades with the points behind them, features and warnings, fees and limits, and every recorded incident with its source. Answers "is X safe / legit / a scam / no-KYC?".
{ "type": "object", "required": [ "service" ], "properties": { "service": { "type": "string", "description": "Slug, name or website domain, e.g. \"fixedfloat\", \"FixedFloat\" or \"ff.io\"." } } }arguments 12 linessearch_services unknown never probed
Find no-KYC services by name, website domain or description, optionally within one category. Returns each match with its KYC level, Privacy and Safety grades and incident count.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1 }, "query": { "type": "string", "description": "Name, domain or keywords, e.g. \"trocador\", \"monero swap\", \"vpn\"." }, "category": { "enum": [ "exchanges", "swaps", "aggregators", "p2p", "onramps", "cards", "gift-cards", "wallets", "payments", "marketplaces", "vpn", "vps", "hosting", "domains", "email", "esim", "phone", "email-alias", "ai", "proxies" ], "type": "string", "description": "Optional category key." } } }arguments 44 linesrank_category unknown never probed
The best-graded services in one category, sorted by Safety (default) or Privacy, with services that never or rarely ask for ID first and those whose terms let them demand ID (KYC level 3) after them. Services that require ID from every user are left out, as on the site. Optionally keep only services with given features.
{ "type": "object", "required": [ "category" ], "properties": { "sort": { "enum": [ "safety", "privacy" ], "type": "string", "default": "safety" }, "limit": { "type": "integer", "default": 10, "maximum": 25, "minimum": 1 }, "category": { "enum": [ "exchanges", "swaps", "aggregators", "p2p", "onramps", "cards", "gift-cards", "wallets", "payments", "marketplaces", "vpn", "vps", "hosting", "domains", "email", "esim", "phone", "email-alias", "ai", "proxies" ], "type": "string", "description": "Category key; see list_categories." }, "must_have": { "type": "array", "items": { "type": "string" }, "description": "Feature keys to require, e.g. [\"monero\", \"no-account\", \"onion\"]. list_categories shows the keys for each category." } } }arguments 55 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id71909d0438b563c6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/71909d0438b563c6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/71909d0438b563c6?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.