website-checks-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@website-checks-mcp check the llms.txt of example.com and draft a better one"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
UnlockLive website checks (MCP server)
Two free, read-only checks you can run from Claude, Cursor or any MCP client:
Tool | What it checks |
| Is the site's |
| Is a remote MCP server safe to connect? HTTPS and certificate, login required, OAuth discovery and PKCE, CORS, HSTS and version leaks. For open servers: the tool list, risky tools without safety hints, tool-poisoning phrases, and missing Origin checks. It never calls a tool. |
Both tools are marked read-only. They call the same public endpoints as the web tools (llms.txt checker, MCP security checker), which only read public files and never log in. Only check servers you own or are allowed to test.
Install
With uv:
{
"mcpServers": {
"unlocklive-checks": {
"command": "uvx",
"args": ["unlocklive-checks-mcp"]
}
}
}Add this to your Claude Desktop config (claude_desktop_config.json) or your client's MCP settings, then restart the client.
From source:
pip install .
unlocklive-checks-mcpRelated MCP server: gaip-broker
Try it
"Check the llms.txt of example.com and write me a better one."
"Is https://mcp.example.com/mcp safe to connect? What should we fix first?"
Limits
The checks look at a site from the outside, like any visitor. They don't replace a security review.
The public endpoints are rate limited (a few checks per 10 minutes per IP).
License
MIT
Made by UnlockLive IT. We build and secure MCP servers: MCP server development.
Available Tools
2 toolscheck_llms_txtARead-only
Check a website's /llms.txt against the llmstxt.org format and its robots.txt for blocked AI crawlers.
Returns a 0-100 score, the problems found with a plain fix for each, and a draft llms.txt built from the site's home page and sitemap when the file is missing. Example input: "example.com".
Inputs: website (required).
check_mcp_server_securityARead-only
Run a read-only security check of a remote MCP server (Streamable HTTP).
Checks HTTPS and the certificate, whether login is required, OAuth discovery and PKCE support, CORS, HSTS and version leaks. For open servers it also lists tools (it never calls them) and flags risky tools without safety hints, tool-poisoning phrases and missing Origin checks. Only check servers you own or are allowed to test. Example input: "https://mcp.example.com/mcp".
Inputs: server_url (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Check a page, AI-crawler access, llms.txt and backlinks of a site. Free, read-only.
Read-only checks for DIDs, credentials, MCP servers, A2A cards and agent delegation.
Live-checks whether a WordPress site is ready to be safely operated by AI agents.
Check whether a website is ready for AI agents (UCP, WebMCP, Access) and monitor your own sites.
Related MCP 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
- 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
- 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
- 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