Forency
io.github.cheevahagadogPublished by GitHub account cheevahagadogv1.1.0Updated Oct 24, 2026
Detect the tech stack behind any website: CMS, ecommerce, analytics, CRM, payments, hosting.
Overview
Forency detects the technology stack behind websites — CMS, ecommerce, analytics, CRM, payments, hosting — for an AI assistant to look up and compare.
- What you can do
- Look up the full technology breakdown of a single website
- Batch-scan up to 25 sites in one call with full detail for each
- Compare stacks side by side across several sites, optionally filtered to categories such as CRM or Analytics
- When to use it
- Useful for competitive research, prospect qualification and vendor audits where you want an assistant to identify which platforms a site runs, or to compare several sites' analytics, payment or CRM choices.
- Requirements
- A Forency API key, supplied as the FORENCY_API_KEY environment variable for the local npm package or as a Bearer token in the Authorization header for the hosted endpoint. Network access to forency.io. A free tier of 100 scans per month is offered.
Installation
In SourceWeft
- Open Forency in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.cheevahagadog%2Fforency/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"forency": {
"type": "http",
"url": "https://forency.io/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
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:
Or with Claude Code:
Get a free API key at forency.io — 100 scans/month, no credit card.
Tools
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
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
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
Source: README.md at commit b2beffc
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts