MCP Server

Just ask your assistant

Connect StackScan to Claude, Cursor, or any MCP client and put technographic data where you are already working. No SDK and no glue code. Paste a config block and ask a question.

Install it See the underlying API

What is MCP, in one minute

The Model Context Protocol is an open standard that lets AI assistants use outside tools. Clients that speak it, including Claude Desktop, Claude Code, Cursor and Windsurf, can call StackScan the way you would, without you ever leaving the conversation.

One connector, many clients

The same small server works in every MCP client. Configure it once per app; there is nothing StackScan-specific to learn beyond your two credentials.

The assistant does the driving

You ask in plain English. The assistant decides which lookup fits, calls it, and reads the answer back, including follow-ups like "now check the other five domains".

Local by design

The server is a tiny Node process started by your own client with npx. Your token lives in your config file, on your machine, and is sent only to api.stackscan.com.

Things you can just say

Your assistant picks the right lookup and reads the answer back. You never touch an endpoint.

"What is example.com built on?"

"Who's behind vercel.com? What industry, where are they, what's their LinkedIn?"

"How many sites run Klaviyo, and in which countries?"

"Here are 15 domains from my CRM. Which ones are on Shopify, and who are they?"

"How many StackScan credits do I have left?"

And because the answers land inside the conversation, you can keep going: "drop the agencies and give me the rest as a CSV", "draft an outreach line for each based on their stack". That part is your assistant's job, and it is where this beats copy-pasting from a dashboard.

Five tools

check_creditsfree Balance, monthly allocation, and how much of this session's spend cap is used. Never charged, and the recommended first call to confirm the connection works.

lookup_company1 credit The company behind a domain: name, industry, city, country, address, LinkedIn profile. No match, no charge.

lookup_domain_technologies1 credit Technologies detected on a domain, grouped by category: CMS, analytics, payments, hosting, and so on.

lookup_technology1 credit How many sites run a technology, and the countries where it is most used.

lookup_companies1 credit / match Up to 20 domains in one call, returned as a compact table. Charged only for domains that resolve. Misses in the batch cost nothing.

All five are read-only lookups against StackScan's index. None of them can modify your CRM, your account, or anything else.

Set it up in about five minutes

You need Node.js 18 or newer and your two credentials. The setup guide has the config block for Claude Desktop, Claude Code, Cursor and Windsurf, every setting, and what to check when a client does not list it.

Read the MCP docs Get a token The REST API

Credits, and a cap that protects them

Lookups draw on the same Bulk Lookup Credits as the dashboard and the API. There is nothing extra to buy, and the server tells the assistant its running total after every charged call, so you always know where you stand.

One credit per answer

A lookup that finds nothing is not charged, batches are charged per match rather than per request, and checking your balance is always free.

A spend cap, not just a rate limit

An assistant can loop far faster than a person clicks. The server stops after 25 charged lookups per session and says so, rather than quietly working through your balance. Raise it when you mean to.

It runs on your machine

There is no StackScan gateway in the middle. The server runs locally and calls api.stackscan.com directly, so your token goes from your machine to us and nowhere else. We never see your conversation, only the domains you looked up. It is read-only: it cannot change anything, here or in your tools.