Remote MCP endpoint that lets a coding agent submit a user's website or startup to the RoboDebut directory for manual review.
What you can do
Submit a project listing to RoboDebut with homepage URL, name, tagline, description, category and contact email
Read the submission instructions resource before submitting
Interpret structured results such as pending review, badge not found and retry later
Guide the agent through placing a required visible, followed homepage badge in server-sent HTML
When to use it
Use it when a user wants their website or startup listed in the RoboDebut directory and is willing to add the required badge to their public homepage. It is not a general-purpose directory or SEO tool.
Requirements
A remote MCP client that supports Streamable HTTP, pointed at the RoboDebut endpoint. No account or API key is needed. The user's public HTTPS apex or www homepage must serve a visible, followed badge link in its raw HTML, and a contact email is required.
Before you install
The tool creates or checks a listing proposal and sends the user's project details and contact email to RoboDebut. The badge must be publicly visible and followed on the homepage, which changes the user's site and its link policy; a badge does not prove ownership. Submission is rate limited per IP and per domain, and shared egress IPs share the allowance. The server asks that no passwords or API keys be handled.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.robodebut%2Fsubmissions/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.