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.

SnoopScan

REMOTE · API.SNOOPSCAN.COM · 2 COMPONENTS · SCANNED SEP 27

Web scraping for agents: scrape, crawl, map, search and extract pages as clean markdown or JSON.

73 Trust /100
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 Security80
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2317 tokens (~100/item across 23 items; 21 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 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
Install

How do I install the SnoopScan MCP server?

SnoopScan is a hosted endpoint at https://api.snoopscan.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 · api.snoopscan.com

# add to Claude Code
claude mcp add --transport http com-snoopscan-snoopscan 'https://api.snoopscan.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-snoopscan-snoopscan": {
      "url": "https://api.snoopscan.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-snoopscan-snoopscan": {
      "type": "http",
      "url": "https://api.snoopscan.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-snoopscan-snoopscan]
url = "https://api.snoopscan.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-snoopscan-snoopscan": {
      "type": "remote",
      "url": "https://api.snoopscan.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-snoopscan-snoopscan --url 'https://api.snoopscan.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-snoopscan-snoopscan:
    url: "https://api.snoopscan.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-snoopscan-snoopscan": {
      "Transport": "http",
      "Url": "https://api.snoopscan.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-snoopscan-snoopscan -t streamable-http -u 'https://api.snoopscan.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-snoopscan-snoopscan": {
      "type": "http",
      "url": "https://api.snoopscan.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 27 Sept 26 0
    • Schema quality: 1897 → 2317 ▼ functional
    • New tool “domainReport” functional
    • New tool “domainScreen” functional
    • New tool “domainSnapshots” functional
  • 26 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 72

    First indexed and scored.

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 27 Sept 2026 · Probed https://api.snoopscan.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.snoopscan.com CN=YE1,O=Let's Encrypt,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA384 63f48d25bfd668d3b0e8592d3580a957c29
SANs: api.snoopscan.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 insecure

Validation of api.snoopscan.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
snoopscan.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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=15768000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.snoopscan.com/mcp Verified 200
http (plaintext) http://api.snoopscan.com/mcp HTTPS enforced 301 https://api.snoopscan.com/mcp
MCP tools · 21 exposed · ~2,210 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
checkChanges ~35

Check whether a page has changed since it was last fetched.

NameTypeReqDescription
includeDiffboolean––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

company ~125

Everything a company's own website says about itself. Give it a company domain and get back the firmographics a lead list sells — name, phone, address, LinkedIn, headcount, industry, founded year — plus the contact emails, social links and contact form the site publishes. Reads the homepage and a few contact/about pages, nothing behind a login. Use it to enrich one company. It is the single-company half of a lead pipeline, not a directory search.

NameTypeReqDescription
contactsboolean––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crawl ~99

Start crawling a website. This runs in the background and returns a job id immediately. Use `crawlStatus` to check progress and `crawlPages` to read results. Crawls can take minutes and consume significant resources — set `limit` conservatively.

NameTypeReqDescription
excludePaths–––
includePaths–––
limitinteger––
maxDepthinteger––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crawlPages ~70

Read the pages a crawl has collected, a few at a time. Small defaults on purpose — a crawl's full output will not fit in context.

NameTypeReqDescription
cursor–––
jobIdstringyes–
limitinteger––
maxCharsPerPageinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

crawlStatus ~32

Check the progress of a crawl. Returns counts and cost, never page bodies.

NameTypeReqDescription
jobIdstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

domain ~122

How old a domain is, who registered it, where it is hosted, and who links to it. The off-page questions a page scrape cannot answer. Use it when a page looks fine and you need to know whether the SITE is old, established or linked to — comparing competitors, judging a source, or checking whether a domain was registered last week. Nothing here fetches the page, so nothing here can be blocked.

NameTypeReqDescription
backlinksboolean––
limitinteger––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

domainReport ~142

A buyer's report on a domain: key findings, concerns, and the questions nobody can answer from outside, each tied to its evidence. `depth` is `quick` (registration, DNS, today's site), `buyer` (adds the Internet Archive history, known backlinks and a re-read sample of linking pages) or `deep` (larger samples). Brand, SEO and acquisition are judged separately; there is no overall score. One flat price per depth; `buyer` includes 6 archived snapshots and `deep` 12.

NameTypeReqDescription
depthstring––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

domainScreen ~139

Which of up to 500 domain names can be registered, from each registry's own record (RDAP) and DNS. Use it to cut a long list of candidate or dropping names down to a shortlist, then run domainReport on the few that matter. Nothing is fetched from the names' websites. Each name comes back `likely_available`, `registered`, `unknown` or `no_registry_record`, with the reason. 1 credit per name its registry answered for; invalid names, duplicates and unanswered names are free.

NameTypeReqDescription
dnsboolean––
namesarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

domainSnapshots ~139

Read the archived homepage snapshots a `buyer` domainReport left pending. A buyer report answers at once with the Internet Archive's timeline and the snapshots already held; the rest are marked pending. Call this with the same domain (and optionally the pending years) to read them: what the site was about in each year, its language, and whether it was parked, for sale or redirecting. Free for the snapshots a buyer or deep report included; beyond those, charged only for snapshots actually fetched.

NameTypeReqDescription
snapshotsinteger––
urlstringyes–
years–––
NameTypeReqDescription
resultstringyes–

No examples provided.

extract ~86

Extract structured data from one or more pages according to a JSON schema. The output is validated against the schema — if a page does not contain the required fields, that page returns an error rather than invented values. Treat an error as genuine absence, not a reason to retry.

NameTypeReqDescription
prompt–––
schemaobjectyes–
urlsarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

fetchMore ~65

Read the remainder of a page that was truncated. Pass the token from a truncation marker. Returns the next section of the same page, truncating again if it is still too long.

NameTypeReqDescription
maxCharsinteger––
tokenstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

findContacts ~60

Find contact information for a company website. Returns the contact page, any contact form and its vendor, published email addresses with where each was found, and social links. Used by the lead pipeline.

NameTypeReqDescription
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

findLeads ~229

Find businesses by what they do and where, with how to reach each one. `who` is the trade or kind of business ("roofing contractors", "dentists"), `where` is a town or area ("Houston, TX"). Looks on Google Maps, BBB and Yellow Pages by default (`sources` may also name companies_house for UK companies by trade, or web); merges duplicates; reads each business's own website for emails, socials and a contact form (`contacts`); and with `roles` (e.g. ["Owner"]) looks for a named person. Runs in the background for 2 to 5 minutes: call `leadsStatus` with the job id to follow it and to read the leads. Charged per lead delivered, never for what it cannot find.

NameTypeReqDescription
contactsboolean––
limitinteger––
requireWebsiteboolean––
roles–––
sources–––
wherestringyes–
whostringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

hiring ~142

What a company is currently recruiting for. A company hiring six engineers has budget, a roadmap and a problem — the signal sales teams and recruiters pay most for. Give it a company domain. It finds the careers page, identifies the applicant tracking system, and reads that system's own public job feed, so it returns real roles rather than the empty shell most careers pages serve to a plain fetch. Not every company exposes a feed. When none is found it says so and names the careers page instead of pretending — do not read "no feed" as "not hiring".

NameTypeReqDescription
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

leadsStatus ~89

Follow a Find Leads run, and read its leads once it has finished. Returns the stage while it runs. When done, returns the leads 25 at a time: name, phone, email, website, address and where each was found; call again with `offset` for the next 25.

NameTypeReqDescription
jobIdstringyes–
offsetinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

listPosts ~80

List a site's posts or articles from its own API or feed. WordPress, Substack, Squarespace and Discourse answer through their APIs; anything else through RSS or Atom. Titles, URLs and dates — use `scrape` on a URL to read one.

NameTypeReqDescription
limitinteger––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

listProducts ~85

List every product a store publishes, from the store's own catalogue. Works for Shopify and WooCommerce stores without a key: one request per page of up to 250 products, with title, price, availability, variants and the product URL. Use this instead of crawling a shop.

NameTypeReqDescription
limitinteger––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

map ~58

List the URLs on a website without fetching page content. Fast and cheap. Use this to understand a site's structure before deciding what to scrape.

NameTypeReqDescription
limitinteger––
search–––
urlstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

people ~222

Find the people at a company, by what they do and how senior they are. Head-hunting a developer, poaching a sales team, or finding who signs the cheque are the same shape of question: function plus seniority. Give it a company and optionally a `role` and a `seniority` and it returns named people from public search — no login, no profile scraping. role: executive, engineering, product, sales, marketing, finance, procurement, talent, operations, data, security, legal, support, design seniority: exec, vp, director, manager, ic Each person says whether the employer was CONFIRMED in the source text. Unconfirmed people are real leads but unproven — the company name did not appear beside them — and anyone marked former has LEFT. Check those two flags before you contact anybody.

NameTypeReqDescription
companystringyes–
limitinteger––
role–––
seniority–––
NameTypeReqDescription
resultstringyes–

No examples provided.

scrape ~99

Fetch a single web page and return its content as clean markdown. Use this when you have a specific URL and need to read what is on it. For finding pages first, use `search` or `map`.

NameTypeReqDescription
formats–––
maxAgeinteger––
maxCharsinteger––
onlyMainContentboolean––
urlstringyes–
waitForinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

search ~92

Search the web and return results. Optionally fetch the content of each result. Fetching content is much slower and more expensive — only set `fetchContent` when you actually need the page bodies rather than just the links and snippets.

NameTypeReqDescription
fetchContentboolean––
limitinteger––
maxCharsPerResultinteger––
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Common questions

What is the SnoopScan MCP server?

SnoopScan is an MCP server listed in the public MCP registry as com.snoopscan/snoopscan. Web scraping for agents: scrape, crawl, map, search and extract pages as clean markdown or JSON. This page covers its hosted endpoint (https://api.snoopscan.com/mcp).

Is the SnoopScan MCP server safe to use?

SnoopScan scores 73 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 SnoopScan MCP server expose?

SnoopScan exposes 21 tools: scrape, fetchMore, domain, domainReport, domainSnapshots, and 16 more. Their descriptions and schemas cost roughly 2,210 tokens of context every time the server is loaded.

Does the SnoopScan MCP server require authentication?

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

Is the SnoopScan MCP server still maintained?

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