RAT LABS MCP server

• Registry nametech.ratlabs/rat-radarverified in the MCP registry

The registry name sits under ratlabs.tech. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-29
• Tools8
• Server calls itselfrat-radar
• Server version1.4.0
• Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 126 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer114 ms
• Space in an agent's context≈ 1,240 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsB · 79 of 100
• Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 2 of 8
• Not saying whether it only reads or can destroy: 8 of 8

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• check_site

  Can I scrape this site, and how? Returns a verdict (open, guarded, hostile, blocked), a hostility score, a recommended approach with steps and risks, bot protections, robots.txt and AI-crawler policy, machine-readable surfaces (sitemap…

• get_playbook

  What should I build with this site, and how? Give a domain and, optionally, a goal in plain words (for example "price alerts", "sales leads", "new jobs", "change log", "knowledge base"). Returns the best-matching workflow for that site…

• list_sites

  List the sites in the dataset, optionally by category or verdict. Use it to find easy targets or to see what is covered.

• xray_page

  How do I extract the data from THIS page? Fetches one public page and returns a ranked extraction plan: embedded JSON, JSON-LD, repeated records with CSS selectors and field names, tables, feeds, hidden API calls. Each source has a…

• xray_diagram

  Draw a page's anatomy as an Excalidraw diagram: its regions, the ranked ways to get its data, proof rows, the best route and what the page is made of. Returns a download link for the .excalidraw file (give it to the user; it opens at…

• search_sites

  Find sites in the dataset by a word: a name, host, category (jobs, shop, news, gov), country or verdict. Use it to discover what is covered before calling check_site.

• can_fetch

  Does robots.txt allow fetching this exact URL? Fetches the live robots.txt and applies the longest-match rule for a user agent (default: * plus GPTBot, ClaudeBot, Google-Extended, CCBot, PerplexityBot). Returns allowed or not, the rule…

• summary

  Headline numbers across the dataset: verdict mix, how many sites block AI crawlers (and which), protection vendors, by category and country.