website-checks-mcp
Related Servers
Alternatives to website-checks-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceAudits MCP server configurations for security risks including capability inventory, SSRF, prompt injection, and drift detection. Works in read-only mode and can also be used as an MCP server to let AI agents audit their own attack surface.182 PyPI4MIT
- AlicenseBqualityCmaintenanceEnables read-only security assessment of a public MCP endpoint by sending initialize and tools/list requests and returning a 0–100 score covering transport, auth, overly broad tools, injection phrasing, and rug-pull definition changes, plus a 12-probe prompt-injection suite against a bot you own that flags leaked system prompts, tool dumps, secrets, exfiltration channels, and canary obedience.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables free, read-only checks of AI agents and MCP servers for conformance, published changes, delivery evidence, and verifiable receipts without requiring an account or API key, using public or non-personal data only.MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to run a live, unauthenticated check of any WordPress or other website's AI-agent readiness by URL, inspecting llms.txt, AI-crawler directives in robots.txt, schema.org markup, and a WebMCP capability manifest against the site itself rather than self-reported data. Results cover the Discoverability, Bot Access, and Content categories, and the remote endpoint requires no API key or signup.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients and AI agents to run read-only infrastructure health checks for TLS/STARTTLS certificate expiry and mail DNS configuration, including bulk certificate scans and MX/SPF/DKIM/DMARC audits.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to run read-only exposure scans against MCP servers that front databases, surfacing unauthenticated access, role/tool leaks, write-capable tools, and locally stored credentials, then returning plain-language findings.3Apache 2.0
TDQS
Scored across 2 tools
The two tools target entirely different artifacts: a website's llms.txt/robots.txt versus a remote MCP server's security posture. There is no plausible way for an agent to confuse one for the other, and the inputs (domain vs. HTTPS URL) are clearly disjoint.
Both follow the same check_<subject> snake_case pattern, and the subject portion is descriptive of exactly what is inspected. No mixed conventions or vague verbs.
Two tools is thin for a server branded as 'website-checks', which implies a broader catalog of checks. Each tool is substantial on its own, but the surface feels minimal rather than deliberately scoped.
Each check is self-contained and returns actionable output (score, problems with fixes, and even a generated draft llms.txt), so there are no dead ends within a single call. Gaps exist at the domain level — e.g., no general site hygiene, DNS/TLS or MCP functional/health checks — but these are minor for the apparent narrow purpose.