PebbleLaunch MCP server
com.pebblelaunch/launchespebblelaunch.comstreamable-httpv0.1.0Scanned
Submit your product to PebbleLaunch daily launches, track its status, and read launches.
5 tools: 2 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 1
- 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 PebbleLaunch MCP server can do
The PebbleLaunch MCP server is published by pebblelaunch.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: submit_product and check_status), but cannot delete data. 3 tools only read.
1 tool reads private data (get_launch_calendar); 2 tools bring in text other people can write (submit_product and check_status); 1 tool can send data out of your system (submit_product). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
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.
Last scanned Nov 19, 2026, version 0.1.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.
5 tools
Changes things 2Claude Code: ask
check_statusStatus of a submission you made (needs its id + status_key).Reads text others write1 finding
Why it is in this group
- The name "check_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "check_status" says "status": a word for reading.
Description, as the server wrote it Status of a submission you made (needs its id + status_key). While ownership is pending this re-checks the proof (at most once a minute). Set resend_email to re-send the maker's confirmation link.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
submit_productSubmit the user's own product for a free launch day on PebbleLaunch.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "submit_product" 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.
- 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 Submit the user's own product for a free launch day on PebbleLaunch. Only submit products the user owns and has asked you to list. Returns an id, a one-time status_key (save it) and ownership-proof options. Next: add ONE proof on the product's domain (a .well-known file, a meta tag, or a DNS TXT record), then call check_status. The maker then confirms by email; nothing is listed before a human confirms. Rules: https://pebblelaunch.com/rules.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Only reads 3Show 3 read-only tools
get_launchOne launched/scheduled product by slug: details, launch day, votes, rank, and the badge snippet once live.No findings
Why it is in this group
- The name "get_launch" says "get": a word for reading.
Description, as the server wrote it One launched/scheduled product by slug: details, launch day, votes, rank, and the badge snippet once live.
Annotations the server declares
- readOnlyHint: true
get_launch_calendarSeats left per upcoming UTC day (free queue, premium, featured) and the next day with a free seat.Reads private dataNo findings
Why it is in this group
- The name "get_launch_calendar" says "get": a word for reading.
What it can reach
- private-dataThe name "get_launch_calendar" says "get" and "calendar": it reads calendars.
Description, as the server wrote it Seats left per upcoming UTC day (free queue, premium, featured) and the next day with a free seat.
Annotations the server declares
- readOnlyHint: true
list_launchesProducts launching on PebbleLaunch on a given UTC day (default today), ranked by human votes.No findings
Why it is in this group
- The name "list_launches" says "list": a word for reading.
Description, as the server wrote it Products launching on PebbleLaunch on a given UTC day (default today), ranked by human votes. Featured items are labelled.
Annotations the server declares
- readOnlyHint: true
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.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- 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 out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__launches__submit_product"
]
}
}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 19, 2026, 17:19 UTC, unchanged since Nov 19, 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://pebblelaunch.com/mcp: tools/list returned 5 tools to an anonymous client, including submit_product (write), check_status (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_status
The server marks "check_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"openWorldHint":true}; The name "check_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http launches https://pebblelaunch.com/mcpclaude mcp add --transport http launches https://pebblelaunch.com/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__launches__list_launches",
"mcp__launches__get_launch",
"mcp__launches__get_launch_calendar"
],
"ask": [
"mcp__launches__submit_product",
"mcp__launches__check_status"
],
"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 launches. Review it before you use it.
Capability tags behind 3 rules
- mcp__launches__get_launch_calendar private-data
- mcp__launches__submit_product untrusted-input, outbound
- mcp__launches__check_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/com.pebblelaunch/launches/verify?hash=a6bd48ebe2139ef094d780e43c0486763a54ac41a2ddad33fe17fec73d263bb6" | jq -e '.changed == false'Pinned hash a6bd48ebe213, from Nov 19, 2026, 17:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.pebblelaunch/launches/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.pebblelaunch/launches)Source: MCP Registry. Synced Nov 19, 2026, 17:17 UTC.
PebbleLaunch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the PebbleLaunch MCP server safe?
- No scan can promise that. What its definitions show: 5 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 PebbleLaunch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the PebbleLaunch 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 PebbleLaunch MCP server have?
- 5 tools: 2 write, 3 read. submit_product, check_status, list_launches, get_launch and get_launch_calendar.
Does the PebbleLaunch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the PebbleLaunch MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_product.
Has the PebbleLaunch MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.