StackScan MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STACKSCAN_API_BASE | No | Base URL for the StackScan API. Rarely needed. Defaults to https://api.stackscan.com | https://api.stackscan.com |
| STACKSCAN_API_TOKEN | Yes | Your StackScan API token, from Dashboard → API Tokens | |
| STACKSCAN_TENANT_ID | Yes | Your StackScan workspace UUID, from the same page as API Tokens | |
| STACKSCAN_SESSION_LOOKUP_CAP | No | Maximum number of credit-consuming lookups per session. Defaults to 25. | 25 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_creditsA | Check the StackScan credit balance. Free - does not consume a credit. Call this before a batch of lookups so you know how many you can afford. |
| lookup_companyA | Given a domain, return the company behind it: name, industry, city, country, address and LinkedIn URL. Use this when asked who owns or operates a website, or to enrich a domain into firmographics. Costs 1 credit. |
| lookup_domain_technologiesA | Given a domain, list the technologies detected on it (analytics, hosting, ecommerce platform, frameworks and so on), each with its category and how many sites overall use it. Use this to answer 'what is this site built with?'. Costs 1 credit. |
| lookup_technologyA | Given a technology name, return how widely it is used and its top countries by adoption. Use this to size a market or compare platforms, e.g. 'how many sites run Shopify, and where?'. Costs 1 credit. |
| lookup_companiesA | Look up the companies behind up to 20 domains in ONE call, returned as a compact table. Prefer this over repeated lookup_company calls whenever you have several domains in hand - it is one request instead of many, and costs the same per resolved domain. Duplicates and www. variants collapse and are charged once. Costs 1 credit per domain that HAS data; misses and malformed domains are free. |
| lookup_domains_technologiesA | Look up the technologies on up to 20 domains in ONE call, returned as a compact table. Prefer this over repeated lookup_domain_technologies calls whenever you have several domains in hand - it is one request instead of many and costs the same per resolved domain. Answers questions like 'which of these run Shopify?'. Pass |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool serves a distinct purpose: credit check, single/multi-company lookup, single/multi-technology lookup, and a standalone technology market lookup. The batch variants are explicitly differentiated from their single counterparts, and descriptions clearly guide when to use each, eliminating ambiguity.
All tools follow a consistent verb_noun pattern: check_credits, lookup_company, lookup_domain_technologies, lookup_technology, lookup_companies, lookup_domains_technologies. The plural versions naturally extend the singular ones, and the pattern is uniform across the entire set.
Six tools is a well-scoped set for a domain intelligence API. Each tool covers a distinct operation (balance, single/batch company lookup, single/batch tech lookup, tech market lookup) without redundancy or bloat, fitting comfortably within the ideal 3-15 range.
The surface covers the core read-only lifecycle: single and batch lookups for both companies and technologies, a technology market tool, and a credit checker. Minor gaps exist (e.g., no way to list all technologies or search companies by name), but they are edge cases that agents can work around.