Website Tech Stack Detector

io.github.wyeming95-rgbPublished by GitHub account wyeming95-rgbv1.0.0Updated Oct 24, 2026

Detect ecommerce platform, CMS, analytics, ad pixels, CDN and payments on any list of URLs

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Detects the ecommerce platform, CMS, analytics, ad pixels, CDN and payment tools used by any list of URLs.

What you can do
This remote MCP server inspects websites and reports the technologies behind them. According to its description, it identifies ecommerce platforms, content management systems, analytics tools, advertising pixels, CDNs and payment providers for any list of URLs. It is hosted by Apify and reached over streamable HTTP rather than installed locally.
When to use it
Useful when you want an assistant to profile a set of websites, for example to compare competitors' storefront platforms, check which analytics or ad pixels a site runs, or audit a list of domains for CMS and CDN choices.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP, with OAuth authentication. An Apify API token is required, sent in the Authorization header as a Bearer token; the token is obtained from the Apify console. No local runtime or packages are needed.
Before you install
The server requires an Apify API token in the Authorization header, so treat it as a secret and avoid exposing it in shared logs or configuration. Requests send the URLs you supply to a third-party hosted service, and Apify usage may be subject to account limits or billing.

Installation

In SourceWeft

  1. Open Website Tech Stack Detector in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.wyeming95-rgb%2Ftech-stack-detector/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "website-tech-stack-detector": {
      "type": "http",
      "url": "https://mcp.apify.com/?actors=smartmoney-data/tech-stack-detector"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 16, 2026

Score

60% 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
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tech integrations