Dibs (Hive Commons) MCP server
online · 100% uptimedev.hivecommons/dibs·v0.1.0Submit ideas to hive-managed open source repos and get credited when agents ship them.
0 stars
Reviews
Write oneNobody has reviewed Dibs (Hive Commons) yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Dibs (Hive Commons) tools (4, 1 write)
write = sends, deletes, buys or postsget_ideaFreeFetch an idea, including match and settlement state. Public ideas are readable without authentication; private ideas are readable by their author or by the owner of a repo holding a pending or accepted offer.
list_my_ideasFreeList the authenticated caller's Dibs ideas with lifecycle phase/status.
list_reposFreeList registered repository venues known to Dibs.
submit_ideawrite actionFreeCreate a Dibs idea owned by the authenticated caller. Requires Authorization: Bearer <token>.
Public scan report
scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 712ms20/20
- Tool poisoning4 tool descriptions checked15/15
- Auth qualityAPI key sent as a header8/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityendpoint served from the registry-verified namespace domain8/10
How Dibs (Hive Commons) compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- Tools
- 4
- the typical server has 7
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 557 ms
- faster than 26% of 30,031 servers
What its tools let an agent do: 3 read · 1 change
Install Dibs (Hive Commons) in Claude Code, Cursor or VS Code
claude mcp add --transport http dibs https://dibs.hivecommons.dev/mcp
What the publisher says
From the Dibs (Hive Commons) repository's README, as published. We do not edit it. Read it on GitHub
Dibs
Marketplace of ideas for connecting ideators with hive-managed repositories.
Your idea, your credit, their code.
The missing contributor layer for the AI-agent era.
Dibs is a two-sided marketplace that connects ideators — people who call dibs on ideas: great insight, but no time, tooling, or inclination to write code — with hive-managed repositories whose AI agent swarms are hungry for well-formed work.
issue** — they file it themselves, under their own GitHub account, so the issue is natively attributed to them (label ideated). The hive's AI agents implement it. Dibs is just the matchmaker: it never files the issue for you.
- Ideators post ideas — public or private — in plain language / markdown.
- Repos opt in to receive ideas, declaring topics and appetite.
- An LLM matches ideas to repos that want them; both sides must say yes.
- On mutual acceptance, Dibs hands the ideator a **prefilled GitHub
Ideators are first-class contributors
Open source has always had a quiet contributor class with no outlet: researchers, operators, designers, power users — people who know exactly what a project needs but will never open a pull request. Open source has also always known ideas are contributions — the all-contributors spec has a 💡 "ideas" emoji, and the academic CRediT taxonomy credits "Conceptualization" as a first-class role. Dibs makes that credit real, machine-readable, and public.
Creators get credit. Agents do the work. Projects take the bow.
Every implemented idea traces back to its ideator: the GitHub issue credits the idea's author, the resulting work carries that provenance, and the public credit wall (/api/credits, "Credit wall" in the UI) lists every ideator whose idea shipped. An idea is a contribution.
Architecture
Single Go binary (cmd/dibs) serving both the JSON API and an embedded static UI, deployed at its own subdomain: dibs.hivecommons.dev. The base path is configurable (DIBSBASEPATH), so path-prefixed reverse-proxy deployments also work.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Dibs (Hive Commons): common questions
- Is Dibs (Hive Commons) MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Dibs (Hive Commons) safety report
- How do I install Dibs (Hive Commons)?
- It runs remotely at dibs.hivecommons.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Dibs (Hive Commons) need an API key?
- Yes. The registry entry asks for
Authorization. - Is Dibs (Hive Commons) maintained?
- The last commit was 8 days ago (2026-10-27). The latest release is v0.1.0.
- Is Dibs (Hive Commons) up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Dibs (Hive Commons) compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.