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

DIEM Agent Workers

de coastmancoastmanversión 0.6.1i★ –iSe ejecuta en la nube
Nombre en el registroio.github.coastmancoastman/diem-agent-workers

Instalar

Resumen

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

Discover privacy-first, bounded Venice-powered micro-work calls with exact x402 USDC prices.

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

Instalación

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

Antes de instalar

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://diem-agent-workers.vercel.app/mcp

Ejecuta esto en tu terminal

claude mcp add --transport http diem-agent-workers https://diem-agent-workers.vercel.app/mcp

Abrir en Cursor

O copia la configuración tú

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

{
  "mcpServers": {
    "diem-agent-workers": {
      "url": "https://diem-agent-workers.vercel.app/mcp"
    }
  }
}

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": {
    "diem-agent-workers": {
      "type": "http",
      "url": "https://diem-agent-workers.vercel.app/mcp"
    }
  }
}

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://diem-agent-workers.vercel.app/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.

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

Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.

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 coastmancoastman, 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

  • … Aún sin revisar

    El endpoint responde

    Aún sin revisar; revisamos los endpoints por turnos

  • … Aún sin revisar

    Inicio de sesión con OAuth

    Aún sin revisar; revisamos los endpoints por turnos

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 18594 servidores de esta categoría
  • Publicado en el registro más recientemente que el 20% de los otros 18594 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 18594 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 DIEM Agent Workers?

Superó 1 de 1 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?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿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.6.1) llegó al registro hace 3 meses.

¿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, Commonly

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

Commonly

Read Commonly pods and post as a Commonly agent you create, with a token from your Commonly account.

de Team-CommonlyEn crecimiento↓ 4,9 mil/semActualizado hoy

Se ejecuta en tu computadora

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.

DIEM Agent Workers

Privacy-first, machine-discoverable micro-work powered by private Venice inference and paid in USDC through x402.

This repository is a fail-closed, agent-first Base mainnet storefront. It exposes six bounded workers over plain HTTP + x402, publishes them to the CDP Bazaar, and adds A2A 1.0, MCP, OpenAPI, llms.txt, and portable-skill discovery surfaces.

Public beta: diem-agent-workers.vercel.app

WorkerBounded outcomeBeta price
extract_text_to_jsonCaller-schema-valid extraction$0.020 USDC
classify_textExactly one caller-supplied label$0.010 USDC
summarize_textStructured abstract and key points$0.020 USDC
text_to_speechUp to 1,000 characters as MP3$0.010 USDC
generate_draft_imageOne safe-mode 1024px WebP$0.020 USDC
transcribe_audioUp to 60 seconds of verified PCM WAV$0.015 USDC

These are fixed prices per successful authorization attempt, not estimates. The public deployment is a low-cap Base mainnet beta: an atomic 0.25 DIEM software budget limits daily inference starts, while the Venice API key retains a separate 1.69 DIEM provider backstop.

Privacy by design

  • Prompts, outputs, payer addresses, transaction hashes, IP addresses, user agents, and request identifiers are excluded from durable metrics.
  • Request and provider bodies are not intentionally logged or persisted.
  • Public reliability statistics are lifetime aggregates only; there are no timestamps or time buckets that could reveal activity patterns.
  • Workers use private Venice models, with web search, scraping, and model tool use disabled.
  • Delivery protection stores only HMAC fingerprints and bounded state needed to redeem an interrupted delivery.

The optional USDC-to-DIEM treasury remains disabled in production and is not part of the storefront runtime. No wallet signer or private key is deployed to Vercel.

What is implemented

  • Three Venice structured-output text workers with post-response JSON Schema validation
  • Bounded Venice speech, image, and transcription workers
  • Native Venice API-key compute ceiling of 1.69 DIEM per EPOCH (daily, resetting at 00:00 UTC)
  • Atomic Upstash-backed software ceiling of 0.25 DIEM of conservatively reserved work per UTC day
  • An environment-backed storefront kill switch checked before payment
  • Input validation before payment, including exact PCM WAV duration checks
  • Pre-payment Venice epoch-access, model-online, private-model, and capability checks
  • Free machine-readable catalog and per-worker fixed-price quotes
  • OpenAPI 3.1, llms.txt, A2A 1.0 Agent Card, JSON-RPC SendMessage, and Streamable HTTP MCP discovery
  • x402 exact-price USDC payment gating through the CDP Facilitator
  • Rich per-worker x402 Bazaar schemas, service name, topical tags, and service icon
  • Official MCP Registry metadata for the public Streamable HTTP server
  • Privacy-preserving runtime telemetry plus durable lifetime aggregate reliability, settlement, revenue, latency-bucket, and DIEM counters
  • Durable, idempotent paid-delivery credits backed by atomic Upstash Redis state
  • Published machine-readable terms linked from every response and discovery surface
  • Payments sent directly to a dedicated treasury address
  • Quote-only and live USDC-to-DIEM treasury modes
  • Hard-coded Base USDC, Venice DIEM, chain ID, and 0x AllowanceHolder
  • Exact approvals, per-swap limits, slippage cap, ETH gas reserve, process lock, and owner-only audit log
  • Installable agent skill and local/stdio MCP adapter

The service is not affiliated with or endorsed by Venice.ai.

Local start

Requirements: Node.js 22+ and pnpm.

cp .env.example .env

pnpm install pnpm test pnpm dev

Add a server-side Venice key to .env:

VENICE_API_KEY=...

VENICE_TEXT_MODEL=venice-uncensored-1-2 VENICE_IMAGE_MODEL=venice-sd35 VENICE_TTS_MODEL=tts-kokoro VENICE_ASR_MODEL=openai/whisper-large-v3 VENICE_DIEM_EPOCH_CAP=1.69

VENICE_DIEM_EPOCH_CAP publishes the cap in service discovery and must match the native EPOCH consumption limit configured on the Venice API key. Venice enforces the hard stop. Before issuing a 402, the service also checks current epoch access and the exact configured model's online/private/capability state; it never estimates DIEM billing from token counts.

The development server binds to 127.0.0.1:8402.

curl http://127.0.0.1:8402/health

curl http://127.0.0.1:8402/v1/catalog curl -X POST http://127.0.0.1:8402/v1/quote/classify_text

With PAYMENTS_MODE=off, the worker is callable without payment for local testing:

curl -X POST http://127.0.0.1:8402/v1/jobs/extract-json \

-H 'Content-Type: application/json' \ -d '{ "source": "The Acme Trail Mug is drinkware and costs $18.50.", "schema": { "type": "object", "properties": { "name": {"type": ["string", "null"]}, "category": {"type": ["string", "null"]}, "price_usd": {"type": ["number", "null"]} }, "required": ["name", "category", "price_usd"], "additionalProperties": false } }'

Production refuses to start unless PAYMENTS_MODE=production, durable delivery credits are enforced, the global compute budget is enforced, and aggregate-only metrics are enabled. The checked-in and local defaults remain PAYMENTS_MODE=off, STOREFRONT_ENABLED=false, AGGREGATE_METRICS_MODE=off, and TREASURY_MODE=disabled.

Add x402 payments

Import a downloaded CDP Secret API Key without printing its values:

pnpm credentials:import-cdp /absolute/path/to/cdp_api_key.json

The command tightens both the downloaded key file and .env to owner-only permissions. It refuses to overwrite configured credentials and does not enable payments.

Start on Base Sepolia:

PAYMENTS_MODE=development

TREASURY_ADDRESS=0xYourDedicatedEvmAddress CDP_API_KEY_ID=... CDP_API_KEY_SECRET=...

The server uses the address form of the CDP configuration, so payments settle directly to TREASURY_ADDRESS; CDP does not provision or control that wallet. An unpaid request to the worker should return HTTP 402 and a PAYMENT-REQUIRED header.

Paid-delivery protection

Mainnet is fail-closed unless durable delivery credits are enforced. Provision an Upstash Redis database through the Vercel Marketplace, then configure:

DELIVERY_CREDITS_MODE=enforced

DELIVERY_CREDIT_HMAC_SECRET= DELIVERY_CREDIT_TTL_SECONDS=86400 DELIVERY_CREDIT_LEASE_SECONDS=180 UPSTASH_REDIS_REST_URL=... UPSTASH_REDIS_REST_TOKEN=...

Agents should generate one unpredictable Idempotency-Key per logical job and reuse it only with the identical request and payment authorization. Signed paid attempts without the header fail before settlement. The Redis record contains only HMAC fingerprints, worker ID, state, lease, and expiry—never request bodies, provider responses, payer addresses, payment headers, or transaction hashes.

Normal successful delivery consumes the key. If the process is interrupted after settlement but before delivery completes, the same authorization, key, worker, and request may redeem one retry without another settlement. Conflicting reuse is rejected, and storage outages return 503 before settlement.

Mainnet compute budget and kill switch

Production also requires an atomic global compute budget:

COMPUTE_BUDGET_MODE=enforced

COMPUTE_BUDGET_DIEM_PER_DAY=0.25 AGGREGATE_METRICS_MODE=enabled STOREFRONT_ENABLED=true

The service reserves a conservative amount equal to the job's USDC price after x402 verification but before Venice inference. Delivery retries reserve again because they can consume provider capacity even when the buyer is not charged again. A Redis outage or exhausted budget aborts new payment settlement and blocks inference. Set STOREFRONT_ENABLED=false and redeploy to disable all paid work before payment.

Run the guarded local Base Sepolia settlement test with:

pnpm test:sepolia

This is an actual testnet transaction: it creates an ephemeral in-memory buyer, requests faucet USDC, validates the exact quote before signing, pays one worker call, and reconciles the treasury's test-USDC increase. It refuses to run unless the saved PAYMENTS_MODE is off and TREASURY_MODE is disabled. Local HTTP tests are not published to Bazaar; a public HTTPS deployment is required.

Mainnet launch checklist:

  1. Use a dedicated, low-balance treasury wallet—not a personal wallet.
  2. Verify the address and Base network.
  3. Deploy behind public HTTPS.
  4. Validate the x402 endpoint with the CDP validation API.
  5. Publish and review TERMS.md; every API response links to /terms.
  6. Enable durable delivery credits and the 0.25 DIEM atomic software budget.
  7. Set PAYMENTS_MODE=production, keep TREASURY_MODE=disabled, and deploy.
  8. Complete one real low-value payment so Bazaar can index the Base mainnet resource.

The mainnet acceptance harness uses a distinct cents-only buyer kept in macOS Keychain, verifies every payment requirement before signing, and refuses a combined storefront authorization above $0.095 USDC. Select individual workers with MAINNET_X402_TEST_WORKERS or use pnpm test:mainnet:all; multi-worker runs require the exact acknowledgement PAY_UP_TO_0_095_USDC_WITH_DISTINCT_BUYER_ON_BASE. Its output deliberately omits wallet addresses, transaction hashes, request bodies, and provider responses.

Reinvest USDC into DIEM

The treasury is a deterministic one-shot runner, not a prompt-driven wallet agent.

Create a new dedicated wallet on macOS with:

pnpm wallet:create

The command stores the private key in macOS Keychain and writes only the public address and Keychain labels to .env. It refuses to replace an existing wallet and requires payments and treasury execution to be disabled.

For seed-phrase recovery, create a dedicated wallet in a trusted wallet app, keep its seed phrase offline, export only its treasury account private key, and import that key through a hidden local prompt:

pnpm wallet:import

Never enter the seed phrase into the project. The import command displays the derived public address for confirmation, stores the account key in macOS Keychain, and replaces the previous disabled treasury configuration only after Keychain readback succeeds.

Verify ownership and read Base balances without revealing the key:

pnpm wallet:verify

See docs/WALLET_ACCESS.md for the macOS-authenticated recovery and wallet-import path. Never send a private key through chat; if you already control a wallet, share only its public 0x address.

Quote-only mode reads balances and requests an indicative 0x price, but never signs:

TREASURY_MODE=quote

TREASURY_ADDRESS=0xYourDedicatedEvmAddress BASE_RPC_URL=https://your-base-rpc.example ZEROX_API_KEY=... TREASURY_MIN_SWAP_USDC=5 TREASURY_MAX_SWAP_USDC=25 TREASURY_USDC_HOLDBACK=0 TREASURY_MAX_SLIPPAGE_BPS=100 TREASURY_MIN_ETH_RESERVE=0.0005

pnpm treasury:run

Live mode additionally requires the matching dedicated key from macOS Keychain (or a production secret manager) and an exact acknowledgement:

TREASURY_MODE=live

TREASURY_LIVE_ACK=BUY_DIEM_ONLY_ON_BASE

Use a production secret manager rather than a plaintext .env when deployed. The live runner:

  • Refuses a key that does not match TREASURY_ADDRESS
  • Refuses the wrong token pair, chain, allowance target, native value, or excess gas
  • Approves only the intended USDC amount
  • Refreshes the firm quote after approval
  • Records the signed transaction hash before broadcast and reconciles it after a restart
  • Verifies that USDC decreased by no more than the authorized amount and DIEM increased
  • Writes 0600 JSONL audit records under data/

The runner does not sell DIEM, withdraw USDC, bridge assets, select

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

Pregunta a PopNx