Makeroo MCP server
app.makeroo/makeroomakeroo.appstreamable-httpv0.2.0Scanned
Search the Makeroo product directory and submit your product from your own agent.
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 2
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 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.
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 Makeroo MCP server can do
The Makeroo MCP server is published by makeroo.app, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: submit_listing and confirm_submission), but cannot delete data. 4 tools only read.
2 tools bring in text other people can write (confirm_submission and get_submission_status); 2 tools can send data out of your system (submit_listing and confirm_submission).
The fixed checks matched 1 finding (annotation-conflict). 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 12, 2026, version 0.2.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.
6 tools
Changes things 2Claude Code: ask
confirm_submissionStep 2 of 2.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.
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 Step 2 of 2. Call only after the maker explicitly confirmed the exact details and recipient email from the submit_listing preview. Pass the same fields plus its confirmationToken (valid 30 minutes). Emails a confirm link to makerEmail (expires after 48 hours) and returns a submission id that stays pending until the maker clicks it; poll get_submission_status. Changed fields or an expired token are rejected.
Annotations the server declares
- title: Confirm submission
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
submit_listingStep 1 of 2 for submitting a product to Makeroo on the maker's behalf.Can send data out1 finding
Why it is in this group
- The name "submit_listing" says "submit": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "submit_listing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "submit_listing" says "submit": a word for a change.
Description, as the server wrote it Step 1 of 2 for submitting a product to Makeroo on the maker's behalf. Only submit what you verified from the product's repo or site. Validates the details and returns a preview plus a confirmationToken. Stores and emails nothing. Show the maker the preview and the recipient email, and only after they explicitly confirm call confirm_submission.
Annotations the server declares
- title: Submit listing
- readOnlyHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_listingGet one live listing by its slug.No findings
Why it is in this group
- The name "get_listing" says "get": a word for reading.
Description, as the server wrote it Get one live listing by its slug.
Annotations the server declares
- title: Get listing
- readOnlyHint: true
- openWorldHint: false
get_submission_statusCheck a submission: pending, review (needs human look), live or rejected, with the verification verdict and reasons.Reads text others writeNo findings
Why it is in this group
- The name "get_submission_status" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it Check a submission: pending, review (needs human look), live or rejected, with the verification verdict and reasons.
Annotations the server declares
- title: Get submission status
- readOnlyHint: true
- openWorldHint: false
list_categoriesList valid category ids and names for submit_listing.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it List valid category ids and names for submit_listing.
Annotations the server declares
- title: List categories
- readOnlyHint: true
- openWorldHint: false
search_listingsSearch live Makeroo listings by keyword across name, tagline, description and tags.No findings
Why it is in this group
- The name "search_listings" says "search": a word for reading.
Description, as the server wrote it Search live Makeroo listings by keyword across name, tagline, description and tags. Omit query to browse the newest. Narrow by pricing, open source and platform; a listing whose value is unknown never matches that filter. Each listing carries attributes: pricing, openSource, repoUrl and platforms, null when unknown.
Annotations the server declares
- title: Search listings
- readOnlyHint: 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 private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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.
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.
Looked at Nov 20, 2026, 18:29 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://makeroo.app/mcp: tools/list returned 6 tools to an anonymous client, including submit_listing (write), confirm_submission (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 1 to 2
Findings
Matches of fixed checks, with the text they matched.
- Warnsubmit_listing
The server marks "submit_listing" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "submit_listing" says "submit": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 2 changed.+1 added~2 changedView diff
- Added:confirm_submissionChanges things
- Changed:get_submission_statusOnly readsinputSchema
- Changed:submit_listingChanges thingsdescriptioninputSchemaannotations
PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
- Tools that change things, listed without credentials: 1 to 2
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http makeroo https://makeroo.app/mcpclaude mcp add --transport http makeroo https://makeroo.app/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__makeroo__search_listings",
"mcp__makeroo__get_listing",
"mcp__makeroo__list_categories",
"mcp__makeroo__get_submission_status"
],
"ask": [
"mcp__makeroo__submit_listing",
"mcp__makeroo__confirm_submission"
],
"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 makeroo. Review it before you use it.
Capability tags behind 3 rules
- mcp__makeroo__submit_listing outbound
- mcp__makeroo__confirm_submission untrusted-input, outbound
- mcp__makeroo__get_submission_status untrusted-input
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/app.makeroo/makeroo/verify?hash=a09ad2bb614cf3d599a70f2e36acd83878329ec44b401e1babfb247359baefbd" | jq -e '.changed == false'Pinned hash a09ad2bb614c, from Nov 12, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.makeroo/makeroo/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.makeroo/makeroo)Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.
Makeroo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Makeroo MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 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 Makeroo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Makeroo 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 Makeroo MCP server have?
- 6 tools: 2 write, 4 read. submit_listing, confirm_submission, search_listings, get_listing, list_categories and get_submission_status.
Does the Makeroo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Makeroo 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): submit_listing and confirm_submission.
Has the Makeroo MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.