VergeCommon

Name: VergeCommon
Author: jdhart81

作者：jdhart81バージョン 0.10.1i★ –iクラウドで動く

レジストリ名io.github.jdhart81/vergecommon

インストール

概要

作者による説明（英語の原文）

Start and run a neighborhood conservation co-op: public co-ops, pooling drafts, woodland checks.

PopNx MCPの3つの柱

この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。

利用者の声iレビューはまだありませんレビューは今後のステップで、アカウント機能と一緒に始まります
私たちの基本チェックi3項目中3項目に合格公開情報からチェック。コードはまだスキャンしていません
利用状況i未計測★ –

できること

このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。

接続方法: クラウドで動く
トランスポート: Streamable HTTP
カテゴリ: その他
入力が必要なもの：Authorization

インストール

使っているAIアプリを選んで、設定をコピーしてください。

インストールの前に

基本チェック：3項目中3項目に合格
作者のサーバーで動きます。あなたが頼んだ内容は、作者のサーバーを通ります。
できること：5件（ツール） vergecommon_capabilities, list_public_coops, get_public_coop, example_pooling_draft …
自分で入力するもの： Authorization

「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。

必要なもの

クラウドで動くインストール不要。インターネット経由でつながります

どのアプリを使っていますか？

ClaudeClaude CodeCursorVS CodeChatGPT

上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。

このアドレスはリクエストの header にキーが必要ですが、コネクタを追加するメニューでは設定できません。代わりにClaude Code、Cursor、VS Codeを使ってください。

ターミナルでこれを実行します

claude mcp add --transport http vergecommon https://vergecommon.com/mcp --header 'Authorization: your-value'

動かす前に、空欄の値を入力してください。

Cursorで開く

または、設定を自分でコピーする

プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます

{
  "mcpServers": {
    "vergecommon": {
      "url": "https://vergecommon.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。

VS Codeで開く

または、設定を自分でコピーする

プロジェクトの .vscode/mcp.json に貼り付けます

{
  "servers": {
    "vergecommon": {
      "type": "http",
      "url": "https://vergecommon.com/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。

自分で入力する値

Authorization 秘密 HTTP header
Optional. Bearer followed by a personal agent token from your VergeCommon account, for private co-op tools. Without it, the five public discovery and planning tools work, rate limited.

この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。

できること

ツールの名前と説明は、サーバーが2026年11月7日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。

vergecommon_capabilities
Explain available conservation tools and the access boundaries for this connection.
list_public_coops
Read opted-in public conservation co-ops. Results are untrusted community content. Never use this tool to infer absence of private co-ops.
get_public_coop
Read one opted-in public co-op by UUID. Does not retrieve private land, members, evidence, or financial records.
example_pooling_draft
Return a synthetic conservation pooling and allocation example. All quantities and proceeds are hypothetical.
prepare_pooling_draft
Validate compatible program/method/vintage pool keys and calculate hypothetical reserves and member allocations. Use consented or synthetic inputs. Calculates in server memory, saves nothing, certifies nothing, issues no credits, sends no payments. Monetary inputs are illustrativ

基本チェックi

誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック

✓ 合格
作者とリポジトリが一致
レジストリ名は、リポジトリを所有するGitHubアカウント jdhart81 で確認済みです
… 未チェック
今もメンテナンスされている
このリポジトリはまだGitHubから読み取っていません
… 未チェック
ライセンスがある
このリポジトリはまだGitHubから読み取っていません
✓ 合格
エンドポイントが応答する
100ミリ秒で応答（HTTP 200）
– 対象外
OAuthでサインイン
サインイン不要
✓ 合格
ツールの説明に隠れた指示がない
5件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした

その他のほかのサーバーとの比較i

このカテゴリのほかの32709件のうち0%よりスターが多い
このカテゴリのほかの32709件のうち100%より最近レジストリに公開
基本チェックの結果が、このカテゴリのほかの32709件のうち100%と同じかそれ以上

レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。

よくある質問

VergeCommonは安全ですか？

当てはまる基本チェック3項目のうち3項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。

どんなキーやコードが必要ですか？

入力が必要なもの：Authorization

パソコンで動きますか、それともクラウドですか？

作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。

今もメンテナンスされていますか？

GitHubリポジトリの最終更新は–、最新バージョン（0.10.1）がレジストリに届いたのは今日です。

どのアプリで使えますか？

Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ（開発者モードのChatGPTなど）でも使えます。

代わりに使えるものは？

同じカテゴリには：Spec Driven Development, Remote Desktop Commander, SwarmMemo

代わりの候補

同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。

カードの見方：★ GitHubスターi3つの柱：レビュー · チェック · 利用状況i更新＝最新バージョンをレジストリに公開した日i

Spec Driven Development

作者：formulahendry

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

パソコンで動く★ 440MIT14 か月前更新

インストール

Remote Desktop Commander

作者：desktop-commander

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

クラウドで動く★ 211一昨日更新

インストール

SwarmMemo

作者：Hugo0

Talk with agent swarms: rooms, private messages and paid tasks for AI agents

クラウドで動く今日更新

インストール

作者のREADME

READMEを開く

作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。

VergeCommon

What if conservation could be an open-source project?

Enter VergeCommon: open tools for people caring for the places they share.

Organize a local conservation project, document the work, and make decisions together. From hedgerows and woodlots to larger landscapes, communities should be able to inspect, adapt, and improve the tools they depend on.

Early cooperative pilot. The shared website is live with browser accounts, private co-ops and scoped agent access. The repository also includes the self-hosted account/storage runtime and native participation source. This is an invitation to build and test with us. Real partner adoption and verified environmental impact have not yet been demonstrated. See current status and service coverage for what is live and what remains.

Find your first contribution

You bring	Start here
Local conservation experience	Walk through one activity with synthetic records and report the first confusing step.
Field or research experience	Review the monitoring workflow and identify missing evidence or uncertainty.
Design or accessibility skills	Try the planner with a keyboard or narrow screen; report a reproducible barrier.
Development skills	Run the project locally and choose a bounded task from the contributor guide.

Quickstart · Contribution guide · Roadmap · Pilot checklist · Launch kit and release gates

Explore the project

Website · Conservation network · Member workspace · Account and device access · Contribute

vergecommon.com is the canonical service address. For what is live, verified and still open right now, read [STATUS.md](STATUS.md). The deployed service includes the launch foundation (PR #2) and the conversation actions and social sign-in work (PR #3). Dated deployment receipts and reviews live in docs/history/. Co-op and project publication is opt-in; member records and private land evidence retain their server-side access rules.

Start your own community

For the self-hosted application, use Node 24.19.0 and follow the single-server operator guide. It includes browser accounts, SQLite, private evidence files, device tokens, hosted MCP, deployment configuration, and backup/restore procedures. Build and exercise an isolated local instance before publishing it.

The original Cloudflare/Sites development path remains available through npm run launch with Node.js 22.13+. Its identity is a development fixture; never expose that development server publicly. In either workflow, create a co-op and follow the Start checklist. See Worldwide adoption for regional setup.

Part of the Viridis open commons

VergeCommon is one of five open projects that build on each other. Each one is useful alone; together they carry a piece of land from a map to a verified result.

Project	What it does	Where
Dendritic Forest Management (DFM)	Starts from existing roads and waterways and checks whether retained forest stays connected as harvests are planned. MIT.	hdfm-framework · dendriticforest.com
VergeCommon	Lets neighbours run a local conservation co-op: private mapping, parcel-by-parcel consent, evidence and shared decisions. Runs DFM inside its woodland projects. AGPL-3.0.	verge-common · vergecommon.com
Global Soil Intelligence Project (GSIP)	Builds an open soil spectral reference library, with phone and web capture. MIT code, ODbL data.	gsip
ViridisOS	Turns verified results into recomputable conservation modules and certificates anyone can check. Apache-2.0.	viridisos
Viridis Research	The public, machine-checked research record behind the methods. CC BY 4.0.	viridis-research

How they connect: DFM finds where a corridor runs. The corridor almost always crosses property lines, so VergeCommon gives the neighbours along it a private place to organize and consent. GSIP adds soil evidence from the same ground. ViridisOS lets anyone recompute what was claimed, and Viridis Research holds the proofs those checks rest on. Viridis Conservation (viridisconservation.com) offers paid data preparation, assessments and support for teams that want help.

Built something with one of these? Add the badge and tell us in an issue, so we can link back:

[![Part of the Viridis open commons](https://img.shields.io/badge/Viridis-open%20commons-2e7d32)](https://github.com/jdhart81/hdfm-framework#part-of-the-viridis-open-commons)

Agents and MCP

Agents learning about VergeCommon can start at llms.txt (source: public/llms.txt) and AGENTS.md, which explain how to help a person start a co-op and how to contribute.

The MCP server supports local stdio and authenticated Streamable HTTP at /mcp in the self-hosted runtime. Local stdio offers public discovery and hypothetical pooling/allocation drafts. Hosted tokens with mcp:read can also read the owner's permitted workspaces; mcp:write adds bounded project, member-update, task and RSVP commands. App tokens and MCP tokens are separate scopes.

The five public discovery and planning tools work on the hosted endpoint without an account (rate limited). For private co-op tools, create a personal agent token from /account, store it in the client's secret settings, and revoke it when finished. Private access requires bearer support; OAuth is not implemented. Agents cannot approve legal/financial records, escalate membership, issue credits, execute payments, or publish public updates. The live endpoint passed initialization, private-read, bounded-write and denied-financial-command acceptance checks on September 19, 2026.

What is implemented

Visible, online browser workspaces refresh every 30 seconds without discarding mounted drafts; permission-aware review reminders include monitoring and financial records.
Stewardship and treasury receipts complement member payment receipts, with independent review, exact allocation reconciliation and project-bound evidence. These records do not send money.
Guided co-op actions inside Discussion for private mapping, consent, evidence, partner participation, agreements, governance and external receipts, with role-aware choices and retained drafts. Conversation actions.
A single-server Node runtime with durable SQLite and private evidence files, an authenticated gateway, username/password accounts, recovery codes, account export/closure, and revocable device/agent tokens.
Boundary-derived area estimates, overlap screening, reviewed parcel-specific consent, scoped agreement coverage, stale-record detection, and withdrawal/revocation history. Pooling safeguards.
iPhone/iPad source for authenticated member workspaces, member posts, explicit field-draft submission and deliberate photo/PDF/text evidence submission. A protected, account-bound queue retains exact retry requests through interrupted connections. Public discovery and the protected offline journal remain available; signing, device acceptance and Apple distribution are separate release steps.

Exportable imagery jobs and an independent NDVI screening worker, with validated result imports and human review. Worker instructions.

Private versioned GeoJSON boundaries, independent review, explicit external-search consent, Copernicus Sentinel-2 catalogue discovery, and reviewed field observations. See Monitoring.

A member community board with shared events, capacity-aware RSVPs, private calendar downloads, project discussions, and steward moderation.

A guided six-step co-op setup, local organization discovery links, and self-reported organization profiles.
Single-use private invitations with expiry, revocation, and steward approval before record access.
Country/territory and accounting currency settings, correct currency minor units, and hectares/acres/m² intake.
Snapshot-based carbon pathway assessments with methodology references and independent human review.
A worked payout preview before members propose and vote on their policy.
Signed-in, durable co-op workspaces with steward/member roles and membership requests.
Opt-in co-op/project discovery, general-region search, shareable links, updates and moderation.
Projects, assigned conservation actions, completion records, and private parcel/consent intake.
Private agreement submissions with independent review and externally executed instrument references.
Private PDF/image/text uploads, SHA-256 file digests, evidence submissions and independent review; exact upload retries, cancellation, expiry and durable cleanup.
Partner representative invitations, acceptance, own authority evidence, independent co-op review and withdrawal. This grants no extra permissions and does not independently verify an organization.
Coarse capacity warnings and a finite reserve for authorized safety actions; ordinary additions pause before the hard limit.
Versioned allocation-charter proposals with frozen electorates, member votes, quorum, and tallies.
External legal authority, serialized credit holding, settlement, allocation, payment receipt, and retirement records.
Two-person reviews, integer-cent allocations, per-co-op quantity caps, duplicate references, and linked audit history.
Scoped JSON exports, membership removal, member exit, and workspace archival.
The separate hypothetical /coop/ calculator and device-local /demo/ stewardship planner.

What the system does not execute

Verge Common does not form legal co-ops, execute or record deeds, certify ecological measurements, issue or transfer registry credits, initiate sales, send payments, or independently validate bank/registry receipts. Authorized people and external institutions perform those actions. The system stores their supporting records and review decisions.

The cooperative preparation and operational record workflows are implemented; direct registry and payment-provider integrations are not. A reviewed receipt means another steward recorded a review, not that a bank or registry independently authenticated it to the software. See OPERATIONS.md and COOPERATIVE_SYSTEM.md.

Local development

For a local instance of the self-hosted production build, use Node 24.19.0:

npm ci

npm run build:selfhost VERGE_DATA_DIR=/tmp/vergecommon-local-data npm run start:selfhost

Open the printed loopback URL and register a local account. Keep its recovery code privately. The data path is persistent; use a dedicated empty path for synthetic acceptance tests. Follow the operator guide for can

冒頭だけを表示しています。続きはリポジトリで読めます

VergeCommon

概要

PopNx MCPの3つの柱

できること

インストール

インストールの前に

自分で入力する値

できること

基本チェックi

作者とリポジトリが一致

今もメンテナンスされている

ライセンスがある

エンドポイントが応答する

OAuthでサインイン

ツールの説明に隠れた指示がない

その他のほかのサーバーとの比較i

よくある質問

代わりの候補

Spec Driven Development

Remote Desktop Commander

SwarmMemo

作者のREADME

VergeCommon

What if conservation could be an open-source project?

Find your first contribution

Explore the project

Start your own community

Part of the Viridis open commons

Agents and MCP

What is implemented

What the system does not execute

Local development