Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

VergeCommon

by jdhart81version 0.10.1i★ –iRuns in the cloud
Registry nameio.github.jdhart81/vergecommon

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Other
  • You need to fill in: Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 5 things (tools) vergecommon_capabilities, list_public_coops, get_public_coop, example_pooling_draft …
  • You fill in yourself: Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

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

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • Authorization secret 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.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

  • 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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account jdhart81, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 100 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 5 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 18345 servers in this category
  • Published to the registry more recently than 98% of the other 18345 servers in this category
  • Basic checks equal to or better than 100% of the other 18345 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is VergeCommon safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: Authorization

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.10.1) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, ScienceShot science reference

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

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

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

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

Runs in the cloud★ 211Updated 2 days ago
Install

Sourced, citable answers in radiation and particle physics, photonics, electronics and quantum.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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 bringStart here
Local conservation experienceWalk through one activity with synthetic records and report the first confusing step.
Field or research experienceReview the monitoring workflow and identify missing evidence or uncertainty.
Design or accessibility skillsTry the planner with a keyboard or narrow screen; report a reproducible barrier.
Development skillsRun 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.

ProjectWhat it doesWhere
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
VergeCommonLets 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
ViridisOSTurns verified results into recomputable conservation modules and certificates anyone can check. Apache-2.0.viridisos
Viridis ResearchThe 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

Only the beginning is shown; read the rest in the repo

Ask PopNx