Skip to main content
Glama

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:

Related MCP server: tech-stack-detector-mcp

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.io and 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

Available Tools

3 tools
batch_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

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying the BuiltWith API to discover and analyze website technology stacks, including frameworks, analytics tools, CMS platforms, and other technologies used by any domain.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Detects 50+ technologies on any website (CMS, JS frameworks, analytics, hosting, etc.) with confidence scores and evidence, using x402 micropayments.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to investigate any website's technology stack, identifying CMS, ecommerce platforms, JavaScript frameworks, analytics, CRM, marketing automation, payments, chat, CDN, and hosting.
      -