StackScope

dev.stackscopePublished by stackscope.devOfficial publisherv1.0.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

StackScope is a remote MCP server that lets an assistant query a corpus of newly launched websites by technology stack, category, country and contact details.

What you can do
Search newly launched sites by technology, category, country, distance, date range and contact availability, and look up everything known about one domain. Get counts and shares of which technologies sites use, grouped by kind such as payments, analytics or hosting. Browse the tracked technology catalogue and weekly adoption trends for a single technology. Export up to 5,000 matching sites in bulk, optionally as CSV. Create, list and delete standing watches that deliver new matching sites by email, Slack or webhook. Check the plan, permissions and remaining monthly site allowance.
When to use it
Useful for prospecting and market research: finding new sites built with a given platform, measuring how many sites use a particular technology, tracking adoption trends, or building contactable lead lists from recent launches.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. No authentication, environment variables or headers are declared in the manifest, though the tools refer to a customer account, plan, permissions and a monthly site allowance.
Before you install
Some tools consume a monthly site allowance: lookup_site counts one site, and find_sites, technology_sites and export_sites return distinct sites against that limit, so check account_status before large queries. create_watch and delete_watch change account state, and watches can send data to email, Slack or webhook destinations. Exports can return up to 5,000 sites, including published contact details.

Installation

In SourceWeft

  1. Open StackScope in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.stackscope%2Fstackscope/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stackscope": {
      "type": "http",
      "url": "https://mcp.stackscope.dev/"
    }
  }
}

Tools

11

stack_breakdown

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 sites use'. Use this BEFORE find_sites or export_sites for those questions; exporting rows and counting them costs hundreds of lookups for the same answer. Same filters as find_sites. Counts one Explore slice and no site allowance.

ParametersnearsinceuntilradiuscountrycategorykeywordstechnologyobservedSincetechnologyCategoryminCountryConfidence

technology_sites

Sites using a technology

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 allowance for each site not already returned to you this period.

ParametersnearlimitsinceuntiloffsetradiusconfirmtechnologyrequiredincludeQuality

export_sites

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 needs no export. Counts one site from the monthly allowance for each site not already returned to you this period, so this is the call most likely to ask you to confirm first.

ParameterscsvnearlimitsinceuntilradiusconfirmcountrycategorykeywordstechnologyobservedSince+3 more

list_watches

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.

Takes no parameters.

technology_trend

Technology adoption over time

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.

Parameterstechnologyrequired

find_sites

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 30 miles of Bristol. Each site carries its town, and its distance when near is given. 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 allowance for each site not already returned to you this period; you may be asked to confirm before a large result is returned.

ParametersnearlimitsinceuntilcursorradiusconfirmcountrycategorykeywordstechnologyobservedSince+4 more

list_technologies

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.

Parameterstofromlimit

lookup_site

Look up one 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.

ParametersdomainrequiredincludeContactincludeQualityincludeInfrastructure

delete_watch

Delete a watch

Delete one of the customer's watches by id, from list_watches. Deliveries stop immediately. Free.

Parametersidrequired

create_watch

Create a 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, but delivered sites count against the monthly site allowance, and plans limit how many watches, technologies and keywords you may have. A webhook watch returns its signing secret exactly once when it is created.

ParametersnearradiuscadencechannelcountrycategorykeywordscountriescategorieswebhookUrltechnologieshasContactPage+3 more

account_status

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.

Takes no parameters.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.