Skip to content

RoboDebut MCP server

com.robodebut/submissionsrobodebut.comstreamable-httpv1.0.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • 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 RoboDebut MCP server can do

The RoboDebut MCP server is published by robodebut.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: submit_project), but cannot delete data. 1 tool only reads.

1 tool reads private data (get_submission_status); 1 tool brings in text other people can write (submit_project).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

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

Last scanned Nov 19, 2026, version 1.0.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.

2 tools

Changes things 1Claude Code: ask
  • submit_projectSubmit the user's project to RoboDebut after the user authorizes submission and the required visible followed homepage badge is deployed.Reads text others write1 finding

    Why it is in this group

    • The name "submit_project" says "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The input schema at properties.homepage_url.description mentions "credentials".

      Matched text

      inputSchema.properties.homepage_url.description: "...lic HTTPS apex or www homepage, without credentials or a custom port. Shared service valida..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • get_submission_statusRead current stored submission status using the secret status_receipt returned only to the original creating request.Reads private dataNo findings

    Why it is in this group

    • The name "get_submission_status" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "secret": it reads secrets.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

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 20, 2026, 18:22 UTC, unchanged since Nov 6, 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
1
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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://robodebut.com/api/mcp: tools/list returned 2 tools to an anonymous client, including submit_project (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The input schema at properties.homepage_url.description mentions "credentials".

    Matched text

    inputSchema.properties.homepage_url.description: "...lic HTTPS apex or www homepage, without credentials or a custom port. Shared service valida..."

    What this check looks for

History

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

  1. Tools1 added.+1 addedView diff

Install

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

claude mcp add --transport http submissions https://robodebut.com/api/mcp
claude mcp add --transport http submissions https://robodebut.com/api/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__submissions__get_submission_status"
    ],
    "ask": [
      "mcp__submissions__submit_project"
    ],
    "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 submissions. Review it before you use it.

Capability tags behind 2 rules
  • mcp__submissions__submit_project untrusted-input
  • mcp__submissions__get_submission_status private-data

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/com.robodebut/submissions/verify?hash=eb3c62902db681d327b190545a34d49ce6c395ccf36f5f7567a19579329019fc" | jq -e '.changed == false'

Pinned hash eb3c62902db6, from Nov 19, 2026, 00:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.robodebut/submissions/changes.xml

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

Badge

Anlyon Radar badge for com.robodebut/submissions
[![Anlyon Radar](https://radar.anlyon.com/badge/com.robodebut/submissions.svg)](https://radar.anlyon.com/servers/com.robodebut/submissions)

Source: MCP Registry. Synced Nov 5, 2026, 06:17 UTC.

RoboDebut MCP server: questions and answers

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

Is the RoboDebut MCP server safe?

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

Can the RoboDebut MCP server delete data?

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

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

2 tools: 1 write, 1 read. submit_project and get_submission_status.

Does the RoboDebut MCP server need sign-in or OAuth?

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

Does the RoboDebut MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RoboDebut MCP server changed its tools?

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