Technology Stack Detection API

io.github.Br0ski777Published by GitHub account Br0ski777v1.2.0Updated Oct 24, 2026

Detect 50+ technologies on any website: CMS, frameworks, analytics, CDN. x402.

The publisher's own server: Tech.eu Funding Explorer

VerifiedSSEWeb executableWeb Search & Scraping Developer Tools

Server details

Identifier: io.github.Br0ski777/tech-enrichment
Transport: SSE
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account Br0ski777 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.Br0ski777%2Ftech-enrichment.svg)](https://sourceweft.com/mcp/io.github.Br0ski777%2Ftech-enrichment?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP endpoint that detects 50+ technologies (CMS, frameworks, analytics, CDN, hosting) on a given website, paid per call via x402.

What you can do: Detect the technology stack of a website from a URL, returning categorized results with confidence levels and evidence.
Identify CMS, JavaScript frameworks, CSS tooling, analytics, hosting, CDN and payment providers found on the page.
Return a summary count of detections grouped by category.
When to use it: Useful for qualifying sales leads by technology fit, competitive or architecture analysis, and quick security-oriented reconnaissance of a site's stack. It is a single-purpose lookup, not a full company, SEO or content-scraping tool.
Requirements: A remote MCP endpoint over SSE; no package install. No API key or signup, but each call is paid in USDC on Base L2 through the x402 protocol, so an x402-capable client and a funded wallet are needed. Network access to the endpoint is required.

Before you install

Every call costs money ($0.012 per detection) and is settled in USDC on Base, so an agent can spend funds automatically; use a limited wallet. The scanned URL is sent to a third-party service, and payment is handled by external facilitators (Coinbase CDP, PayAI). No credentials are requested.

Installation

In SourceWeft

Open Technology Stack Detection API in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Ftech-enrichment/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "technology-stack-detection-api": {
      "type": "sse",
      "url": "https://tech-enrichment.api.klymax402.com/mcp"
    }
  }
}

README

Technology Stack Detection API

[MCP Server] [x402] [License: MIT]

Detect 50+ technologies on any website. CMS, JS frameworks, analytics, hosting, CDN, payments. Confidence scores and evidence. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json

{  "mcpServers": {    "tech-enrichment": {      "url": "https://tech-enrichment.api.klymax402.com/mcp"    }  }}

{  "mcpServers": {    "tech-enrichment": {      "url": "https://tech-enrichment.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash

curl "https://tech-enrichment.api.klymax402.com/api/detect?url=https://example.com"# -> 402 Payment Required, with an x402 payment challenge in the response body

curl "https://tech-enrichment.api.klymax402.com/api/detect?url=https://example.com"# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

`website_detect_tech_stack`

Use this when you need to identify what technologies a website uses. Returns structured JSON with categorized detections, confidence levels, and evidence for each technology found.

Parameters

Example response:

json

{"technologies":[{"name":"React","category":"JS Framework","confidence":"high","evidence":"react-dom in bundle"},{"name":"Tailwind CSS","category":"CSS","confidence":"high","evidence":"tailwind classes in HTML"},{"name":"Vercel","category":"Hosting","confidence":"medium","evidence":"x-vercel-id header"}],"summary":{"totalDetected":8,"categories":{"JS Framework":2,"CSS":1,"Hosting":1,"Analytics":3,"Payments":1}}}

{"technologies":[{"name":"React","category":"JS Framework","confidence":"high","evidence":"react-dom in bundle"},{"name":"Tailwind CSS","category":"CSS","confidence":"high","evidence":"tailwind classes in HTML"},{"name":"Vercel","category":"Hosting","confidence":"medium","evidence":"x-vercel-id header"}],"summary":{"totalDetected":8,"categories":{"JS Framework":2,"CSS":1,"Hosting":1,"Analytics":3,"Payments":1}}}

When to use: sales outreach (to personalize pitch by tech stack), competitive analysis, or security audits. Essential for qualifying leads by technology fit and understanding competitor architecture.

Not for: full company data (use company_enrich_from_domain), SEO analysis (use seo_audit_page), website content (use web_scrape_to_markdown).

Example agent prompts

"Identify what technologies a website uses"

Payment

Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
Network: Base L2 (eip155:8453)
Asset: USDC
Facilitator: Coinbase CDP (primary), PayAI (fallback)
Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

Catalog: https://klymax402.com/llms.txt
Full API reference: https://klymax402.com/llms-full.txt
Live stats: https://klymax402.com/stats

License

MIT

Source: README.md at commit 41407df

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts