Dibs (Hive Commons)

Name: Dibs (Hive Commons)
Author: hivecommons

제작자: hivecommons버전 0.1.0i★ –i클라우드에서 실행

레지스트리 이름dev.hivecommons/dibs

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i3개 중 3개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아주 새로움★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 클라우드에서 실행
전송 방식: Streamable HTTP
카테고리: 기타
입력해야 할 값: Authorization

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 3개 중 3개 통과
제작자의 서버에서 실행돼요. 내가 요청한 내용은 제작자의 서버를 거쳐요.
할 수 있는 일 4가지(도구) get_idea, list_my_ideas, list_repos, submit_idea
직접 입력할 값: Authorization

비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.

필요한 것

클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

터미널에서 이 명령어를 실행하세요

claude mcp add --transport http dibs https://dibs.hivecommons.dev/mcp --header 'Authorization: your-value'

실행하기 전에 빈 값을 채워 주세요.

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "dibs": {
      "url": "https://dibs.hivecommons.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "dibs": {
      "type": "http",
      "url": "https://dibs.hivecommons.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

Authorization 비밀 HTTP header
Bearer verified by the Hive Hub; required to submit or list your ideas and read your private ideas. See the repository README's Token section.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 7일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

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.
list_my_ideas
List the authenticated caller's Dibs ideas with lifecycle phase/status.
list_repos
List registered repository venues known to Dibs.
submit_idea
Create a Dibs idea owned by the authenticated caller. Requires Authorization: Bearer .

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 9일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 도메인 hivecommons.dev 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
✓ 통과
엔드포인트 응답
120ms 만에 응답(HTTP 200)
– 해당 없음
OAuth로 로그인
로그인 필요 없음
✓ 통과
도구 설명에 숨겨진 지시 없음
도구 설명 4개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 18721개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 18721개 중 67%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 18721개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Dibs (Hive Commons), 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

입력해야 할 값: Authorization

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.1.0)은 21일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Soleil Clusters

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

제작자: formulahendry초기↓ 66/주★ 44014개월 전 업데이트

내 컴퓨터에서 실행

설치

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

제작자: desktop-commander성장 중★ 2114일 전 업데이트

클라우드에서 실행✓ desktopcommander.app

설치

Soleil Clusters

Read and build visual moodboards, shot lists and lookbooks from an AI assistant.

제작자: arconkli초기↓ 119/주오늘 업데이트

컴퓨터 또는 클라우드✓ soleilpictures.com

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

Dibs

A place to offer software ideas to projects and retain credit for them.

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: projects that use Hive to run coding agents under maintainer-chosen rules.

Ideators post ideas — public or private — in plain language / markdown.
Repos opt in to receive ideas, declaring topics and appetite.
A language model (LLM) matches ideas to repos that want them; both the idea contributor and the receiving project must accept the match.
On mutual acceptance, Dibs hands the ideator a prefilled GitHub issue — they file it themselves, under their own GitHub account, so the issue is natively attributed to them (label ideated). The receiving project can then have its agents work on it under its own review rules. In this default flow Dibs is just the matchmaker: it never files the issue for you.

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 with a settled idea: a GitHub issue URL has been recorded. This credits the proposal, not proof that its implementation shipped or its issue was closed. Settled ideas appear regardless of their visibility setting: settling a private idea makes its credit facts (author, title/TLDR, target, issue URL, and time) public, but not its body or private detail endpoint.

Try Dibs in your browser

No local installation or Go toolchain is needed. Open dibs.hivecommons.dev to browse the public surface; posting needs a Hive Hub sign-in and filing the issue needs a GitHub account.

Sign in and describe your idea in plain language. Choose public or private deliberately; unsettled private ideas are not included in the public wall.
Review suggested repositories and offer the idea to a suitable project. For Hive-managed targets, both sides accept before issue filing.
Open the prefilled GitHub issue, review it, and file it yourself.
Confirm the resulting issue URL in Dibs. This step is settlement: it records the handoff, not completion of the proposed work. Confirming also publishes the credit facts above, even for an idea marked private.

Non-Hive GitHub targets can skip the receiving-project acceptance step. For settlement and privacy details, see the consumer API. To submit from a coding agent instead, see MCP setup.

Maintainer and developer reference

The following sections cover running Dibs, its API, and local development, not prerequisites for using the hosted site.

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 (DIBS_BASE_PATH), so path-prefixed reverse-proxy deployments also work.

Package	Purpose
`pkg/server`	HTTP server, base-path routing, embedded UI
`pkg/auth`	Auth bridge — validates the hive hub session cookie against the hub
`pkg/store`	Idea model + JSON file store (atomic writes, no external DB), offer/settlement state machine
`pkg/fsutil`	Shared atomic JSON persistence helper (temp file + rename, mode 0600) used by the file stores
`pkg/api`	Idea CRUD + matching/offer/feed/decide/notification API (author-scoped, private ideas never leak)
`pkg/registry`	Hive-managed repo profiles + "accepting ideas" opt-in
`pkg/match`	LLM idea↔repo scoring via litellm gateway, cached TLDRs, "✨ Embellish" draft refinement, deterministic keyword fallback
`pkg/settle`	Settlement — prefilled GitHub new-issue URL the ideator files themselves (`ideated` label, 🐝 Dibs footer, URL-length budget) + issue-URL confirmation; legacy token mode. Ideas can target ANY GitHub repo: non-hive targets skip acceptance and their issues carry a "request a hive" growth CTA
`pkg/notify`	In-app notification feed (bell): matches, offers, decisions, issues
`pkg/mcpserver`	Streamable HTTP MCP endpoint exposing Dibs tools (see Submit ideas from your agent)
`pkg/intake`	Extracts idea text from uploaded documents or transcribed audio
`pkg/game`	Gamification layer — points, levels, badges — recomputed from stored idea state, never a mutable counter
`pkg/catalog`	Builds and searches a separate CNCF project catalog
`pkg/history`	Backfills public GitHub activity for hive-managed repos; persists daily counts for repo index charts
`pkg/indexformula`	Weighted composite behind the repo market index
`pkg/news`	Turns recent merged PRs into repo news cards
`pkg/deps`	Single place declaring the subsystem dependencies the HTTP server, JSON API, and MCP endpoint are wired with

Configuration

Env var	Default	Meaning
`DIBS_BASE_PATH`	`/`	Base path every route/asset is served under (set e.g. `/ideas` for path-prefixed proxying)
`DIBS_ADDR`	`:8080`	Listen address
`DIBS_METRICS_ADDR`	(unset)	Internal Prometheus `/metrics` listener (e.g. `:9090`); unset keeps it off. See `deploy/`
`HUB_URL`	`https://hive.hivecommons.dev`	Hive hub for session validation & repo sync
`DATA_DIR`	`/data`	JSON store directory
`REPOS_SEED_FILE`	(unset)	Static JSON seed of repo profiles for dev/demo
`DIBS_LLM_BASE_URL`	(unset)	OpenAI-compatible gateway (hive litellm), e.g. `http://litellm:4000/v1`. Unset → deterministic keyword matcher
`DIBS_LLM_API_KEY`	(unset)	Bearer token for the LLM gateway
`DIBS_LLM_MODEL`	`gpt-4o-mini`	Model name routed by the gateway
`DIBS_GITHUB_TOKEN`	(unset)	Legacy mode only for issue creation: when set, Dibs opens the credited issue server-side on accept. Unset (default), the ideator files a prefilled GitHub issue themselves — native attribution. Also used, when present, to authenticate the GitHub lookup that verifies a confirmed issue URL (anonymous otherwise)
`DIBS_ADMINS`	(unset)	Comma-separated, case-insensitive GitHub logins granted admin access (idea-moderation endpoints)
`DIBS_CLANKER_MARKERS`	`hive: agent=,kubestellar-hive[bot]`	Comma-separated, case-insensitive markers matched against PR branch/labels/body/author to classify agent activity
`DIBS_INTAKE_MAX_MB`	`25`	Max upload size (MB) accepted for idea-intake file uploads
`DIBS_INTAKE_EXTRACT_WORKER`	_(on)_	Set to `off` to extract uploaded documents in-process instead of in a memory-limited, time-limited child worker (not recommended: crafted documents can then exhaust the server's memory)
`DIBS_STT_URL`	(unset)	Speech-to-text gateway URL; when set, enables voice/audio idea submission
`DIBS_STT_KEY`	(unset)	API key for the STT gateway
`DIBS_STT_MODEL`	(unset)	Model name routed by the STT gateway

Legacy IDEATE_* names (the pre-rename prefix) are still honored as fallbacks for every DIBS_* variable.

Roadmap

See ROADMAP.md for what is planned next. Delivery history:

Wave 1 (done): scaffold, hub auth bridge, idea CRUD, repo registry.
Wave 2 (done): LLM matching + TLDRs, swipe UX ("offer" / "pass"), issue settlement (credited GitHub issues), notifications.
Wave 3 (done): deployment (GHCR image + deploy/ manifests for dibs.hivecommons.dev), public landing page, public credit wall, ideator profile stats.
Wave 4 (done): matchmaker settlement — the ideator files a prefilled GitHub issue themselves (native attribution, ideated label) and confirms the issue URL; LLM-assisted idea refinement on posting and repo-tailored expansion on submission; token-based settlement demoted to legacy.
Later: cookie-domain/hub-OAuth session sharing, non-hive receptor repos, idea economics.

Deployment

Every push to main publishes ghcr.io/hivecommons/dibs (latest + commit sha) via .github/workflows/docker.yml; the image is distroless and runs as non-root. Plain Kubernetes manifests for dibs.hivecommons.dev (Deployment, Service, cert-manager TLS Ingress, PVC, ConfigMap/Secret) live in deploy/, including the required DNS record and hub-cookie prerequisites.

Public surface (no sign-in required)

Route	Purpose
`GET /`	Landing page (pitch + sign-in) — signed-in users get the full app
`GET /api/credits`	Credit wall data: settled ideas only (handle, title, TLDR, repo, issue URL)
`GET /api/leaderboard`	Aggregate ideator scores/levels/badges
`GET /api/ticker`	Public idea ticker tape for the logged-out landing page
`GET /api/board`	Live-markets board shown on the logged-out landing page
`GET /api/stats`	Aggregate, non-identifying counts
`GET /api/repos/{org}/{repo}/index`	Repo value-index chart series
`GET /api/repos/{org}/{repo}/news`	Repo news feed
`GET /api/repos/{org}/{repo}/qr.png`	Repo QR code
`GET /healthz`	Liveness check + embedded git version
`GET /readyz`	Readiness check — verifies the data store is accessible/writable

Everything else requires a hive hub session; signed-in ideators additionally get GET /api/me/stats (ideas posted / offered / accepted / settled).

For response schemas, eligibility/privacy rules, settlement actions, rewards, and stability levels, see the credit-wall consumer API.

Submit ideas from your agent

Dibs exposes a stateless Streamable HTTP MCP endpoint at https://dibs.hivecommons.dev/mcp, so Claude Code, Copilot CLI, Cursor, Gemini CLI, Codex, and other MCP clients can submit ideas without leaving the agent.

Dibs is listed in the official MCP Registry as dev.hivecommons/dibs (registry entry). Search for that full name: a plain dibs search also returns unrelated servers with the same name, including the 1stDibs marketplace and other coding-agent tools called dibs. How the listing is published is covered in MCP Registry publishing.

Available tools:

Tool	Auth	Purpose
`submit_idea(title, description, tags?)`	Required	Creates a private draft idea owned by you and returns its id and API URL
`list_my_ideas()`	Required	Lists your ideas with lifecycle phase/status
`get_idea(id)`	Optional for public ideas; required for private ideas (author, or owner of a repo holding a pending or accepted offer)	Shows detail, matches, offers, and settlement state
`list_repos()`	Not required	Lists registered repo venues

Token

Use Authorization: Bearer . Dibs first asks the Hive Hub /api/saas/whoami endpoint to verify the bearer token server-to-server; the hub already accepts GitHub bearer tokens for registered hub user

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

Dibs (Hive Commons)

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

직접 입력할 값

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

Soleil Clusters

제작자의 README

Dibs

Ideators are first-class contributors

Try Dibs in your browser

Maintainer and developer reference

Architecture

Configuration

Roadmap

Deployment

Public surface (no sign-in required)

Submit ideas from your agent

Token