Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Stackscan MCP
Overview
Description from the maker (original English)
Look up the technology stack behind any domain, and the company running it.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: STACKSCAN_API_TOKEN, STACKSCAN_TENANT_ID
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
STACKSCAN_API_TOKEN,STACKSCAN_TENANT_ID,STACKSCAN_SESSION_LOOKUP_CAP
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"stackscan": {
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "your-value",
"STACKSCAN_TENANT_ID": "your-value",
"STACKSCAN_SESSION_LOOKUP_CAP": "your-value"
}
}
}
}Run this in your terminal
claude mcp add stackscan --env STACKSCAN_API_TOKEN=your-value --env STACKSCAN_TENANT_ID=your-value --env STACKSCAN_SESSION_LOOKUP_CAP=your-value -- npx -y @stackscan/mcp-serverFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"stackscan": {
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "your-value",
"STACKSCAN_TENANT_ID": "your-value",
"STACKSCAN_SESSION_LOOKUP_CAP": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"stackscan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "your-value",
"STACKSCAN_TENANT_ID": "your-value",
"STACKSCAN_SESSION_LOOKUP_CAP": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- API token from the StackScan dashboard, My Account -> API Tokens.
- Workspace UUID, shown on the same page as the token.
STACKSCAN_SESSION_LOOKUP_CAPenvMaximum credit-consuming lookups per session. Defaults to 25.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain stackscan.com (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32451 servers in this category
- Published to the registry more recently than 53% of the other 32451 servers in this category
- Basic checks equal to or better than 100% of the other 32451 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Stackscan MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: STACKSCAN_API_TOKEN, STACKSCAN_TENANT_ID
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.4.0) reached the registry 35 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Recta
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Recta
by RectaBuild
Cheaper cross-chain stablecoin routes for AI agents; 5 % of the verified saving, nothing if none.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
StackScan MCP server
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.
Install
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.
Claude Desktop (extension)
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.
Claude Desktop (manual config)
Settings → Developer → Edit Config, then add:
{"mcpServers": { "stackscan": { "command": "npx", "args": ["-y", "@stackscan/mcp-server"], "env": { "STACKSCAN_API_TOKEN": "your-token", "STACKSCAN_TENANT_ID": "your-workspace-uuid" } } } }
Restart Claude Desktop. The tools appear under the connectors icon.
Claude Code
claude mcp add stackscan \--env STACKSCAN_API_TOKEN=your-token \ --env STACKSCAN_TENANT_ID=your-workspace-uuid \ -- npx -y @stackscan/mcp-server
Cursor, Windsurf, and others
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.
Tools
| 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, estimated revenue band | 1 credit |
lookup_domain_technologies | Technologies on ONE domain, in full: category and global usage for each (limit, default 50, max 100), plus how many are paid (premium) products and the estimated monthly tech spend | 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.
Breadth vs depth
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.
Why the batch tools stop at 20
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.
Configuration
| 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 |
The session cap is a spend cap, and it is deliberate
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.
Development
npm installnpm run build
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:
export STACKSCAN_API_TOKEN=...export STACKSCAN_TENANT_ID=... node test-stdio.mjs check_credits lookup_company:stripe.com
Never write to stdout in this server. stdout is the JSON-RPC channel; anything else on it corrupts the protocol. Diagnostics go to stderr.
Notes for anyone reading the source
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.
Privacy Policy
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.
Links
License
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.