The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Stackscan MCP listing page.
Ask your assistant what a website runs, and who is behind it.
A Model Context Protocol server for the StackScan Tech Lookup API. Point Claude, Cursor, or any other MCP client at it and you can ask things like:
What is example.com built on?
Who's behind vercel.com? Where are they, what industry, what's their LinkedIn?
How many sites run Klaviyo, and in which countries?
Read-only by design. Nothing here writes to any system of yours.
You need a StackScan account. Sign in, open API Tokens in the dashboard, create a token, and copy your workspace UUID from the same page.
Download stackscan.mcpb from the
releases page, then drag it onto
Settings > Extensions. It asks for your API token and workspace ID and installs the
rest itself.
Settings → Developer → Edit Config, then add:
Restart Claude Desktop. The tools appear under the connectors icon.
Same shape: command: npx, args: ["-y", "@stackscan/mcp-server"], and the two
environment variables. Check your client's own MCP docs for where its config file lives.
| Tool | What it does | Cost |
|---|---|---|
check_credits | Remaining balance and this month's allocation | free |
lookup_company | The company behind a domain: name, industry, city, country, LinkedIn | 1 credit |
lookup_domain_technologies | Technologies on ONE domain, in full: category and global usage for each (limit, default 50, max 100) | 1 credit |
lookup_technology | How many sites run a technology, and where they are | 1 credit |
lookup_companies | The companies behind up to 20 domains, as a compact table | 1 credit per domain with data |
lookup_domains_technologies | The technologies on up to 20 domains, as a compact table. Optional category filter | 1 credit per domain with data |
A lookup that finds nothing is not charged. Neither is check_credits.
There are two technology tools and they answer different questions.
lookup_domains_technologies is the breadth view: many domains, technology
names only, ideal for "which of these run Shopify?". lookup_domain_technologies
is the depth view: one domain, every technology with its category and how many
sites use it globally. The batch tool reports how many technologies it left out per
domain, so the model can offer to drill in.
The REST endpoints behind them take 100 domains per request, and these tools deliberately do not. A tool result goes straight into the model's context, and a hundred full company payloads is tens of thousands of tokens, which crowds out the conversation you are actually having, and the model then has to re-read all of it to answer anything. Twenty compact rows is a table a model can reason over.
It also refuses rather than truncates. If a batch would cost more than your session cap allows, it charges nothing and tells you how many you can afford. Quietly dropping domains would hand back an answer that looks complete and is not.
If you genuinely need hundreds of domains, that is what the REST endpoint is for.
| Variable | Required | Default | Notes |
|---|---|---|---|
STACKSCAN_API_TOKEN | yes | none | Dashboard → API Tokens |
STACKSCAN_TENANT_ID | yes | none | Your workspace UUID, same page |
STACKSCAN_API_BASE | no | https://api.stackscan.com | Rarely needed |
STACKSCAN_SESSION_LOOKUP_CAP | no | 25 | See below |
StackScan's own limit is a rate limit: requests per minute. That stops a burst. It does nothing to stop a patient agent quietly spending an entire credit balance over an afternoon, which is a failure mode humans clicking buttons do not have.
So this server keeps its own counter: 25 credit-consuming lookups per session by
default, after which it refuses and says why. Misses and check_credits never count
against it, because they are never charged. Every successful result carries a footer
showing lookups remaining and your last known balance, so the model can pace itself
instead of discovering the limit by hitting it.
If you mean to go higher, raise it deliberately ("STACKSCAN_SESSION_LOOKUP_CAP": "200") rather
than finding out afterwards.
test-stdio.mjs is a minimal JSON-RPC client that drives the server over a real stdio
pipe, so you can exercise it without an MCP host:
Never write to stdout in this server. stdout is the JSON-RPC channel; anything else on it corrupts the protocol. Diagnostics go to stderr.
Three things about the upstream API shaped this code and are easy to get wrong:
A miss is HTTP 200, not 404. The API answers "no data for that domain" with
200 {"success": false, "error": "No data available"}. A client that trusts the status
code reads the absent payload and crashes. Every response goes through one place that
separates a miss from a failure, so only a real failure is reported as an error.
Cached responses are still charged. The API's response cache shields its database, not your wallet: a repeat lookup inside the cache window costs the same credit. That is why the local balance decrements on every hit instead of trying to guess which calls were free.
Two base URLs are live. The API's home is api.stackscan.com/v1/.... The older
app.stackscan.com/api/v1/... paths are still served and are deliberately not
redirected, because a redirect would drop the body on POST. If your config still names
the old host, this server detects it and keeps using the old path shape, so upgrading
will not break you.
StackScan's privacy policy is at www.stackscan.com/privacy. What it means for this server specifically:
What is collected. The domains and technology names you look up, sent to
api.stackscan.com over HTTPS along with your API token and workspace ID. Nothing else
leaves your machine. This server reads no files, opens no ports and keeps no local
store; the only state it holds is a lookup counter and a credit balance, both in memory
and both gone when the process exits.
How it is used and stored. Lookups are logged against your workspace so credits can be metered and the account can be supported. Results come from StackScan's own crawl data, not from anything you send.
Third parties. Query terms are not sold or shared for advertising. They reach the infrastructure providers StackScan runs on, as set out under "Sharing With Service Providers" in the policy, and nowhere else.
Retention. Covered under "Data Retention" in the policy. Delete your account and the associated lookup history goes with it.
Contact. hello@stackscan.com, or www.stackscan.com/contact.
MIT. See LICENSE.
The licence covers this client only, roughly 500 lines that make HTTP requests. The StackScan data it reaches is a paid service and is not covered by it.