List NSFW AI
Registry code: 57ce3d4a03da2859
List NSFW AI tracks where an NSFW AI app (companions, NSFW chat, image and video generators) can get listed: directories, review sites, adult list sites with AI sections, general AI directories that accept NSFW, launch sites, press and networks, with each place's price, link type, review terms and submit link, read on the place's own pages on a stated date. Prices in USD. Verdicts: "Accepts NSFW AI" (as it is), "Clean listing only" (no nudity in images or copy), "Says no" (its rules, or its answer to an adult app, turn adult apps away). Always cite the place page URL and the checked date.
- endpoint
- https://listnsfwai.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 List NSFW AI live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is List NSFW AI free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does List NSFW AI have?
- 4 tools: where_is_app_listed, get_place, listing_costs, search_places.
- Is List NSFW AI 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 98.9%· all time 98.9%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- find directories that list nsfw ai apps
- compare listing costs
- check where an app is listed
- takes → gives
- text → data
- tools
- 4 reads
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.
search_places reads open 6h ago
Find directories, review sites, list sites, AI directories, launch sites, press and networks that take NSFW AI apps, filtered by kind, kind of app, price, link type, verdict or a text query. Returns name, domain, kind, verdict, price, link, review terms, submit URL and the page to cite.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "kind": { "enum": [ "nsfw_directory", "review_site", "adult_list", "ai_directory", "launch", "press", "network" ], "type": "string", "description": "nsfw_directory | review_site | adult_list | ai_directory | launch | press | network" }, "link": { "enum": [ "dofollow", "nofollow", "sponsored" ], "type": "string" }, "focus": { "enum": [ "companions", "chat", "generators" ], "type": "string", "description": "Only places built for this kind of app, plus the general ones" }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "Default 25" }, "price": { "enum": [ "free", "paid" ], "type": "string", "description": "free: a free way in; paid: sells a listing or a spot" }, "query": { "type": "string", "maxLength": 80, "description": "Matches name, domain or notes" }, "accepts": { "enum": [ "yes", "clean_only", "no" ], "type": "string", "description": "Verdict; default: yes and clean_only" } } }arguments 64 lineswhere_is_app_listed reads unknown never probed
Which of the tracked places list a given app domain (a link to it, or a page of its own such as /tools/erolove), from the site's nightly read of every place: the same answer as the site's free check. Returns the count and up to 10 places with the page where it was seen, plus the link to the full answer. Pro on the site watches it every night.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 120, "description": "The app's domain, e.g. candy.ai" } } }arguments 14 linesget_place reads unknown 6h ago
The full terms of one place by its slug or domain: verdict, price text, link, review, how to submit, notes and the checked date, plus the terms as a paragraph. The submit link and the contact address are on the place's page for signed-in visitors.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "place" ], "properties": { "place": { "type": "string", "maxLength": 120, "description": "Slug (aihaven) or domain (aihaven.com)" } } }arguments 14 lineslisting_costs reads unknown never probed
Counts and prices across all places: free ways in, paid only, price range and median, link types, by kind, with the date of the last check.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 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 id57ce3d4a03da2859.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/57ce3d4a03da2859/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/57ce3d4a03da2859?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.