Serveur MCP Website Tech Stack Detector
Commit 7 nov. 2026Identifies the technologies used by a website, including CMS, frameworks, analytics, CDN, hosting, and email providers.
Aussi connu sous prometheus-maker/apify-tools-examples, tech-stack
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 1.0.0
- Dernier commit
- 7 nov. 2026
- Licence
- MIT
Qu'est-ce que Website Tech Stack Detector MCP ?
Website Tech Stack Detector est un serveur MCP. Identifies the technologies used by a website, including CMS, frameworks, analytics, CDN, hosting, and email providers.
Résumé généré à partir du README du projet
À propos du MCP server Website Tech Stack Detector
Identifying the underlying technologies of a website is what this server enables for developers and researchers. By providing a list of over 7,000 technologies, it reveals the specific CMS, frameworks, analytics, CDN, hosting, and email providers used by any given domain. This tool acts as a functional alternative to services like BuiltWith or Wappalyzer.
Users connect to this remote server via an Apify token provided in the MCP client configuration. The service operates on a pay-per-use model, costing $0.002 per website processed, which avoids the need for a monthly subscription. It is designed to work within MCP clients like Claude or Cursor by sending URLs to the Apify API and receiving JSON data in return. You can further refine results by using the checkDns option to verify email providers or the includeEvidence option for more detailed reporting.
Ce que vous pouvez faire avec
- 1Analyze competitor infrastructureIdentify the specific frameworks and hosting providers used by a competitor's website.
- 2Verify email service providersUse DNS checks to confirm which email provider a specific domain is utilizing.
- 3Perform bulk technology auditsProcess a list of multiple domains to extract their technical specifications in JSON format.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer Website Tech Stack Detector MCP
Formats vérifiés le 10 nov. 2026Installer Website Tech Stack Detector MCP dans Claude Code
$ claude mcp add --transport http tech-stack https://mcp.apify.com/?tools=prometheus-maker/website-tech-stack-detectorInstaller Website Tech Stack Detector MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"tech-stack": {
"url": "https://mcp.apify.com/?tools=prometheus-maker/website-tech-stack-detector"
}
}
}Installer Website Tech Stack Detector MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"tech-stack": {
"type": "http",
"url": "https://mcp.apify.com/?tools=prometheus-maker/website-tech-stack-detector"
}
}
}Installer Website Tech Stack Detector MCP dans Codex
~/.codex/config.toml
[mcp_servers.tech-stack] url = "https://mcp.apify.com/?tools=prometheus-maker/website-tech-stack-detector"
Installer Website Tech Stack Detector MCP dans Gemini CLI
~/.gemini/settings.json
{
"mcpServers": {
"tech-stack": {
"httpUrl": "https://mcp.apify.com/?tools=prometheus-maker/website-tech-stack-detector"
}
}
}Configuration
APIFY_TOKEN
| Nom | Description | Type |
|---|---|---|
| APIFY_TOKEN | — |
Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →Pas encore vérifié. Un serveur nécessite un score de 80, aucune faille sérieuse et suffisamment de données pour que nous puissions effectuer les vérifications. Fonctionnement des vérifications
- Dépôt source lié et accessibleprometheus-maker/apify-tools-examples is public and reachablegithub.com/prometheus-maker/apify-tools-examples ↗Réussi
- Le paquet cite ce dépôt comme sourceNon vérifié
- Provenance du build (attestation Sigstore)Non vérifié
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-11-07github.com/prometheus-maker/apify-tools-examples ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNon vérifié
- Aucun avis critique dans le paquet ni ses dépendancesNon vérifié
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- L'endpoint distant répond au handshake MCPHTTPS endpoint answered 401 (sign-in required)Réussi
README
Voir sur GitHubApify tools: PDF to Markdown, OCR, Website to Markdown crawler, SEO audit, Tech Stack
Working examples for my pay-per-use tools on the Apify Store. Each one is an API: send URLs, get JSON back. You only pay for what you process, and there's no subscription.
| Tool | What it does | Price |
|---|---|---|
| 📄 PDF & Document to Markdown | PDF, Word, PowerPoint, Excel, HTML, EPUB → clean Markdown for LLM / RAG. Tables, two-column papers, OCR for scans, chunking | $0.002 per document + $0.0002 per page |
| 🖼️ Image & Scanned PDF to Text OCR | Text from photos, screenshots and scans in 41 languages, with line positions and confidence | $0.004 per image or page |
| 🕸️ Website to Markdown Crawler | Crawl a site into clean Markdown for LLM / RAG: main content only, linked PDF/Word/Excel files converted too, optional chunks | $0.0015 per page |
| 🔎 SEO Audit & Broken Link Checker | Audit every page of a site (titles, meta, headings, canonical, schema) and check every link and image for 404s. 0-100 score per page | $0.004 per page |
| 🌐 Website Tech Stack Detector | What a website is built with: CMS, frameworks, analytics, CDN, hosting, email provider. 7,000+ technologies (BuiltWith / Wappalyzer alternative) | $0.002 per website |
| 📸 Website Screenshot API | Full-page, first-screen, mobile or element screenshots as PNG, JPEG or PDF, cookie banners hidden | $0.005 per full page, $0.003 per first screen |
| 🔁 HTTP Request Runner | Send many API calls (GET/POST/any method) with retries and rate limits; status, headers and parsed JSON back | $0.001 per request |
| 📦 Bulk File Downloader | Download files from URL lists or every file linked on a page; images, PDFs, media; optional ZIP | $0.0015 per file |
| 🎙️ Audio & Video Transcriber | Speech to text with Whisper models: files, podcast feeds; text, timestamps, SRT | from $0.003 per audio minute |
Full prices, including per-page rates and discounts for paid Apify plans, are on each Store page.
Quick start (curl)
Get an API token from Apify Console → Integrations, then:
curl -X POST "https://api.apify.com/v2/acts/prometheus-maker~website-tech-stack-detector/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" -H "Content-Type: application/json" \
-d '{"urls": ["python.org"]}'
The same endpoint works for the other tools: replace the tool name and the input.
Use them from Claude, Cursor or any MCP client
Every tool is also an MCP server, hosted by Apify (streamable HTTP). Add one to your client with your Apify token:
{
"mcpServers": {
"pdf-to-markdown": {
"url": "https://mcp.apify.com/?tools=prometheus-maker/pdf-document-to-markdown",
"headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
}
}
}
Swap the part after tools= for any tool in the table (prometheus-maker/website-to-markdown-crawler, ...), or list
several separated by commas. The same entries are in the official MCP Registry
under io.github.prometheus-maker/* (files in mcp/). You pay per use, as with the API.
Python
pip install apify-client
export APIFY_TOKEN=...
python python/pdf_to_markdown.py # PDF → Markdown + RAG chunks
python python/image_to_text_ocr.py # image → text
python python/tech_stack.py # domains → technologies
python python/website_to_markdown.py # website → Markdown pages + chunks
python python/seo_audit.py # website → SEO scores, issues, broken links
The scripts are in python/. They use apify-client 3.x.
Inputs at a glance
| Tool | Main input | Useful options |
|---|---|---|
| PDF to Markdown | startUrls: [{"url": ...}] |
chunkSize, outputFormat, pageRange, pdfPassword, ocrLanguages, includeTablesJson |
| Image OCR | imageUrls: [{"url": ...}] |
languages (e.g. ["eng","deu"]), engine, includeLines (line positions) |
| Tech stack | urls: ["example.com", ...] |
checkDns (email provider, verified tools), includeEvidence |
| Website to Markdown | startUrls: ["https://example.com/docs/"] |
maxPages, crawlScope, includeDocuments, chunkSize, keepLinks |
| SEO audit | startUrls: ["https://example.com"] |
maxPages, checkExternalLinks, excludeUrlPatterns, maxLinkChecks |
See each Store page for every field and a full output example.
About
These tools are built and maintained by Prometheus (notes). Issues and requests are welcome in this repo.
Questions sur Website Tech Stack Detector MCP
Comment ajouter Website Tech Stack Detector MCP à Claude Code ?
Exécutez claude mcp add --transport http tech-stack https://mcp.apify.com/?tools=prometheus-maker/website-tech-stack-detector dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter Website Tech Stack Detector MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
What kind of information can the tech stack detector provide?
It identifies CMS, frameworks, analytics, CDN, hosting, and email providers used by a website.
How many technologies can this tool detect?
The tool can detect over 7,000 different technologies.
Can I check for specific email providers?
Yes, you can use the checkDns option to verify email providers and other tools.
How much does it cost to use?
The tool follows a pay-per-use model costing $0.002 per website.