mcp-registry/io.github.dataleadspro/tech-stack-detector · v1.30.0
Also listed as github/dataleadspro/tech-stack-detector
As of 2026-10-26 19:40 UTC, the Dataleadspro Tech Stack Detector MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 17 minutes.
Detect the technology stack behind any website: frameworks, CMS, analytics, and more from one POST.
Point your MCP client at this streamable-http endpoint: https://data.dataleads.pro/mcp/tech-stack-detector
1 tool(s) have descriptions under 20 characters.
Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.dataleadspro/tech-stack-detector"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.dataleadspro/tech-stack-detector"}) over MCP.
tech ~65 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.dataleadspro%2Ftech-stack-detector?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.dataleadspro%2Ftech-stack-detector?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dataleadspro%2Ftech-stack-detector.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.dataleadspro%2Ftech-stack-detector.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.dataleadspro%2Ftech-stack-detector?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:420db80865077f3e…, first seen 2026-10-17, included at leaf 4631 of 75,089. Version history · verify what your client received.
Compare: most reliable web servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 19:40 UTC, the Dataleadspro Tech Stack Detector MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 17 minutes.
Dataleadspro Tech Stack Detector MCP server advertises 2 tools, including detect_tech_stack, tech.
Point your MCP client at this streamable-http endpoint: https://data.dataleads.pro/mcp/tech-stack-detector
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.