npm forency-mcpstreamable-httpupdated 11d ago
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.
What can you do with forency?
Forency MCP Server
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."
Two ways to connect
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:
Install
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.
Tools
| 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.
What this package does, and doesn't
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:
- it talks to
https://forency.ioand nothing else - it sends your API key and the URLs you asked about, nothing more
- no telemetry, no analytics, no third-party calls
- detection happens server-side, so it is not in this repo
You 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.
Environment
| Variable | Required | Description |
|---|---|---|
FORENCY_API_KEY |
Yes | Your key from forency.io |
FORENCY_API_URL |
No | API base URL (defaults to https://forency.io) |
A note on detection
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.
Pricing
| 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.
Acknowledgements
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).
License
MIT
Install
Add forency to your client. Pick the one you use.
{
"servers": {
"forency-mcp": {
"type": "http",
"url": "https://forency.io/api/mcp"
}
}
}Add to `.vscode/mcp.json` in your workspace.
claude mcp add forency-mcp -- npx -y forency-mcpcodex mcp add forency-mcp -- npx -y forency-mcpamp mcp add forency-mcp -- npx -y forency-mcp{
"mcpServers": {
"forency-mcp": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"forency-mcp": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"mcpServers": {
"forency-mcp": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
{
"mcpServers": {
"forency-mcp": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}Add to `cline_mcp_settings.json` via the MCP Servers panel.
{
"mcpServers": {
"forency-mcp": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}Add to `~/.gemini/settings.json`.
{
"mcpServers": {
"forency-mcp": {
"type": "local",
"command": "npx",
"args": [
"-y",
"forency-mcp"
],
"tools": [
"*"
]
}
}
}Add to `~/.copilot/mcp-config.json`, or run `/mcp add` inside the CLI.
{
"context_servers": {
"forency-mcp": {
"command": {
"path": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
}
}Add to your Zed `settings.json`.
npx -y forency-mcpRun `goose configure`, choose **Add Extension → Command-line Extension**, and paste this command.
Score
39 / 100
Incomplete
- Documentation22/25
- Maintenance19/25
- Trust6/20
- Capability0/15
- Install experience15/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 3 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 0 tool(s) documented
- Provides prompt templates
- Provides resources
- 18 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint — no local install
Version history
| Versions | Published |
|---|---|
| 1.1.0Latest | Aug 28, 2026 |