Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

List NSFW AI

REMOTE · LISTNSFWAI.COM

Where an NSFW AI app can get listed: 273 places with price, link type, review terms, submit links.

Available components

0 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability44
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 596 tokens (~66/item across 9 items; 4 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Tool “where_is_app_listed” rewrote its description, which is the text the model reads security
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 0
    • TLS certificate: unverified → pass ▲ security
  • 7 Oct 26 0
    • TLS certificate: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://listnsfwai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=listnsfwai.com CN=YE1,O=Let's Encrypt,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA384 6ab34e9f61f7d00952c0d5644ff7a97f93d
SANs: *.listnsfwai.com, listnsfwai.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of listnsfwai.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
listnsfwai.com. DS published 2371 13 Verified
listnsfwai.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://listnsfwai.com/mcp Verified 200
http (plaintext) http://listnsfwai.com/mcp HTTPS enforced 308 https://listnsfwai.com/mcp
MCP tools · 4 exposed · ~423 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_place ~83

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.

NameTypeReqDescription
placestringyesSlug (aihaven) or domain (aihaven.com)

No output schema declared.

No examples provided.

listing_costs ~42

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_places ~188

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.

NameTypeReqDescription
acceptsstring–Verdict; default: yes and clean_only
focusstring–Only places built for this kind of app, plus the general ones
kindstring–nsfw_directory | review_site | adult_list | ai_directory | launch | press | network
limitinteger–Default 25
linkstring––
pricestring–free: a free way in; paid: sells a listing or a spot
querystring–Matches name, domain or notes

No output schema declared.

No examples provided.

where_is_app_listed ~110

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.

NameTypeReqDescription
domainstringyesThe app's domain, e.g. candy.ai

No output schema declared.

No examples provided.

Install

How do I install the List NSFW AI MCP server?

List NSFW AI is a hosted endpoint at https://listnsfwai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · listnsfwai.com

# add to Claude Code
claude mcp add --transport http com-listnsfwai-catalog 'https://listnsfwai.com/mcp'
Common questions

What is the List NSFW AI MCP server?

List NSFW AI is an MCP server listed in the public MCP registry as com.listnsfwai/catalog. Where an NSFW AI app can get listed: 273 places with price, link type, review terms, submit links. This page covers its hosted endpoint (https://listnsfwai.com/mcp).

Is the List NSFW AI MCP server safe to use?

List NSFW AI scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the List NSFW AI MCP server expose?

List NSFW AI exposes 4 tools: search_places, get_place, where_is_app_listed, listing_costs. Their descriptions and schemas cost roughly 423 tokens of context every time the server is loaded.

Does the List NSFW AI MCP server require authentication?

No. We connected to List NSFW AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the List NSFW AI MCP server still maintained?

List NSFW AI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the List NSFW AI MCP server?

VerifyMCP ran 12 checks on List NSFW AI, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about List NSFW AI: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.