# Dibs (Hive Commons) (remote · dibs.hivecommons.dev)

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

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `dibs.hivecommons.dev`: 71/100 (this document), [markdown](https://verifymcp.io/servers/dev-hivecommons-dibs/dibs.md), [page](https://verifymcp.io/servers/dev-hivecommons-dibs/dibs)

## Channel facts

- Endpoint: `https://dibs.hivecommons.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 164 tokens (~41/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

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

### Claude

```bash
claude mcp add --transport http dev-hivecommons-dibs 'https://dibs.hivecommons.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-hivecommons-dibs": {
      "url": "https://dibs.hivecommons.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-hivecommons-dibs": {
      "type": "http",
      "url": "https://dibs.hivecommons.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-hivecommons-dibs]
url = "https://dibs.hivecommons.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-hivecommons-dibs": {
      "type": "remote",
      "url": "https://dibs.hivecommons.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-hivecommons-dibs --url 'https://dibs.hivecommons.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-hivecommons-dibs:
    url: "https://dibs.hivecommons.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-hivecommons-dibs": {
      "Transport": "http",
      "Url": "https://dibs.hivecommons.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-hivecommons-dibs -t streamable-http -u 'https://dibs.hivecommons.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-hivecommons-dibs": {
      "type": "http",
      "url": "https://dibs.hivecommons.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 71, +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.

### 2026-11-02 (score 70, +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.

### 2026-10-31 (score 69, +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.

### 2026-10-29 (score 68, +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.

### 2026-10-27 (score 67, +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.

### 2026-10-25 (score 66, +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.

### 2026-10-23 (score 65, +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.

### 2026-10-21 (score 64, +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.

## MCP tools (4)

### `get_idea` (~58 tokens)

Get idea

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.

Input parameters:

- `id` (string, required): Dibs idea id

Output parameters:

- `author` (string)
- `description` (string)
- `id` (string)
- `issueURL` (string)
- `matches` (null|array)
- `offers` (null|array)
- `phase` (string)
- `status` (string)
- `tags` (null|array)
- `targetRepo` (string)
- `title` (string)
- `url` (string)
- `visibility` (string)

### `list_my_ideas` (~23 tokens)

List my ideas

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

Output parameters:

- `ideas` (null|array)

### `list_repos` (~18 tokens)

List repos

List registered repository venues known to Dibs.

Output parameters:

- `repos` (null|array)

### `submit_idea` (~65 tokens)

Submit idea

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

Input parameters:

- `description` (string, required): plain language or markdown idea description
- `tags` (null|array): optional short tags for the idea
- `title` (string, required): idea title

Output parameters:

- `id` (string)
- `status` (string)
- `tags` (null|array)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-hivecommons-dibs/dibs#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 70
- 2026-11-03: 70
- 2026-11-02: 70
- 2026-11-01: 69
- 2026-10-31: 69
- 2026-10-30: 68
- 2026-10-29: 68
- 2026-10-28: 67
- 2026-10-27: 67
- 2026-10-26: 66
- 2026-10-25: 66
- 2026-10-24: 65
- 2026-10-23: 65
- 2026-10-22: 64
- 2026-10-21: 64
- 2026-10-20: 63
- 2026-10-19: 63

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

## Links

- Remote endpoint: https://dibs.hivecommons.dev/mcp
- Repository: https://github.com/hivecommons/dibs
- Changelog RSS feed: https://verifymcp.io/servers/dev-hivecommons-dibs/dibs.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-hivecommons-dibs/dibs.json
- HTML version of this page: https://verifymcp.io/servers/dev-hivecommons-dibs/dibs