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

POPCORN MCP

de violetclaireversión 0.1.6i★ –iComputadora o nube
Nombre en el registroio.github.violetclaire/popcorn-mcp

Instalar

Resumen

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

Witness layer for agents: signed receipts binding a fingerprint to a witnessed time. $0.001.

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: Computadora o nube
  • Transporte: stdio, Streamable HTTP
  • Categoría: Otros
  • Debes completar: EVM_PRIVATE_KEY

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 …”.

Funciona en Claude para web, escritorio y móvil:

  1. Abre Settings → Connectors
  2. Presiona Add custom connector
  3. Pega la dirección de abajo y presiona Add
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Add2https://…3
https://767-2676.com/mcp

O ejecútalo en tu computadora

Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json

{
  "mcpServers": {
    "popcorn": {
      "command": "npx",
      "args": [
        "-y",
        "@violetclaire/popcorn-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "your-value"
      }
    }
  }
}

Ejecuta esto en tu terminal

claude mcp add --transport http popcorn https://767-2676.com/mcp

O ejecútalo en tu computadora

claude mcp add popcorn --env EVM_PRIVATE_KEY=your-value -- npx -y @violetclaire/popcorn-mcp

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": {
    "popcorn": {
      "url": "https://767-2676.com/mcp"
    }
  }
}

O ejecútalo en tu computadora

Abrir en Cursor

O copia la configuración tú

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

{
  "mcpServers": {
    "popcorn": {
      "command": "npx",
      "args": [
        "-y",
        "@violetclaire/popcorn-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "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": {
    "popcorn": {
      "type": "http",
      "url": "https://767-2676.com/mcp"
    }
  }
}

O ejecútalo en tu computadora

Abrir en VS Code

O copia la configuración tú

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

{
  "servers": {
    "popcorn": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@violetclaire/popcorn-mcp"
      ],
      "env": {
        "EVM_PRIVATE_KEY": "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ú.

ChatGPT solo se conecta a servidores en internet:

  1. Abre ChatGPT en la web → Settings → Connectors (Apps)
  2. Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
  3. Pega la dirección de abajo, ponle un nombre y guarda
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Create2https://…3
https://767-2676.com/mcp

Los nombres de los menús pueden variar un poco según el plan y con el tiempo.

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

Valores que debes completar

  • EVM_PRIVATE_KEY secreto env
    Optional dedicated Base payer key. Required only for a paid tool call that explicitly sets approve_payment to true.

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.

  • popcorn_sample

    Check the public October 14 TAIN 2.0 receipt and a changed-digest control. No inputs, wallet, payment, or outbound request. Historical evidence, not a fresh clock. Bundled sample keys do not independently establish issuer identity.

  • popcorn_catalog

    Read the live catalog, offer, and published verification keys. Free; no payment.

  • popcorn_hash

    Hash public bytes on this remote server. Submitted text reaches the server: hash private work locally instead. Free; no onward request or payment.

  • popcorn_verify

    Verify a time or witness receipt using caller-trusted JWKS and expected values. Digest-only for witness payloads. No outbound request or payment. Caller keys do not establish issuer identity; a signature grants no authority.

  • popcorn_verify_v2

    Verify TAIN 2.0 evidence against keys fetched from the fixed POPCORN issuer URL. Caller jwks is replaced with published keys, including predecessors. Send a digest, never private work. Free; does not grant authority, establish current time, or verify settlement on chain.

  • popcorn_time

    Request signed current-time evidence. Defaults to a free unpaid 402 challenge. A fresh receipt costs exactly $0.001 USDC on Base. Payment requires owner approval, approve_payment:true, and a caller-signed payment_signature. No server wallet or private key. No automatic retry. Ver

  • popcorn_witness

    Witness a SHA-256 digest and fresh caller nonce at a time. Defaults to a free unpaid 402 challenge. One fresh receipt costs exactly $0.001 USDC on Base; requires owner approval, approve_payment:true, and caller-signed payment_signature. Keep work and wallet keys local. No automat

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 8 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub violetclaire, 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 244 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 7 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 18474 servidores de esta categoría
  • Publicado en el registro más recientemente que el 76% de los otros 18474 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 18474 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 POPCORN MCP?

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: EVM_PRIVATE_KEY

¿Se ejecuta en mi computadora o en la nube?

Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.1.6) llegó al registro hace 12 días.

¿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, Brontide agent arena

Alternativas

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

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

Spec Driven Development

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

de formulahendryInicial↓ 66/sem★ 440Actualizado hace 14 meses

Se ejecuta en tu computadora

Remote Desktop Commander

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

de desktop-commanderEn crecimiento★ 211Actualizado hace 3 días

Se ejecuta en la nube✓ desktopcommander.app

Brontide agent arena

THE MECH ARENA BUILT FOR AI AGENTS. HUMANS WELCOME. Pilot mech duels over MCP, free, no sign-in.

de beeswaxpatMuy nuevoActualizado hoy

Se ejecuta en la nube✓ brontide.live

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.

Briarwood AI / POPCORN MCP server

For RFC 3161, FreeTSA, OpenTimestamps, a trusted timestamp, proof of existence, authorization expiry, a signed execution receipt, or independent verification, start with Proving an action happened before an authorization expired.

Read-only time and task evidence from Briarwood AI, usable across independent agents. POPCORN supplies signed time and digest checkpoints at https://767-2676.com.

Try it first, without a wallet

At the hosted HTTP MCP endpoint, call popcorn_sample with {}. This free check verifies a real historical TAIN 2.0 receipt dated October 14, 2026: genuine.accepted: true, changed_digest_control.accepted: false, and passed: true. It requires no wallet and returns payment_sent: false, current_time_established: false, and authorization_granted: false. It does not independently establish issuer-key trust or check on-chain settlement.

The bundled npm sample below is a separate offline evaluation of historical pre-TAIN receipts.

Save sample.mjs, read it, then run node sample.mjs with Node.js 20 or newer. This standalone sample includes an exact eight-line schedule with who, its SHA-256 digest, and a real signed receipt. It runs offline and rejects a one-byte change to who.

The plain-text contract and full packet can be retained locally. The receipt is historical evidence. Fetch new time for a new decision.

Run the current source from this public repository:

git clone https://github.com/violetclaire/popcorn-temporal-anchor.git

cd popcorn-temporal-anchor/packages/mcp npm ci npm run build node dist/packages/mcp/src/index.js --sample

Run this release's bundled offline sample with:

npx -y @violetclaire/popcorn-mcp@0.1.5 --sample

The evaluation checks the eight-line task schedule and two legacy, historically settled receipts with the maintained verifier. It returns valid signatures, STOP for a checkpoint after its task window, TIME_CHECK_PASSED for one inside its window, and a rejected one-byte change for each. Every result retains authorization_granted: false. The sample needs no account, wallet, or original task data. npm may download the package; the verification itself runs entirely offline.

With the npm package or this source checkout running as a local stdio MCP server, call popcorn_sample with {} for this bundled historical result. The hosted HTTP MCP endpoint runs the separate TAIN 2.0 sample described above. The bundled sample's public source links let another developer repeat the check. Its historical keys are for sample reproduction. A real task requires independently trusted issuer keys; an old receipt is not a fresh clock reading. This bundled offline sample tests historical pre-TAIN receipts only. Passing it does not test the currently deployed TAIN 2.0 service or establish integration readiness.

Use it for a real task

NeedToolWhat stays local
A fresh, signed time reference for a deadline or expirypopcorn_timeThe task and decision
Evidence of one exact task version at a stated timepopcorn_hash, then popcorn_witnessRaw task bytes; only the digest, nonce, and optional predecessor digest go to the witness
Check evidence received from another agentpopcorn_verifyThe receipt, trusted keys, payload, and verification
Check a TAIN 2.0 witness receiptpopcorn_verify_v2 or local CLI verify-v2Exact expected bytes and independently trusted keys

These uses apply across agent providers and industries. Share a receipt and the relevant exact bytes through your existing authorized handoff, then let the receiving system verify them. No account at the originating agent provider is required for offline verification. Each participant decides what to do.

This source checkout exposes five free tools and two x402 tools. The x402 tools are dry run by default. They cannot spend unless the individual tool call contains approve_payment: true. A wallet key is read only from EVM_PRIVATE_KEY in the server process environment. It is never accepted as a tool parameter.

This is a clock and a seal. It does not refund, authorize, or hold funds.

Run with npx

Install and run the published package with:

npx -y @violetclaire/popcorn-mcp

Node.js 20 or newer is required.

Programmatic core

The supported @violetclaire/popcorn-mcp/core export exposes the same local hashing, offline verification, and paid client functions used by the stdio server:

import {

popcornHash, popcornVerifyWitnessChain, popcornWitness, } from "@violetclaire/popcorn-mcp/core";

popcornVerifyWitnessChain accepts receipts in chronological order, starting with a receipt whose previous_attestation_digest is null. It verifies each receipt and signature once, checks each link against the prior receipt's exact signed-payload bytes, and returns the verified entries plus the head digest. It is free, local, and sends no network request.

Tools

popcorn_sample

Input: {}. The result depends on which server you connect to:

  • Hosted HTTP MCP at `https://767-2676.com/mcp`: verifies the historical October 14, 2026 TAIN 2.0 receipt and rejects the changed-digest control. It sends no payment and establishes neither current time nor authorization.
  • Local stdio MCP from npm 0.1.5 or this source checkout: checks the bundled eight-line schedule, two historical pre-TAIN receipt examples, and their tamper controls. It makes no network request or payment. These historical receipts are not a TAIN 2.0 conformance test.
popcorn_verify_v2

Verifies a POPCORN-WITNESS/2.0 signed envelope, required TAIN fields, exact expected payload digest and nonce, and the signed time interval. Both this local MCP tool and popcorn-mcp verify-v2 call the same verifier. The fixed positive and negative vectors under verify/test-vectors/interface-parity-v2/ run through both interfaces in npm run check and fail the check on any result or reason mismatch.

Provide the full response, expected SHA-256 payload digest as canonical unpadded base64url, the expected nonce, and issuer keys obtained independently of the receipt. The local CLI and stdio MCP also accept exact payload bytes as expected_payload_base64url instead of a digest; the remote HTTP MCP accepts only a digest, including for predecessor receipts, so private payload bytes need not leave the caller. Supply previous_receipt with its own response, JWKS, and verification inputs for a chained receipt, up to eight links. Caller-supplied keys alone do not establish issuer identity; this verifier does not prove on-chain settlement or grant authority.

popcorn_catalog

Fetches the live service catalog, published JWKS, and public schemas. It is free and sends no payment.

Input:

{}
popcorn_hash

Hashes exact bytes locally and returns the SHA-256 digest plus byte length. It is free, local, and sends no network request.

Provide exactly one input form:

{ "payload_text": "exact UTF-8 text" }
{ "payload_base64url": "ZXhhY3QgYnl0ZXM" }
popcorn_verify

Verifies a POPCORN temporal or witness receipt locally against caller-supplied keys and expected values. It is free, local, and sends no payment.

For a witness receipt:

{

"receipt_type": "witness", "response": { "witness_receipt": {}, "witness_attestation": {}, "payment_status": "settled" }, "jwks": { "keys": [] }, "verification": { "expected_nonce": "<43-character-base64url>", "expected_payload_base64url": " ", "expected_node_id": "767-2676.com", "max_clock_accuracy_radius_ms": 10000 } }

Provide exactly one of expected_payload_text, expected_payload_base64url, or expected_payload_digest.

When previous_attestation_digest is non-null, add this recursively under verification:

{

"previous_receipt": { "response": { "witness_receipt": {}, "witness_attestation": {}, "payment_status": "settled" }, "jwks": { "keys": [] }, "verification": { "expected_nonce": " ", "expected_payload_digest": " " } } }

The verifier first verifies the predecessor. It then hashes the exact bytes obtained by base64url-decoding the predecessor compact JWS payload segment and compares that digest with previous_attestation_digest.

For a temporal receipt, verification.observation carries the monotonic timer values required by the existing offline verifier. An optional verification.policy can carry execution_window_utc.

popcorn_time

Requests GET /v1/time. The default call is a free dry run:

{

"freshness_ms": 30000, "approve_payment": false }

It returns the HTTP 402 terms and the exact request that would be paid. To authorize one payment, the caller must set approve_payment to true in that specific call.

popcorn_witness

Requests POST /v2/receipt. POST /v1/receipt remains available to existing integrations. The default call is a free dry run:

{

"digest": "<43-character-sha256-base64url>", "nonce": "<43-character-random-base64url>", "previous_attestation_digest": null, "approve_payment": false }

The optional predecessor digest is SHA-256 over the exact decoded signed payload bytes of the predecessor compact JWS. It is not a digest of the full compact JWS string.

Both paid tools lock payment to exactly $0.001 USDC on Base, the published USDC contract, and POPCORN's published payTo. A changed challenge fails closed. A successful paid result includes the settlement transaction hash and server_processing_duration_ms.

Wallet environment

Paid calls require:

EVM_PRIVATE_KEY=0x<dedicated-32-byte-Base-payer-key>

Use a dedicated payer with a small balance. Do not commit this value. The free tools and all dry runs work without it.

Claude Desktop

Add this server to the mcpServers object in Claude Desktop's configuration:

{

"mcpServers": { "popcorn": { "command": "npx", "args": ["-y", "@violetclaire/popcorn-mcp"] } } }

That configuration supports all free tools and dry runs. For paid calls, launch Claude Desktop from an environment containing EVM_PRIVATE_KEY, or add an env object to its private local configuration. Never paste the key into a tool call or chat.

Claude Code

claude mcp add --transport stdio popcorn -- npx -y @violetclaire/popcorn-mcp

Set EVM_PRIVATE_KEY in the environment that launches Claude Code only when paid calls are needed. Every paid call still requires approve_payment: true.

Local development

From packages/mcp:

npm install

npm run check npm start

The package build includes the repository's existing TypeScript verifier in the published files. Runtime dependencies remain normal npm dependencies.

Pregunta a PopNx