Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas
Modo principiante Activado
ColoresSistemaClaroOscuro
IdiomaไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenúAjustes
Modo principiante Activado
ColoresSistemaClaroOscuro
IdiomaไทยEnglish中文日本語한국어EspañolDeutsch

VergeCommon

de jdhart81versión 0.10.1i★ –iSe ejecuta en la nube
Nombre en el registroio.github.jdhart81/vergecommon

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en la nube
  • Transporte: Streamable HTTP
  • Categoría: Otros
  • Debes completar: Authorization

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Ejecuta esto en tu terminal

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

Completa los valores vacíos antes de ejecutarlo.

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Esta dirección necesita una clave en un header de la solicitud, y el menú para agregar conectores no puede ponerla. Usa Claude Code, Cursor o VS Code.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

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

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 7 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

  • 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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub jdhart81, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • ✓ Superada

    El endpoint responde

    Respondió en 100 ms (HTTP 200)

  • – No aplica

    Inicio de sesión con OAuth

    No hace falta iniciar sesión

  • ✓ Superada

    Sin instrucciones ocultas en las descripciones de herramientas

    Leímos 5 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 32708 servidores de esta categoría
  • Publicado en el registro más recientemente que el 100% de los otros 32708 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 32708 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro VergeCommon?

Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: Authorization

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.10.1) llegó al registro hoy.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, OpenTakeoff

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

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

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar

Remote Desktop Commander

de desktop-commander

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

Se ejecuta en la nube★ 211Actualizado anteayer
Instalar

OpenTakeoff

de Kentucky-ai

Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.

Se ejecuta en tu computadoraActualizado hoy
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

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

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx