Detect the tech stack behind any website: CMS, ecommerce, analytics, CRM, payments, hosting.
Let your AI assistant investigate any website's technology stack — CMS, ecommerce platform, JavaScript frameworks, analytics, CRM, marketing automation, payments, chat widgets, CDN, and hosting.
Ask Claude (or Cursor, or any MCP client):
"What tech stack does competitor.com run?"
"Which of these 15 prospects use HubSpot vs Salesforce?"
"Compare the analytics and payment stacks of these three stores."
Hosted — no install. If your client supports remote MCP servers, point it at
https://forency.io/api/mcp with your API key as a Bearer token. Nothing to
download, and you always get the current tools. Also listed on
Smithery.
Local — this package. For clients that run MCP servers on your machine:
Add to your MCP config — claude_desktop_config.json, .mcp.json, or your client's equivalent:
{
"mcpServers": {
"forency": {
"command": "npx",
"args": ["-y", "forency-mcp"],
"env": { "FORENCY_API_KEY": "fcy_your_key" }
}
}
}
Or with Claude Code:
claude mcp add forency -e FORENCY_API_KEY=fcy_your_key -- npx -y forency-mcp
Get a free API key at forency.io — 100 scans/month, no credit card.
| Tool | What it does |
|---|---|
lookup_tech_stack(url) | Full technology breakdown for one website |
batch_lookup(urls) | Up to 25 websites in one call, full detail for each |
compare_stacks(urls, categories?) | Side-by-side table across sites, optionally filtered to categories like ["CRM", "Analytics"] |
Each URL scanned counts as one scan against your plan.
This repository is the whole client. It is a thin stdio MCP server that forwards your request to the Forency REST API and formats the reply. Worth knowing before you hand any tool an API key:
https://forency.io and nothing elseYou can read the entire thing in src/index.ts in about five minutes. Point it somewhere else with FORENCY_API_URL if you want to watch what it sends.
| Variable | Required | Description |
|---|---|---|
FORENCY_API_KEY | Yes | Your key from forency.io |
FORENCY_API_URL | No | API base URL (defaults to https://forency.io) |
Forency reads the HTML and headers a site's server returns. It does not run a browser, so technologies injected purely by client-side JavaScript may not show up — a sparse result means little was detectable, not that a site runs nothing.
| Tier | Price | Scans/mo |
|---|---|---|
| Free | $0 | 100 |
| Starter | $29/mo | 1,000 |
| Pro | $49/mo | 10,000 |
| Enterprise | Custom | Unlimited |
BuiltWith's API starts at $295/mo and Wappalyzer's at $250/mo. Neither ships an MCP server.
Forency's detection is built on the technology fingerprints maintained by the webappanalyzer project, the community-maintained continuation of Wappalyzer's open-source fingerprint database, which is licensed GPL-3.0. That work is what makes accurate detection possible at this price, and it deserves the credit.
This MCP client contains no fingerprint data or detection code of its own and is released under the MIT license (see LICENSE).
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y forency-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cheevahagadog-forency": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceforency-mcpnpmio.github.cheevahagadog/forency works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.