Skip to main content
Glama
813,727 tools. Updated 2026-11-20 22:56

"Wappalyzer" matching MCP tools:

  • <summary>Find companies whose technographic profile matches a target tech stack. Use ONLY when the user explicitly wants to discover companies BY THEIR INSTALLED TECHNOLOGY — e.g. "find DTC brands using Shopify and Klaviyo", "who runs Snowflake AND Looker", "US e-commerce companies using HubSpot". For hiring-signal discovery (companies posting jobs that mention a tech), use `theirstack_search` instead — that surfaces investment intent, whereas this surfaces installed base. That installed base is what TheirStack DETECTS from job-posting text, not from crawling storefronts, so it only sees companies that hire and name the tool in their JDs — treat a company's absence as "not detected here," not "not using it" (a storefront-sniffing method like BuiltWith/Wappalyzer would surface more). For ecommerce-platform tools, results may include the platform's SERVICE PROVIDERS (agencies, ISVs) alongside actual merchants — job mentions don't distinguish "we run on Shopify" from "we sell to Shopify merchants," so name the kind of company you want in `criteria` and the check filters them out. Recruiting agencies are always excluded (company_type = direct_employer), matching theirstack_search. Costs 1.5 Sliq credits per company returned; a failed search is free. In chat, STATE THE COUNT AND THE COST in the same reply as the results — every time, without stopping to ask first. Use the user's number when they gave one, otherwise the default: "pulled 25 companies — 37.5 credits; say if you want more, max 100." Price the companies actually returned, which `count` gives: fewer than `limit` costs less. Because this endpoint pages, prefer one page at the user's number over silently walking `offset` past it — every extra page is more credits. Each company returned is then checked against `criteria` on its own, reading its name, firmographics and technologies, and only the matches come back in `companies`; the rest come back in `rejected` as {name, reason}. It adds a few seconds per ten companies. When this runs in an agent, every company with a domain is saved to the Output tab as a company row (deduped by domain) with its verdict, carrying its firmographics and matched technologies; the rejected ones are hidden from the list's default view. The tool resolves each technology name to a TheirStack catalog slug (calling /v0/catalog/technologies per name; popularity tiebreak; exact name match wins), then queries /v1/companies/search with `company_technology_slug_and` so EVERY supplied technology must be present on the returned company.</summary> <returns> <description>{ "companies": [ { "id": str, "name": str, "domain": str | None, "industry": str | None, "employee_count": int | None, "country_code": str | None, "linkedin_url": str | None, "technologies_found": [ {"slug": str, "name": str, "confidence": str, "jobs": int, "last_date_found": str}, ... ], "verdict": str | None, # 'qualified', 'unclear', or None when the check couldn't run "verdict_reason": str, }, ... ], "rejected": [{"name": str, "reason": str}, ...], # companies the check turned down "count": int, # companies in this page, rejected ones included; the number billed "total_matches": int, # universe size for this query (or None) "created_identifiers": [str], # domains of matching companies this call newly added to the list } On upstream failure (timeout / 5xx / connection error), returns `{"companies": [], "count": 0, "theirstack_available": False}` so the agent can read the flag and degrade gracefully.</description> </returns>
    ConnectorOAuth
  • Find known vulnerabilities in what a project or site runs, ranked by what to fix first. Send exact package versions, the raw content of a lockfile (package-lock.json, poetry.lock, go.sum and others), a CycloneDX or SPDX SBOM, a Wappalyzer export, or detected technologies such as nginx 1.18.0. Returns each finding with severity, exploitation, priority and fixed versions.
    ConnectorNo auth
  • Find known vulnerabilities in what a project or site runs, ranked by what to fix first. Send exact package versions, the raw content of a lockfile (package-lock.json, poetry.lock, go.sum and others), a CycloneDX or SPDX SBOM, a Wappalyzer export, or detected technologies such as nginx 1.18.0. Returns each finding with severity, exploitation, priority and fixed versions.
    ConnectorNo auth
  • Website technology detection API (BuiltWith/Wappalyzer alternative): given a URL, identify the CMS, frameworks, CDN and hosting, analytics, tag managers, payments and server software from headers, meta generator and script signatures, with evidence for each. Use for competitor analysis, lead qualification and sales prospecting: what is this site built with? Pay-per-call via x402 (USDC, Base).
    ConnectorNo auth
  • This tool calls the Actor "kadi_bence/tech-stack-detector" and retrieves its output results. Actor description: $1.50 per 1,000 websites. Detect the technology stack of websites (Wappalyzer/BuiltWith alternative). Input: URLs or domains; optional category filter. Returns per site: CMS, ecommerce, analytics, frameworks, CDN, server and payment processors with versions and confidence, from 7,600+ fingerprints.
    Connector
    Destructive
    API key
  • Paid. Detect a website's tech stack: CMS, framework, analytics, CDN, server (like BuiltWith/Wappalyzer). $0.02 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/website/tech.
    ConnectorNo auth

Matching MCP Connectors

  • Detect CMS, ecommerce, analytics, payments and email hosting for every website in a list.

  • Free, read-only vulnerability intelligence merged from the CVE List, NVD, GitHub Advisory Database, OSV, ENISA EUVD, CISA KEV, FIRST EPSS and Exploit-DB. Seven tools search advisories, look up CVE/GHSA/EUVD/OSV IDs, check package and product versions, rank patch priorities, and check lockfiles, SBOMs or Wappalyzer exports. Results include source links, CVSS, EPSS, exploitation evidence and published fixes where available. No account or API key. Documentation: https://vulnerable.now/agents

  • Security audit, WHOIS, RDAP, DNS lookup (MX, SPF, DMARC), SSL/security headers (HSTS, CSP, X-Frame-Options), tech stack (Wappalyzer-style), and B2B company enrichment / email finder for 1 to 5 URLs (url or urls). Supports deep=true sub-crawling of /contact, /about, /pricing, and /team plus Google Workspace / Microsoft 365 detection.
    ConnectorNo auth