Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dibs (Hive Commons)

REMOTE · DIBS.HIVECOMMONS.DEV

Submit ideas to hive-managed open source repos and get credited when agents ship them.

+3 this week 71 Trust /100

Last scanned (2 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security51
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 164 tokens (~41/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://dibs.hivecommons.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hive.hivecommons.dev CN=YR1,O=Let's Encrypt,C=US 10 Sept 2026 9 Dec 2026 RSA 2048 SHA256-RSA 59f73c32c055fb1080d4434be8493eabc97
SANs: *.hive.hivecommons.dev, *.lke.hive.hivecommons.dev, dibs.hivecommons.dev, hive.hivecommons.dev
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dibs.hivecommons.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
hivecommons.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dibs.hivecommons.dev/mcp Verified 200
http (plaintext) http://dibs.hivecommons.dev/mcp Inconclusive 405
MCP tools · 4 exposed · ~164 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_idea ~58

Fetch 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.

NameTypeReqDescription
idstringyesDibs idea id
NameTypeReqDescription
authorstringyes–
descriptionstringyes–
idstringyes–
issueURLstring––
matchesnull|arrayyes–
offersnull|array––
phasestringyes–
statusstringyes–
tagsnull|array––
targetRepostring––
titlestringyes–
urlstringyes–
visibilitystringyes–

No examples provided.

list_my_ideas ~23

List the authenticated caller's Dibs ideas with lifecycle phase/status.

Input schema present but exposes no named parameters.

NameTypeReqDescription
ideasnull|arrayyes–

No examples provided.

list_repos ~18

List registered repository venues known to Dibs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
reposnull|arrayyes–

No examples provided.

submit_idea ~65

Create a Dibs idea owned by the authenticated caller. Requires Authorization: Bearer <token>.

NameTypeReqDescription
descriptionstringyesplain language or markdown idea description
tagsnull|array–optional short tags for the idea
titlestringyesidea title
NameTypeReqDescription
idstringyes–
statusstringyes–
tagsnull|array––
urlstringyes–

No examples provided.

Install

How do I install the Dibs (Hive Commons) MCP server?

Dibs (Hive Commons) is a hosted endpoint at https://dibs.hivecommons.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · dibs.hivecommons.dev

# add to Claude Code
claude mcp add --transport http dev-hivecommons-dibs 'https://dibs.hivecommons.dev/mcp'
Common questions

What is the Dibs (Hive Commons) MCP server?

Dibs (Hive Commons) is an MCP server listed in the public MCP registry as dev.hivecommons/dibs. Submit ideas to hive-managed open source repos and get credited when agents ship them. This page covers its hosted endpoint (https://dibs.hivecommons.dev/mcp).

Is the Dibs (Hive Commons) MCP server safe to use?

Dibs (Hive Commons) scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Dibs (Hive Commons) MCP server expose?

Dibs (Hive Commons) exposes 4 tools: get_idea, list_my_ideas, list_repos, submit_idea. Their descriptions and schemas cost roughly 164 tokens of context every time the server is loaded.

Does the Dibs (Hive Commons) MCP server require authentication?

No. We connected to Dibs (Hive Commons) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Dibs (Hive Commons) MCP server still maintained?

Dibs (Hive Commons) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.