io.github.cheevahagadog/forency
NPM · FORENCY-MCP · 2 COMPONENTS · SCANNED SEP 22
Detect the tech stack behind any website: CMS, ecommerce, analytics, CRM, payments, hosting.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 23 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 375 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.cheevahagadog/forency MCP server?
io.github.cheevahagadog/forency runs locally as an npm package, launched with npx -y forency-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · forency-mcp
claude mcp add cheevahagadog-forency -- npx -y forency-mcp
{
"mcpServers": {
"cheevahagadog-forency": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
} {
"servers": {
"cheevahagadog-forency": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
} codex mcp add cheevahagadog-forency -- npx -y forency-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cheevahagadog-forency": {
"type": "local",
"command": [
"npx",
"-y",
"forency-mcp"
],
"enabled": true
}
}
} openclaw mcp add cheevahagadog-forency --command npx --arg -y --arg forency-mcp
mcp_servers:
cheevahagadog-forency:
command: "npx"
args: ["-y", "forency-mcp"] {
"McpServers": {
"cheevahagadog-forency": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"forency-mcp"
]
}
}
} assistant mcp add cheevahagadog-forency -t stdio -c npx -a -y forency-mcp
{
"mcpServers": {
"cheevahagadog-forency": {
"command": "npx",
"args": [
"-y",
"forency-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/forency-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batch_lookup Look up several websites at once ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | The websites to analyze, 1-25. Bare domains are fine. |
No output schema declared.
No examples provided.
compare_stacks Compare the technology stacks of several websites ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional: only compare these categories, e.g. ['CRM', 'Analytics', 'Ecommerce']. Omit to compare every detected category. |
| urls | array | yes | The websites to compare, 2-25. Bare domains are fine. |
No output schema declared.
No examples provided.
lookup_tech_stack Look up a website's technology stack ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website to analyze. A bare domain works — 'example.com' and 'https://example.com' are both fine. |
No output schema declared.
No examples provided.
What is the io.github.cheevahagadog/forency MCP server?
io.github.cheevahagadog/forency is an MCP server listed in the public MCP registry as io.github.cheevahagadog/forency. Detect the tech stack behind any website: CMS, ecommerce, analytics, CRM, payments, hosting. This page covers its npm package (forency-mcp).
Is the io.github.cheevahagadog/forency MCP server safe to use?
io.github.cheevahagadog/forency scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cheevahagadog/forency MCP server expose?
io.github.cheevahagadog/forency exposes 3 tools: lookup_tech_stack, batch_lookup, compare_stacks. Their descriptions and schemas cost roughly 375 tokens of context every time the server is loaded.
Is the io.github.cheevahagadog/forency MCP server still maintained?
io.github.cheevahagadog/forency is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cheevahagadog/forency MCP server under?
io.github.cheevahagadog/forency declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.