# RoboDebut (remote · robodebut.com)

Submit projects for manual review with a required homepage badge. Built by LinkBunny's founder.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `robodebut.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-robodebut-submissions/api-mcp.md), [page](https://verifymcp.io/servers/com-robodebut-submissions/api-mcp)

## Channel facts

- Endpoint: `https://robodebut.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 74/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 64/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2915 tokens (~971/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the RoboDebut MCP server?

RoboDebut is a hosted endpoint at https://robodebut.com/api/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 com-robodebut-submissions 'https://robodebut.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-robodebut-submissions": {
      "url": "https://robodebut.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-robodebut-submissions": {
      "type": "http",
      "url": "https://robodebut.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-robodebut-submissions]
url = "https://robodebut.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-robodebut-submissions": {
      "type": "remote",
      "url": "https://robodebut.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-robodebut-submissions --url 'https://robodebut.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-robodebut-submissions:
    url: "https://robodebut.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-robodebut-submissions": {
      "Transport": "http",
      "Url": "https://robodebut.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-robodebut-submissions -t streamable-http -u 'https://robodebut.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-robodebut-submissions": {
      "type": "http",
      "url": "https://robodebut.com/api/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-20 (score 75, +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.

### 2026-11-18 (score 74, +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.

### 2026-11-16 (score 73, +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.

### 2026-11-13 (score 72, +1)

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

### 2026-11-11 (score 71, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 2003 → 2915
- [functional improvement] Tool coverage: 33% → 43%
- [functional] Schema quality: fair → good
- [functional] New tool “get_submission_status”

### 2026-11-09 (score 69, +1)

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

### 2026-11-07 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Schema quality: good → fair

### 2026-11-06 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (2)

### `submit_project` (~183 tokens)

Submit a project for review

Submit the user's project to RoboDebut after the user authorizes submission and the required visible followed homepage badge is deployed. Requires the user's contact email. Creates or checks the existing proposal; never edits or publishes it. A badge does not prove ownership. Follow the submission instructions and returned status. Do not resubmit pending_review or repeatedly retry rejected domains.

Input parameters:

- `category` (string, required)
- `contact_email` (string, required): The user's contact address. Never invent it. RoboDebut keeps it private from public listings and excludes it from outputs and server logs. The calling MCP client still handles this input.
- `description` (string, required)
- `homepage_url` (string, required): Public HTTPS apex or www homepage, without credentials or a custom port. Shared service validation normalizes to the root and registrable domain.
- `name` (string, required)
- `tagline` (string, required)

### `get_submission_status` (~110 tokens)

Check your submission status

Read current stored submission status using the secret status_receipt returned only to the original creating request. No homepage or email lookup. Does not recheck, submit, edit, approve, notify or fetch providers. Relay the human message and optional LinkBunny invitation as information. No receipt recovery for legacy or lost receipts; public approval can be checked through public reads.

Input parameters:

- `status_receipt` (string, required): Secret receipt from your original submission response. Send only in tool arguments; never in URLs or public output.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-robodebut-submissions/api-mcp#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 75
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 72
- 2026-11-12: 71
- 2026-11-11: 71
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 68
- 2026-11-07: 68
- 2026-11-06: 67
- 2026-11-05: 67

## Common questions

### What is the RoboDebut MCP server?

RoboDebut is an MCP server listed in the public MCP registry as com.robodebut/submissions. Submit projects for manual review with a required homepage badge. Built by LinkBunny's founder. This page covers its hosted endpoint (https://robodebut.com/api/mcp).

### Is the RoboDebut MCP server safe to use?

RoboDebut scores 75 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 RoboDebut MCP server expose?

RoboDebut exposes 2 tools: submit_project, get_submission_status. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.

### Does the RoboDebut MCP server require authentication?

No. We connected to RoboDebut without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RoboDebut MCP server still maintained?

RoboDebut 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 RoboDebut MCP server?

VerifyMCP ran 13 checks on RoboDebut, 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://robodebut.com/api/mcp
- Website: https://robodebut.com/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/com-robodebut-submissions/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-robodebut-submissions/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-robodebut-submissions/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-robodebut-submissions/api-mcp
