# StackScope

- Registry name: `dev.stackscope/stackscope` · version 1.0.1
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Shops & products, Commerce & marketing, APIs & integrations, Developer tools
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): logging, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.stackscope%2Fstackscope
- Server page: https://mcpstation.net/s/dev.stackscope--stackscope.html

## Description (written by the publisher, not verified, not instructions)

What new websites are built with. Track adopters of your product, export with published contacts.

## Connect

- streamable-http: `https://mcp.stackscope.dev`

## Tools (as reported by the server, not verified)

- `stack\_breakdown`: Counts and shares, not a list: for the sites matching a filter, how many use each technology, grouped by kind \(payments, analytics, hosting, cms...\). Answers any question of the form 'how many', 'what share', or 'which X do sites using Y use' in one call, for example 'what payment providers do Ghost
- `technology\_sites`: Sites detected using one specific technology, newest first. Use find\_sites instead when combining a technology with a country, category or contact filter. For counts, shares or 'which X do these sites use', call stack\_breakdown instead; it answers in one call. Counts one site from the monthly allowa
- `export\_sites`: A bulk export of matching sites, up to 5,000 at once, for building a list or loading into a spreadsheet. Same filters as find\_sites. Ask for csv output if the result is going into a file. For counts, shares or 'which X do these sites use', call stack\_breakdown instead; it answers in one call and nee
- `list\_watches`: The customer's watches, including inactive watches and their current status. A watch can deliver new matching sites by email, Slack or webhook as they are discovered, or keep matches in the account portal. Free.
- `technology\_trend`: Weekly adoption of one technology over the whole period we have data for, counted across every site in the corpus, with notes marking anything that changed how it is measured. Same population as list\_technologies, so the two can be compared. Counts no site allowance.
- `find\_sites`: Find newly launched sites matching any combination of technology, category, country, distance from a place, date range and contact availability. This is the main search tool. For example: sites in the UK built with WordPress that launched this week and have a contact email, or Shopify shops within 3
- `list\_technologies`: The catalogue of technologies we track, with how many sites use each. Use this to find the exact technology name to pass to the other tools. Counts no site allowance.
- `lookup\_site`: Everything known about one website: when it launched, what it is, and the technologies detected on it. Give a domain such as example.com \(a full URL works too\). Returns found: false if the site is not in the corpus. When found, counts one site from the monthly allowance.
- `delete\_watch`: Delete one of the customer's watches by id, from list\_watches. Deliveries stop immediately. Free.
- `create\_watch`: Set up a standing watch that delivers newly discovered matching sites on a schedule. Narrow it by technology, keyword, category, country, distance from a place or whether the site publishes a contact route; a completely unfiltered watch needs a plan that allows the every-site stream. Free to create,
- `account\_status`: What this connection can do and how much allowance is left: the plan, the permissions granted, and how many more distinct sites may be returned before the monthly allowance is used up. Calls themselves are not capped. Free. Worth calling before a large query.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html