Website Technology Detector: Tech Stack Scanner logo

Website Technology Detector: Tech Stack Scanner

by Fred JonesGitHubWebsiteUpdated Jul 22, 2026

Website technology detector — scan any URL for CMS, framework, ecommerce & analytics tools. For agencies & sales teams. Public page only, nothing stored.

tech-stack
technology-lookup
wappalyzer
+7
|

How to pay

Subscribe

Monthly billing

$19/month

Predictable monthly cost with included usage. Best for steady, high-volume traffic.

  • Unlimited tools within plan limits
  • One API key, billed once a month
  • Cancel any time

Website Technology Detector: Tech Stack Scanner

Detect what technology any website runs on — CMS, web framework, JavaScript libraries, ecommerce platform, analytics/tag managers, web server, CDN, hosting, and marketing/pixel tags — from a single URL. A BuiltWith / Wappalyzer-style technology lookup, built as an MCP tool an agent can call directly.

What it does

Fetches a single public page — the URL you give it, plus whatever redirect it issues — and matches its HTTP response headers, cookies, HTML markup, meta tags and

Who it's for: agencies scoping a prospect's site before a pitch, sales and lead-gen teams qualifying leads by tech stack, competitive researchers tracking what tools competitors use, security teams doing passive recon on exposed software/versions, and developers who just want to know what a site is built with.

BuiltWith / Wappalyzer alternative

Both are great for checking one site at a time by hand. This server wraps the same kind of fingerprint-matching technique as a structured MCP tool — call it from an agent, a script, or a workflow, get typed JSON back instead of a page you have to read, and check up to 50 sites in one call instead of one tab at a time.

Tools

  • detect_stack — fetch one public page, detect its stack. Example: { "url": "wordpress.org" }
  • bulk_detect_stack — detect up to 50 URLs in one call, 5 at a time, with a pass/fail summary. Example: { "urls": ["wordpress.org", "shopify.com"] }

Sample call and output

Call: { "url": "wordpress.org" }

{
  "input": "wordpress.org",
  "finalUrl": "https://wordpress.org/",
  "httpStatus": 200,
  "status": "OK",
  "technologies": [
    { "name": "WordPress", "category": "CMS", "confidence": 100, "evidence": "meta: generator, html markup" },
    { "name": "PHP", "category": "Programming languages", "confidence": 100, "evidence": "implied by WordPress" },
    { "name": "Nginx", "category": "Web servers", "confidence": 100, "evidence": "header: server" }
  ],
  "categoriesSummary": { "CMS": 1, "Programming languages": 1, "Web servers": 1 }
}

FAQ

What CMS does a site use? Call detect_stack with the URL — WordPress, Shopify, Wix, Drupal, Ghost and thousands of other platforms show up under CMS or Ecommerce with a confidence score. How do I detect a website's framework? Same call — JavaScript and web frameworks are detected from script patterns and headers alongside everything else. What technologies does a website use overall? One call returns every match: CMS, frameworks, analytics, CDN, hosting, ecommerce, marketing pixels. Is this site on Shopify or WordPress? Check the technologies array by name, or categoriesSummary for a quick Ecommerce vs. CMS signal. What if a site blocks the check? You get status: "BLOCKED" (403, rate-limiting, or a known anti-bot wall) instead of a false "no technology detected" — that distinction matters, so don't read a block as a clean result.

Trust & limits

Fetches only the single public page at the URL you give it (and whatever redirect that page itself issues) — no login or paywall bypass, no anti-bot evasion, no crawling beyond that one page. Identifies itself honestly via its User-Agent. Nothing is stored: pages are fetched, matched, and forgotten. No headless browser, so technologies that only reveal themselves after client-side JavaScript runs won't be detected.

Using this from an AI agent (MCP)

// detect_stack
{ "url": "wordpress.org" }
// bulk_detect_stack
{ "urls": ["wordpress.org", "shopify.com"] }