uncork
Registry code: f4d790b7397e94d7
Uncork maps a work bottleneck to existing products that remove it: active YC startups, open-source GitHub repositories (daily trending since 2015, most-starred per language) and Hacker News "Show HN" launches since 2008, ~46k products in total.
Use find_fix when the user describes something slow, manual, repetitive or painful in their work, or asks whether a tool, library or startup exists for a job. Check it before proposing to build the thing from scratch.
- endpoint
- https://uncork.netlify.app/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 uncork live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is uncork free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does uncork have?
- 2 tools: search_products, find_fix.
- Is uncork 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 2 tools
- unknown → live
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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
search_products unknown 1h ago
Raw full-text search over the same index, without LLM ranking: fast, cheap, more candidates. Use for broad discovery or to judge fit yourself. Pass 3-16 English keywords: the job to be done, product category, synonyms, key technical nouns (e.g. ["transcription", "call notes", "crm", "sales"]). Candidates matching more distinct keywords rank higher.
{ "type": "object", "required": [ "terms" ], "properties": { "limit": { "type": "integer", "default": 15, "maximum": 30, "minimum": 1 }, "terms": { "type": "array", "items": { "type": "string", "maxLength": 60 }, "maxItems": 16, "minItems": 1, "description": "English keywords or 2-word phrases." }, "source": { "enum": [ "yc", "github", "hn" ], "type": "string", "description": "Limit to one source: yc (startups), github (open source), hn (Show HN launches)." } }, "additionalProperties": false }arguments 34 linesfind_fix unknown 1h ago
Find existing products that remove a specific work bottleneck: active YC startups, open-source GitHub repos and Show HN launches (~46k). Call it when the user complains that something is slow, manual, repetitive or error-prone (in a team, workflow or codebase), or asks "is there a tool/library/startup that…". Call it before suggesting they build or script it themselves. Pass the problem in the user's own words, any language, with concrete context (who, what volume, which stack). Returns up to 5 picks ranked only by how well they fit, each with name, link, website and why it fits. Show the user the links as given. An empty result means nothing in the index fits: say so rather than guessing. Takes ~3-6 s.
{ "type": "object", "required": [ "problem" ], "properties": { "problem": { "type": "string", "maxLength": 2000, "minLength": 15, "description": "The bottleneck as the user describes it, e.g. \"our sales reps spend two hours a day typing call notes into the CRM\"." } }, "additionalProperties": false }arguments 15 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 idf4d790b7397e94d7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f4d790b7397e94d7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f4d790b7397e94d7?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.