product-launch-checklist
https://productlaunchchecklist.com
Registry code: 30b97b159f63524b
Call get_checklist with the launch types that apply (see list_launch_types) and walk the person through it phase by phase, giving the reason for each item.
- endpoint
- https://productlaunchchecklist.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is product-launch-checklist live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
- Is product-launch-checklist free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does product-launch-checklist have?
- 3 tools: get_item, get_checklist, list_launch_types.
- Is product-launch-checklist safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 3 tools
- degraded → live
- unknown → live
- used for
- get a product launch checklist
- list launch types
- get one checklist item
- takes → gives
- text → text
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_checklist reads open 4h ago
Returns the product launch checklist as Markdown: phases from "before you launch" to the first month, each item with why it matters, when to skip it, tools and links. Type-specific items are only included for the launch types you pass.
{ "type": "object", "properties": { "phase": { "enum": [ "before", "product", "website", "assets", "listed", "day", "week", "month", "type" ], "type": "string", "description": "Only return one phase." }, "launch_types": { "type": "array", "items": { "enum": [ "saas", "mobile", "ai", "ext", "oss", "dev" ], "type": "string" }, "description": "What is being launched. Several can apply, e.g. [\"saas\", \"ai\"]." } }, "additionalProperties": false }arguments 36 lineslist_launch_types reads open 4h ago
Lists the launch types the checklist can be filtered by, with their keys.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_item reads unknown 4h ago
Returns a single checklist item by id (ids appear in get_checklist output, e.g. "p3").
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Item id" } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id30b97b159f63524b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/30b97b159f63524b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/30b97b159f63524b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.