# Red Center Studio free tools (remote · redcenterstudio.com)

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

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `redcenterstudio.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp.md), [page](https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp)

## Channel facts

- Endpoint: `https://redcenterstudio.com/api/tools/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 618 tokens (~123/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Red Center Studio free tools MCP server?

Red Center Studio free tools is a hosted endpoint at https://redcenterstudio.com/api/tools/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.

### Claude

```bash
claude mcp add --transport http red-center-studio-rcs-tools 'https://redcenterstudio.com/api/tools/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "red-center-studio-rcs-tools": {
      "url": "https://redcenterstudio.com/api/tools/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "red-center-studio-rcs-tools": {
      "type": "http",
      "url": "https://redcenterstudio.com/api/tools/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.red-center-studio-rcs-tools]
url = "https://redcenterstudio.com/api/tools/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "red-center-studio-rcs-tools": {
      "type": "remote",
      "url": "https://redcenterstudio.com/api/tools/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add red-center-studio-rcs-tools --url 'https://redcenterstudio.com/api/tools/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  red-center-studio-rcs-tools:
    url: "https://redcenterstudio.com/api/tools/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "red-center-studio-rcs-tools": {
      "Transport": "http",
      "Url": "https://redcenterstudio.com/api/tools/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add red-center-studio-rcs-tools -t streamable-http -u 'https://redcenterstudio.com/api/tools/mcp'
```

### Other

```json
{
  "mcpServers": {
    "red-center-studio-rcs-tools": {
      "type": "http",
      "url": "https://redcenterstudio.com/api/tools/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-20 (score 76, +3)

- [security improvement] HSTS header: fail → pass

### 2026-11-17 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-15 (score 72)

First indexed and scored.

## MCP tools (5)

### `geo_audit` (~114 tokens)

GEO audit

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.

Input parameters:

- `url` (string, required): The website address, for example example.com or https://www.example.com/.

### `spof_scan` (~106 tokens)

Single point of failure scan

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.

Input parameters:

- `domain` (string, required): The business domain, for example example.com.

### `decode_error` (~73 tokens)

Bubble error decoder

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.

Input parameters:

- `error` (string, required): The error message, or the key words from it.

### `domain_health` (~114 tokens)

Domain health check

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.

Input parameters:

- `domain` (string, required): The business domain, for example example.com.

### `ai_crawler_check` (~120 tokens)

AI crawler access check

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.

Input parameters:

- `url` (string, required): The website address, for example example.com or https://www.example.com/.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72

## Common questions

### What is the Red Center Studio free tools MCP server?

Red Center Studio free tools is an MCP server listed in the public MCP registry as io.github.Red-Center-Studio/rcs-tools. Free website checks: AI search readiness, AI crawler access, domain health, DNS risks. No key. This page covers its hosted endpoint (https://redcenterstudio.com/api/tools/mcp).

### Is the Red Center Studio free tools MCP server safe to use?

Red Center Studio free tools scores 77 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 Red Center Studio free tools MCP server expose?

Red Center Studio free tools exposes 5 tools: geo_audit, spof_scan, decode_error, domain_health, ai_crawler_check. Their descriptions and schemas cost roughly 527 tokens of context every time the server is loaded.

### Does the Red Center Studio free tools MCP server require authentication?

No. We connected to Red Center Studio free tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Red Center Studio free tools MCP server still maintained?

Red Center Studio free tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Red Center Studio free tools MCP server?

VerifyMCP ran 13 checks on Red Center Studio free tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://redcenterstudio.com/api/tools/mcp
- Repository: https://github.com/Red-Center-Studio/webdesk-mcp
- Website: https://redcenterstudio.com/webdesk/agents/docs/#free-tools
- Changelog RSS feed: https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp.json
- HTML version of this page: https://verifymcp.io/servers/red-center-studio-rcs-tools/api-tools-mcp
