Skip to content

Red Center Studio free tools MCP server

io.github.Red-Center-Studio/rcs-toolsRed-Center-Studiostreamable-httpv1.1.0Scanned

Free website checks: AI search readiness, AI crawler access, domain health, DNS risks. No key.

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Red Center Studio free tools MCP server can do

The Red Center Studio free tools MCP server is published by the GitHub account Red-Center-Studio. It has 5 tools. It can create or change data (3 tools: geo_audit, domain_health and ai_crawler_check), but cannot delete data. 2 tools only read.

1 tool reads private data (spof_scan); 4 tools bring in text other people can write (geo_audit, spof_scan, domain_health and 1 more); 2 tools can send data out of your system (geo_audit and ai_crawler_check). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • ai_crawler_checkCheck whether the main AI search crawlers from OpenAI, Anthropic, Perplexity and Google can reach a website: the robots.txt rule for each one, and a firewall test that requests the…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Check whether the main AI search crawlers from OpenAI, Anthropic, Perplexity and Google can reach a website: the robots.txt rule for each one, and a firewall test that requests the home page with each crawler's user agent and compares the answer with a normal visit. Returns each crawler with pass or fail and copy-paste fixes. Reads robots.txt and the home page only. Free, no key. Rate limited per connection.

    Annotations the server declares

    • title: AI crawler access check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • domain_healthCheck the things that quietly take a business offline: when the domain expires (RDAP), when the latest certificate issued for the site expires and who issued it (public Certificate…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Check the things that quietly take a business offline: when the domain expires (RDAP), when the latest certificate issued for the site expires and who issued it (public Certificate Transparency logs), whether the site answers over HTTPS, DNS basics, and email security (SPF, DMARC and DKIM at common selectors). Returns each finding with pass, warn or fail and a plain fix. Public data only. Free, no key. Rate limited per connection.

    Annotations the server declares

    • title: Domain health check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • geo_auditCheck how ready a public website is for AI assistants and search engines: AI crawler access in robots.txt, sitemap, llms.txt, structured data, titles and page basics.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Check how ready a public website is for AI assistants and search engines: AI crawler access in robots.txt, sitemap, llms.txt, structured data, titles and page basics. Returns a score out of 100, each check with pass, warn or fail, and copy-paste fixes. Reads the home page, robots.txt, sitemap.xml and llms.txt only. Free, no key. Rate limited per connection.

    Annotations the server declares

    • title: GEO audit
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • decode_errorExplain an error message from an app built on Bubble: the likely cause, and a link to the full fix guide.No findings

    Why it is in this group

    • The description's first verb is "explain": a word for reading.
    Description, as the server wrote it
    Explain an error message from an app built on Bubble: the likely cause, and a link to the full fix guide. Matches the text against the same list as the decoder page at redcenterstudio.com/decoder/. Free, no key.

    Annotations the server declares

    • title: Bubble error decoder
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • spof_scanFind which companies a business depends on for email, sign-in, DNS, website hosting, outbound email and SaaS, using public DNS only, and what a single outage would stop.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "find" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Find which companies a business depends on for email, sign-in, DNS, website hosting, outbound email and SaaS, using public DNS only, and what a single outage would stop. Returns the layers, the vendors, a risk score and recommendations. Free, no key. Rate limited per connection and to about 20 fresh scans an hour; repeat scans of the same domain within an hour come from cache.

    Annotations the server declares

    • title: Single point of failure scan
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

8 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__rcs-tools__spof_scan"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://redcenterstudio.com/api/tools/mcp: tools/list returned 5 tools to an anonymous client, including geo_audit (write), domain_health (write), ai_crawler_check (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 3 changed.+2 added~3 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rcs-tools https://redcenterstudio.com/api/tools/mcp
claude mcp add --transport http rcs-tools https://redcenterstudio.com/api/tools/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rcs-tools__spof_scan",
      "mcp__rcs-tools__decode_error"
    ],
    "ask": [
      "mcp__rcs-tools__geo_audit",
      "mcp__rcs-tools__domain_health",
      "mcp__rcs-tools__ai_crawler_check"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rcs-tools. Review it before you use it.

Capability tags behind 4 rules
  • mcp__rcs-tools__geo_audit untrusted-input, outbound
  • mcp__rcs-tools__spof_scan private-data, untrusted-input
  • mcp__rcs-tools__domain_health untrusted-input
  • mcp__rcs-tools__ai_crawler_check untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Red-Center-Studio/rcs-tools/verify?hash=6f3ebdd9198d8e720b05eb3cccd2744e56fea0979c84a2e4df9aeab1e734bb08" | jq -e '.changed == false'

Pinned hash 6f3ebdd9198d, from Nov 15, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Red-Center-Studio/rcs-tools/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Red-Center-Studio/rcs-tools
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Red-Center-Studio/rcs-tools.svg)](https://radar.anlyon.com/servers/io.github.Red-Center-Studio/rcs-tools)

Source: MCP Registry · repository. Synced Nov 15, 2026, 08:17 UTC.

Red Center Studio free tools MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Red Center Studio free tools MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Red Center Studio free tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Red Center Studio free tools MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Red Center Studio free tools MCP server have?

5 tools: 3 write, 2 read. geo_audit, domain_health, ai_crawler_check, spof_scan and decode_error.

Does the Red Center Studio free tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Red Center Studio free tools MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): geo_audit and ai_crawler_check.

Has the Red Center Studio free tools MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.