Forency
Forency MCP Server
让你的 AI 助手调查任何网站的技术栈——CMS、电子商务平台、JavaScript 框架、分析、CRM、营销自动化、支付、聊天组件、CDN 和托管。
询问 Claude(或 Cursor,或任何 MCP 客户端):
"competitor.com 运行的是什么技术栈?"
"这 15 个潜在客户中,哪些使用 HubSpot,哪些使用 Salesforce?"
"比较这三家商店的分析和支付技术栈。"
两种连接方式
托管——无需安装。 如果你的客户端支持远程 MCP 服务器,请将其指向 https://forency.io/api/mcp,并使用你的 API 密钥作为 Bearer token。无需下载任何内容,而且你始终能获得当前的工具。也列在 Smithery 上。
本地——本包。 适用于在你机器上运行 MCP 服务器的客户端:
Related MCP server: tech-stack-detector-mcp
安装
添加到你的 MCP 配置中——claude_desktop_config.json、.mcp.json 或你客户端的等效配置:
{
"mcpServers": {
"forency": {
"command": "npx",
"args": ["-y", "forency-mcp"],
"env": { "FORENCY_API_KEY": "fcy_your_key" }
}
}
}或者使用 Claude Code:
claude mcp add forency -e FORENCY_API_KEY=fcy_your_key -- npx -y forency-mcp在 forency.io 获取免费 API 密钥——每月 100 次扫描,无需信用卡。
工具
工具 | 作用 |
| 单个网站的完整技术栈解析 |
| 一次调用最多 25 个网站,每个网站包含完整详情 |
| 跨网站的并排对比表,可选择按类别过滤,例如 |
每个被扫描的 URL 都计为一次扫描,计入你的套餐。
这个包做什么,不做什么
这个仓库就是完整的客户端。它是一个轻量的 stdio MCP 服务器,将你的请求转发到 Forency REST API 并格式化回复。在把 API 密钥交给任何工具之前,值得了解以下几点:
它只与
https://forency.io通信,不与其他任何地址通信它只发送你的 API 密钥和你询问的 URL,仅此而已
没有遥测、没有分析、没有第三方调用
检测在服务端进行,因此不在此仓库中
你可以在大约五分钟内读完 src/index.ts 中的全部内容。如果你想观察它发送了什么,可以用 FORENCY_API_URL 将它指向其他地方。
环境
变量 | 必需 | 描述 |
| 是 | 来自 forency.io 的密钥 |
| 否 | API 基础 URL(默认为 |
关于检测的说明
Forency 读取网站服务器返回的 HTML 和响应头。它不运行浏览器,因此完全由客户端 JavaScript 注入的技术可能不会显示出来——结果稀疏意味着可检测到的内容很少,而不是网站没有运行任何技术。
定价
套餐 | 价格 | 每月扫描次数 |
免费版 | $0 | 100 |
入门版 | $29/月 | 1,000 |
专业版 | $49/月 | 10,000 |
企业版 | 自定义 | 无限 |
BuiltWith 的 API 起价为 $295/月,Wappalyzer 的起价为 $250/月。两者都不附带 MCP 服务器。
致谢
Forency 的检测基于 webappanalyzer 项目维护的技术指纹,该项目是 Wappalyzer 开源指纹数据库的社区维护延续,采用 GPL-3.0 许可证。正是这项工作使得以这样的价格实现准确检测成为可能,它值得这份赞誉。
这个 MCP 客户端本身不包含任何指纹数据或检测代码,并以 MIT 许可证发布(参见 LICENSE)。
许可证
MIT
Available Tools
3 toolsbatch_lookupLook up several websites at onceAInspect
Detect the technology stacks of up to 25 websites in one call, returning the full detail for each. Use it when working through a list of prospects, competitors, or portfolio sites. If you want a side-by-side view of who uses what, use compare_stacks instead. Counts one scan per URL against the caller's plan.
Inputs: urls (required).
compare_stacksCompare the technology stacks of several websitesAInspect
Scan 2-25 websites and return a side-by-side table of which technologies each one uses. Answers questions like 'which of these prospects use HubSpot vs Salesforce?' or 'how does our stack compare to our competitors?'. For the full per-site detail rather than a table, use batch_lookup. Counts one scan per URL against the caller's plan.
Inputs: urls (required), categories.
lookup_tech_stackLook up a website's technology stackAInspect
Detect the technologies a website runs: CMS, ecommerce platform, JavaScript frameworks, analytics, CRM, marketing automation, payment processors, chat widgets, CDN, and hosting. Use it to research a competitor, qualify a sales prospect, or check what a site is built with. Reads the HTML and headers the server sends, so anything injected only by client-side JavaScript may not appear — a sparse result means little was detectable, not that the site runs nothing. Counts as one scan against the caller's plan.
Inputs: url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool serves a distinct workflow: single-site lookup, bulk detail lookup, and side-by-side comparison. The descriptions explicitly cross-reference each other, making it clear when to choose one over the other.
Two names follow a verb_noun pattern (lookup_tech_stack, compare_stacks), while batch_lookup is a modifier_noun form. The inconsistency is minor and all names are still clear and predictable.
Three tools is well-scoped for a tech-stack detection server. Each tool covers a distinct usage size: single, batch, and comparative, with no redundant or unnecessary additions.
The tool surface covers the full intended workflow: looking up one site, looking up many sites, and comparing stacks across sites. There are no obvious dead ends or missing operations within the stated domain.
Maintenance
Related MCP Connectors
Detect a website's tech stack (CMS, analytics, ecommerce, hosting) plus company profile.
Detect a website's tech stack (frameworks, hosting, CDN, analytics). By Crypto Money Maker
Detect a website's CMS, analytics, chat, payments and ad pixels, with evidence and tracking IDs.
Detect a website's CMS, framework, analytics, CDN and hosting live, with evidence for each
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables querying the BuiltWith API to discover and analyze website technology stacks, including frameworks, analytics tools, CMS platforms, and other technologies used by any domain.2MIT
- FlicenseNot gradedqualityDmaintenanceDetects what technologies (CMS, frameworks, analytics, etc.) a website uses by fingerprinting its HTTP response and markup, returning confidence-scored results for single or bulk URL queries.-
- AlicenseNot gradedqualityCmaintenanceDetects 50+ technologies on any website (CMS, JS frameworks, analytics, hosting, etc.) with confidence scores and evidence, using x402 micropayments.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to investigate any website's technology stack, identifying CMS, ecommerce platforms, JavaScript frameworks, analytics, CRM, marketing automation, payments, chat, CDN, and hosting.-