dribba
Registry code: 43ac3cecb9cdf71f
Dribba is an end-to-end digital product studio (Barcelona · Andorra). This is the product surface: read the service catalog and case studies, get a ballpark budget, read company facts, and submit a contact request (which asks the user to confirm first). For documentation and search, connect to https://dribba.com/docs/mcp. Every tool of both surfaces is callable here.
- endpoint
- https://dribba.com/mcp
- door code
- 4c088af024e2b53c
- protocol
- http-sse ·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 dribba live?
- Partly — its last checks failed now and then (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is dribba free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dribba have?
- 5 tools: submit_contact_request, estimate_project, list_projects, list_services, company_facts.
- Is dribba 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 99.2%· all time 99.3%
last good check
of 5 tools
- live → degraded· fetch failed
- live → degraded· fetch failed
- degraded → live
- degraded → live
- degraded → live
- topic
- productivity & business
- used for
- estimate an app development budget
- browse a studio's case studies
- send a project inquiry
- takes → gives
- text → data
- tools
- 4 reads1 sends messages
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.
list_projects reads open 15h ago
List Dribba's case studies (slug, title, industry).
{ "type": "object", "required": [], "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum number of case studies to return." }, "industry": { "type": "string", "description": "Case-insensitive substring match on the industry, e.g. \"fintech\". Omit for all industries." } }, "additionalProperties": false }arguments 17 lineslist_services reads open 19h ago
List Dribba's services with a one-line summary and URL.
{ "type": "object", "required": [], "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Maximum number of services to return. Omit for all of them." } }, "additionalProperties": false }arguments 13 linescompany_facts reads open 15h ago
Structured facts about Dribba: positioning, offices, team, distinctions, clients.
{ "type": "object", "required": [], "properties": { "fields": { "type": "array", "items": { "type": "string" }, "description": "Subset of fact keys to return (e.g. [\"offices\",\"distinctions\"]). Omit for every fact." } }, "additionalProperties": false }arguments 14 linessubmit_contact_request sends messages unknown never probed
Submit a real project inquiry to Dribba on behalf of the user. This sends an email and creates a lead — ONLY call it after the user has explicitly confirmed the exact name, email and message to be sent. Dribba replies within 1h. Rate-limited per client.
{ "type": "object", "required": [ "name", "email", "message" ], "properties": { "name": { "type": "string", "description": "Full name of the person making the inquiry." }, "email": { "type": "string", "description": "Email address Dribba should reply to." }, "budget": { "type": "string", "description": "Approximate budget range, e.g. \"30-60k EUR\" (optional)." }, "company": { "type": "string", "description": "Company name (optional)." }, "message": { "type": "string", "description": "The inquiry, confirmed by the user." } } }arguments 30 linesestimate_project reads unknown 15h ago
Ballpark budget and range for an app/product, mirroring dribba.com's public calculator. Minimum project budget is €30,000.
{ "type": "object", "required": [ "platforms" ], "properties": { "design": { "enum": [ "basic", "custom", "premium" ], "type": "string" }, "timeline": { "enum": [ "rush", "normal", "relaxed" ], "type": "string" }, "platforms": { "type": "array", "items": { "enum": [ "ios", "android", "web", "desktop" ], "type": "string" }, "description": "At least one target platform." }, "complexity": { "enum": [ "mvp", "standard", "complex" ], "type": "string" } } }arguments 45 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 id43ac3cecb9cdf71f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/43ac3cecb9cdf71f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/43ac3cecb9cdf71f?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.