RobotsGate
REMOTE · ROBOTSGATE.MIKE-TUSA.WORKERS.DEV
Generate, validate and check robots.txt rules for AI crawlers. Free; optional Pro key.
Available components
Last scanned (2 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 901 tokens (~225/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://robotsgate.mike-tusa.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mike-tusa.workers.dev | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | f05aa95d8943eeed0e4e86dd1f6f1e02 |
| SANs: mike-tusa.workers.dev, *.mike-tusa.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of robotsgate.mike-tusa.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://robotsgate.mike-tusa.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://robotsgate.mike-tusa.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_site Check which AI crawlers a live site allows ~140
Fetch a site's /robots.txt (http/https on the default port only; private, loopback and internal addresses are refused; up to 512,000 bytes; results cached for 5 minutes) and report, for one path, which registry AI crawlers are allowed or blocked, plus validation errors and warnings. Read-only: one GET of /robots.txt with a RobotsGate user-agent. Same engine as GET /api/check.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | URL path to test, starting with "/" (default "/"). |
| url | string | yes | Site URL or bare hostname, e.g. example.com. Only the scheme and host are used. |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_crawlers | – | – | Per-crawler results, or null when robots.txt was unreachable |
| cache | object | – | – |
| fetched_at | string | – | – |
| final_url | string | yes | – |
| http_status | integer | yes | – |
| interpretation | string | yes | – |
| path | string | – | – |
| personal_agents | – | – | Object, or null when robots.txt was unreachable |
| redirects | integer | – | – |
| robots_found | boolean | yes | – |
| url | string | yes | – |
No examples provided.
generate_robots Generate a robots.txt for AI crawlers ~324
Build a robots.txt from per-category choices (allow, block or omit for training, dataset, search, user_fetch or other), optional per-token overrides, a default policy for other bots, paths, sitemaps and custom rules. Returns the file text, a per-crawler summary and notes. Read-only: it only returns text and changes nothing. Same engine as POST /api/generate.
| Name | Type | Req | Description |
|---|---|---|---|
| agents | object | – | Per-token overrides, e.g. {"GPTBot": "block"}. Tokens: letters, digits, "_", "." and "-", up to 64 characters (not "*"). At most 100. |
| allow_paths | array | – | Paths to allow explicitly. Each path starts with "/" or "*" and has no whitespace or "#". At most 100. |
| categories | object | – | Action per crawler category. Omitted categories get no group of their own. |
| custom_rules | string | – | Extra robots.txt lines appended after validation (max 20000 bytes). |
| date | string | – | Date for the header comment (YYYY-MM-DD). Default: today (UTC). |
| default | string | – | Policy for "User-agent: *" (default allow). |
| disallow_paths | array | – | Paths to disallow for "*" and for allowed AI groups. Each path starts with "/" or "*" and has no whitespace or "#". At most 100. |
| sitemap | string | – | A single sitemap URL (alternative to sitemaps). |
| sitemaps | array | – | Absolute http(s) sitemap URLs. At most 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| notes | array | yes | – |
| personal_agents_note | string | – | – |
| robots_txt | string | yes | – |
| summary | array | yes | – |
No examples provided.
list_crawlers List the AI crawler registry ~97
Return RobotsGate's AI crawler registry: each crawler's robots.txt token, operator, category (training, dataset, search, user_fetch or other), whether the operator says it respects robots.txt, and a link to the operator's documentation, plus unverified entries and notes. Read-only, no network access. Same data as GET /api/crawlers.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: only crawlers in this category. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | object | yes | – |
| crawlers | array | yes | – |
| generated | string | – | – |
| schema_version | integer | – | – |
| unverified | array | – | – |
No examples provided.
validate_robots Validate robots.txt text ~128
Validate robots.txt text against RFC 9309 and report errors, warnings and, for one URL path, which registry AI crawlers are allowed or blocked and by which rule. Read-only, no network access. Same engine as POST /api/validate. Up to 50,000 characters over MCP (the whole JSON-RPC request must also fit in 64 KB); for larger files use POST /api/validate or check_site.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | URL path to test, starting with "/" (default "/"). |
| robots_txt | string | yes | The robots.txt file content. |
| Name | Type | Req | Description |
|---|---|---|---|
| ai_crawlers | array | yes | – |
| diagnostics | object | – | – |
| errors | array | yes | – |
| info | array | – | – |
| path | string | – | – |
| personal_agents | object | – | – |
| stats | object | – | – |
| valid | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the RobotsGate MCP server?
RobotsGate is a hosted endpoint at https://robotsgate.mike-tusa.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · robotsgate.mike-tusa.workers.dev
claude mcp add --transport http dev-workers-mike-tusa-robotsgate-robotsgate 'https://robotsgate.mike-tusa.workers.dev/mcp'
What is the RobotsGate MCP server?
RobotsGate is an MCP server listed in the public MCP registry as dev.workers.mike-tusa.robotsgate/robotsgate. Generate, validate and check robots.txt rules for AI crawlers. Free; optional Pro key. This page covers its hosted endpoint (https://robotsgate.mike-tusa.workers.dev/mcp).
Is the RobotsGate MCP server safe to use?
RobotsGate scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RobotsGate MCP server expose?
RobotsGate exposes 4 tools: list_crawlers, generate_robots, validate_robots, check_site. Their descriptions and schemas cost roughly 689 tokens of context every time the server is loaded.
Does the RobotsGate MCP server require authentication?
No. We connected to RobotsGate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RobotsGate MCP server still maintained?
RobotsGate is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.