SnoopScan
Web scraping for agents: scrape, crawl, map, search and extract pages as clean markdown or JSON.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'fetchMore' suggests web access but openWorldHint=falsein fetchMore
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"snoopscan": {
"url": "https://api.snoopscan.com/mcp-oauth"
}
}
}Remote endpoints
https://api.snoopscan.com/mcp-oauthstreamable-httphttps://api.snoopscan.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (20)
🟢scrape(url, formats, onlyMainContent, maxChars, maxAge, ...)
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`.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"formats": {
"anyOf": [
{
"items": {
"type": "string"
},
"type": "array"
},
{
"type": "null"
}
],
"default": null,
"title": "Formats"
},
"onlyMainContent": {
"default": true,
"title": "Onlymaincontent",
"type": "boolean"
},
"maxChars": {
"default": 20000,
"title": "Maxchars",
"type": "integer"
},
"maxAge": {
"default": 172800000,
"title": "Maxage",
"type": "integer"
},
"waitFor": {
"default": 0,
"title": "Waitfor",
"type": "integer"
}
},
"required": [
"url"
],
"title": "scrapeArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "scrapeOutput"
}🟢fetchMore(token, maxChars)
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.
Input Schema
{
"type": "object",
"properties": {
"token": {
"title": "Token",
"type": "string"
},
"maxChars": {
"default": 20000,
"title": "Maxchars",
"type": "integer"
}
},
"required": [
"token"
],
"title": "fetchMoreArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "fetchMoreOutput"
}🟢domain(url, backlinks, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"backlinks": {
"default": true,
"title": "Backlinks",
"type": "boolean"
},
"limit": {
"default": 25,
"title": "Limit",
"type": "integer"
}
},
"required": [
"url"
],
"title": "domainArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "domainOutput"
}🟢domainReport(url, depth)
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. Charged for the requests it makes.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"depth": {
"default": "buyer",
"title": "Depth",
"type": "string"
}
},
"required": [
"url"
],
"title": "domainReportArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "domainReportOutput"
}🟢domainSnapshots(url, years, snapshots)
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. Charged only for snapshots actually fetched.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"years": {
"anyOf": [
{
"items": {
"type": "integer"
},
"type": "array"
},
{
"type": "null"
}
],
"default": null,
"title": "Years"
},
"snapshots": {
"default": 6,
"title": "Snapshots",
"type": "integer"
}
},
"required": [
"url"
],
"title": "domainSnapshotsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "domainSnapshotsOutput"
}🟢hiring(url)
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".
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
}
},
"required": [
"url"
],
"title": "hiringArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "hiringOutput"
}🟢people(company, role, seniority, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"company": {
"title": "Company",
"type": "string"
},
"role": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Role"
},
"seniority": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Seniority"
},
"limit": {
"default": 8,
"title": "Limit",
"type": "integer"
}
},
"required": [
"company"
],
"title": "peopleArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "peopleOutput"
}🟢company(url, contacts)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"contacts": {
"default": true,
"title": "Contacts",
"type": "boolean"
}
},
"required": [
"url"
],
"title": "companyArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "companyOutput"
}🟢map(url, search, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"search": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Search"
},
"limit": {
"default": 100,
"title": "Limit",
"type": "integer"
}
},
"required": [
"url"
],
"title": "mapArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "mapOutput"
}🟡crawl(url, limit, maxDepth, includePaths, excludePaths)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
},
"maxDepth": {
"default": 2,
"title": "Maxdepth",
"type": "integer"
},
"includePaths": {
"anyOf": [
{
"items": {
"type": "string"
},
"type": "array"
},
{
"type": "null"
}
],
"default": null,
"title": "Includepaths"
},
"excludePaths": {
"anyOf": [
{
"items": {
"type": "string"
},
"type": "array"
},
{
"type": "null"
}
],
"default": null,
"title": "Excludepaths"
}
},
"required": [
"url"
],
"title": "crawlArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "crawlOutput"
}🟢crawlStatus(jobId)
Check the progress of a crawl. Returns counts and cost, never page bodies.
Input Schema
{
"type": "object",
"properties": {
"jobId": {
"title": "Jobid",
"type": "string"
}
},
"required": [
"jobId"
],
"title": "crawlStatusArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "crawlStatusOutput"
}🟢crawlPages(jobId, cursor, limit, maxCharsPerPage)
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.
Input Schema
{
"type": "object",
"properties": {
"jobId": {
"title": "Jobid",
"type": "string"
},
"cursor": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Cursor"
},
"limit": {
"default": 5,
"title": "Limit",
"type": "integer"
},
"maxCharsPerPage": {
"default": 5000,
"title": "Maxcharsperpage",
"type": "integer"
}
},
"required": [
"jobId"
],
"title": "crawlPagesArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "crawlPagesOutput"
}🟢findLeads(who, where, limit, sources, contacts, ...)
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.
Input Schema
{
"type": "object",
"properties": {
"who": {
"title": "Who",
"type": "string"
},
"where": {
"title": "Where",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
},
"sources": {
"anyOf": [
{
"items": {
"type": "string"
},
"type": "array"
},
{
"type": "null"
}
],
"default": null,
"title": "Sources"
},
"contacts": {
"default": true,
"title": "Contacts",
"type": "boolean"
},
"roles": {
"anyOf": [
{
"items": {
"type": "string"
},
"type": "array"
},
{
"type": "null"
}
],
"default": null,
"title": "Roles"
},
"requireWebsite": {
"default": true,
"title": "Requirewebsite",
"type": "boolean"
}
},
"required": [
"who",
"where"
],
"title": "findLeadsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "findLeadsOutput"
}🟢leadsStatus(jobId, offset)
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.
Input Schema
{
"type": "object",
"properties": {
"jobId": {
"title": "Jobid",
"type": "string"
},
"offset": {
"default": 0,
"title": "Offset",
"type": "integer"
}
},
"required": [
"jobId"
],
"title": "leadsStatusArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "leadsStatusOutput"
}🟢extract(urls, schema, prompt)
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.
Input Schema
{
"type": "object",
"properties": {
"urls": {
"items": {
"type": "string"
},
"title": "Urls",
"type": "array"
},
"schema": {
"additionalProperties": true,
"title": "Schema",
"type": "object"
},
"prompt": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Prompt"
}
},
"required": [
"urls",
"schema"
],
"title": "extractArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "extractOutput"
}🟢search(query, limit, fetchContent, maxCharsPerResult)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"limit": {
"default": 5,
"title": "Limit",
"type": "integer"
},
"fetchContent": {
"default": false,
"title": "Fetchcontent",
"type": "boolean"
},
"maxCharsPerResult": {
"default": 5000,
"title": "Maxcharsperresult",
"type": "integer"
}
},
"required": [
"query"
],
"title": "searchArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "searchOutput"
}🟢checkChanges(url, includeDiff)
Check whether a page has changed since it was last fetched.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"includeDiff": {
"default": false,
"title": "Includediff",
"type": "boolean"
}
},
"required": [
"url"
],
"title": "checkChangesArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "checkChangesOutput"
}🟢listProducts(url, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"limit": {
"default": 200,
"title": "Limit",
"type": "integer"
}
},
"required": [
"url"
],
"title": "listProductsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "listProductsOutput"
}🟢listPosts(url, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
},
"limit": {
"default": 100,
"title": "Limit",
"type": "integer"
}
},
"required": [
"url"
],
"title": "listPostsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "listPostsOutput"
}🟢findContacts(url)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"title": "Url",
"type": "string"
}
},
"required": [
"url"
],
"title": "findContactsArguments"
}Output Schema
{
"type": "object",
"properties": {
"result": {
"title": "Result",
"type": "string"
}
},
"required": [
"result"
],
"title": "findContactsOutput"
}Community
Evidence