Loading…
MCPGrade grades Model Context Protocol servers with an automated, read-only scanner. This is exactly what it does, what it refuses to do, how to identify it, and how to opt out.
The scanner enumerates a server (initialize, then tools/list, resources/list, prompts/list) and statically analyses the metadata it advertises. It never issues tools/call, so it never triggers a side effect, writes data, or executes an action on your server.
Only publicly reachable HTTP(S) endpoints are scanned. Targets that resolve to loopback, private, link-local, or cloud-metadata addresses are refused — the scanner will not be used as an SSRF relay into a private network.
The scanner carries no credentials and never supplies a bearer token, API key, or cookie. It cannot access anything behind authorization.
When a server demands authorization, the scanner stops. It does not retry, guess, or attempt to bypass the gate. Such a server is graded on its authorization surface only (verdict N) — the tool surface is left uninspected.
The scanner respects robots directives for the hosts it touches. A host that disallows our agent is skipped.
Rate limits are respected. A 429 (or a Retry-After header on any response) backs the scanner off for at least the interval the server asks for. Scans are low-volume and infrequent by design.
Every request the scanner makes carries a stable, published User-Agent. Allow or deny it on this exact string:
MCPGrade/1.0 (+https://andraxpentester.in/scanning)The scanner also publishes a stable machine-readable identity — a Client ID Metadata Document (CIMD) — so an authorization server can recognise us without open dynamic client registration:
If you operate an MCP server and want it removed from the directory — or want it excluded from future scans — email abuse@andraxpentester.in from an address you can demonstrate control of the server or its domain from. We action verified delist requests within 24 hours.
Delisting suppresses the public row and stops the crawler revisiting it; the scan history is retained but no longer served. You can also block the scanner outright at your edge using the User-Agent above, or disallow it in robots.txt.
Send us the endpoint URL (or canonical server name) you want removed and the domain you control, from an address at that domain. Use the button below to open a pre-filled request addressed to abuse@andraxpentester.in.
Email a delist requestRead the scoring methodology to see exactly how a grade is computed, or browse the graded server directory.