StackScan Tech Lookup APIを使用して、ウェブサイトのテクノロジースタックを特定し、詳細な企業情報を取得します。
別名 stackscan/stackscan-mcp, stackscan-mcp, @stackscan/mcp-server
- スター
- 3
- ツール
- 6
- ダウンロード数(30日間)
- —
- 最新バージョン
- 0.4.0
- 最終コミット
- 2026年10月2日
- ライセンス
- MIT
StackScan MCPとは
StackScanはMCPサーバーです。 StackScan Tech Lookup APIを使用して、ウェブサイトのテクノロジースタックを特定し、詳細な企業情報を取得します。. 6個のツールを提供しており、check_credits, lookup_company, lookup_domain_technologiesなどがあります。
プロジェクトのREADMEから生成された概要
StackScan MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにStackScan MCPをインストール
$ claude mcp add --env 'STACKSCAN_API_TOKEN=<YOUR_STACKSCAN_API_TOKEN>' --env 'STACKSCAN_TENANT_ID=<STACKSCAN_TENANT_ID>' stackscan-mcp -- npx -y @stackscan/mcp-serverCursorにStackScan MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"stackscan-mcp": {
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "<YOUR_STACKSCAN_API_TOKEN>",
"STACKSCAN_TENANT_ID": "<STACKSCAN_TENANT_ID>"
}
}
}
}VS CodeにStackScan MCPをインストール
.vscode/mcp.json
{
"servers": {
"stackscan-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "<YOUR_STACKSCAN_API_TOKEN>",
"STACKSCAN_TENANT_ID": "<STACKSCAN_TENANT_ID>"
}
}
}
}VS Code CLIにStackScan MCPをインストール
$ code --add-mcp '{"name":"stackscan-mcp","type":"stdio","command":"npx","args":["-y","@stackscan/mcp-server"],"env":{"STACKSCAN_API_TOKEN":"<YOUR_STACKSCAN_API_TOKEN>","STACKSCAN_TENANT_ID":"<STACKSCAN_TENANT_ID>"}}'Claude DesktopにStackScan MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"stackscan-mcp": {
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "<YOUR_STACKSCAN_API_TOKEN>",
"STACKSCAN_TENANT_ID": "<STACKSCAN_TENANT_ID>"
}
}
}
}CodexにStackScan MCPをインストール
$ codex mcp add stackscan-mcp --env 'STACKSCAN_API_TOKEN=<YOUR_STACKSCAN_API_TOKEN>' --env 'STACKSCAN_TENANT_ID=<STACKSCAN_TENANT_ID>' -- npx -y @stackscan/mcp-serverCodex config.tomlにStackScan MCPをインストール
~/.codex/config.toml
[mcp_servers.stackscan-mcp] command = "npx" args = ["-y", "@stackscan/mcp-server"] [mcp_servers.stackscan-mcp.env] STACKSCAN_API_TOKEN = "<YOUR_STACKSCAN_API_TOKEN>" STACKSCAN_TENANT_ID = "<STACKSCAN_TENANT_ID>"
Gemini CLIにStackScan MCPをインストール
$ gemini mcp add -s user -e 'STACKSCAN_API_TOKEN=<YOUR_STACKSCAN_API_TOKEN>' -e 'STACKSCAN_TENANT_ID=<STACKSCAN_TENANT_ID>' stackscan-mcp npx -- -y @stackscan/mcp-serverGemini settings.jsonにStackScan MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"stackscan-mcp": {
"command": "npx",
"args": [
"-y",
"@stackscan/mcp-server"
],
"env": {
"STACKSCAN_API_TOKEN": "<YOUR_STACKSCAN_API_TOKEN>",
"STACKSCAN_TENANT_ID": "<STACKSCAN_TENANT_ID>"
}
}
}
}StackScan MCPツール 6
READMEから検出check_creditslookup_companylookup_domain_technologieslookup_technologylookup_companieslookup_domains_technologies
| check_credits | — | |
| lookup_company | — | |
| lookup_domain_technologies | — | |
| lookup_technology | — | |
| lookup_companies | — | |
| lookup_domains_technologies | — |
設定
STACKSCAN_API_TOKEN必須シークレットAPI token from the StackScan dashboard, My Account -> API Tokens.
STACKSCAN_TENANT_ID必須Workspace UUID, shown on the same page as the token.
STACKSCAN_SESSION_LOOKUP_CAPMaximum credit-consuming lookups per session. Defaults to 25.
| 名前 | 説明 | 種類 |
|---|---|---|
| STACKSCAN_API_TOKEN | API token from the StackScan dashboard, My Account -> API Tokens. | 必須シークレット |
| STACKSCAN_TENANT_ID | Workspace UUID, shown on the same page as the token. | 必須 |
| STACKSCAN_SESSION_LOOKUP_CAP | Maximum credit-consuming lookups per session. Defaults to 25. |
自動チェック
実行日 2026年11月13日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能stackscan/stackscan-mcp is public and reachablegithub.com/stackscan/stackscan-mcp ↗合格
- パッケージがこのリポジトリをソースとして指定@stackscan/mcp-server names stackscan/stackscan-mcp as sourcenpmjs.com/package/@stackscan/mcp-server ↗合格
- ビルドの来歴 (Sigstore 証明)No build attestation published for this release未チェック
- オープンソースライセンス (OSI)MITspdx.org/licenses/MIT.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-10-02github.com/stackscan/stackscan-mcp ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していないNo popular package one edit away from @stackscan/mcp-server合格
- パッケージおよびその依存関係に重大な勧告なし4 resolved dependencies checked; no critical advisoryosv.dev ↗合格
- モデルへの隠れた指示がない6 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされているNo tool named like delete, drop or exec合格
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見る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 install
npm 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.
StackScan MCPのよくある質問
StackScan MCPをClaude Codeに追加するには
ターミナルでclaude mcp add --env 'STACKSCAN_API_TOKEN=<YOUR_STACKSCAN_API_TOKEN>' --env 'STACKSCAN_TENANT_ID=<STACKSCAN_TENANT_ID>' stackscan-mcp -- npx -y @stackscan/mcp-serverを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
StackScan MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
StackScan MCPが提供するツールは
6個のツールを提供しており、check_credits, lookup_company, lookup_domain_technologies, lookup_technology, lookup_companiesなどがあります。
ドメインからどのような情報を得られますか?
会社名、業界、都市、国、LinkedInプロフィール、および推定収益帯を確認できます。
サーバーはどのように過剰なクレジット消費を防ぎますか?
サーバーにはセッション上限が設定されており、エージェントが残高をすべて使い切らないよう、1セッションあたりのクレジット消費を伴うルックアップはデフォルトで25回に制限されています。
テクノロジー調査ツールの違いは何ですか?
breadth view (lookup_domains_technologies) は多数のドメインのテクノロジー名を表示し、depth view (lookup_domain_technologies) は単一のドメインに関する詳細情報を提供します。