Servidor MCP de Vigilnotary

• Nombre en el registrocom.vigilnotary/vigilverificado en el registro MCP

El nombre en el registro está bajo vigilnotary.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-25
• Herramientas26
• El servidor se llamavigil
• Versión del servidor0.1-mvp
• Versión del protocolo2025-06-18

El 2026-10-25 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 174 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 2 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 2 hasta ahora
• Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta534 ms
• Espacio en el contexto del agente≈ 5017 tokenslas definiciones de todas sus herramientas (26), que el agente lleva en cada turno
• Definiciones de herramientasA · 99 de 100
• Resultados tipados1 de 26 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 1 de 26

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• vigil_info

  Service description, the Ed25519 signing pubkey to verify receipts against, current chain head, and free-tier limits. No key required.

• vigil_register

  Create a key. Returns a bearer key shown ONCE — store it; it is your only identity. No email, no account. Starts on the free tier. Creates a persistent identity. The returned key grants full account control; provision it in a trusted…

• vigil_pricing

  The plans and per-tier limits (free, dev, pro). No key required.

• vigil_usage

  Your current tier, its limits, and how much you've used today. Requires your key.

• vigil_notarize

  Notarize work: POST the sha256 (64 hex chars) of anything and get back an Ed25519-signed, timestamped, hash-chained, serial-numbered receipt. Chain position orders submitted records; the timestamp is a signed assertion of Vigil's clock…

• vigil_get_receipt

  Fetch a receipt by serial number. Public — anyone can read any receipt.

• vigil_verify_receipt

  Verify a receipt's hash and Ed25519 signature against a mandatory, independently pinned Ed25519 public key. The key must not come from the receipt being checked. Returns valid=false for tampering, forgery, a wrong signer, or malformed…

• vigil_chain

  Read a range of receipts to audit chain continuity. Max 1000 per call.

• vigil_set_watchdog

  Arm a dead-man switch. Register an interval and an https webhook; then call vigil_heartbeat before each interval elapses. Miss one and Vigil attempts a signed 'absence' payload to your webhook, retrying failed delivery. Free tier: 1…

• vigil_heartbeat

  'Still alive.' Reset a watchdog's timer. Call this at least once per interval. Resets the deadline and delivery state, potentially suppressing an overdue alert or rearming delivery.

• vigil_watchdog_status

  Read a watchdog's state: interval, last beat, whether it is overdue, fired, or exhausted.

• vigil_delete_watchdog

  Remove a watchdog. Destructive: deletes its configuration and stops future alerts. No undo or restoration of the previous timer is provided.

• vigil_grant_lease

  Grant a short-lived, Ed25519-signed LEASE authorizing an agent to perform an action until it expires. A customer-run gateway verifies the lease offline (fail-closed) before letting the action through. This is the guard on a…

• vigil_renew_lease

  Extend a lease with a fresh signed token and new expiry. Renewing is how a healthy agent keeps acting; stop renewing (or revoke) and it lapses. Security-sensitive: extends authority and refreshes the offline recheck window. Keep renewal…

• vigil_revoke_lease

  Revoke a lease. A compliant v2 gateway refuses the old offline token at recheck_by_ms (at most 30 seconds after issue/renewal), or earlier if it polls revocation. Revocation is not instantaneous. Irreversible for this lease ID; it cannot…

• vigil_lease_status

  Public status of a lease (active / expired / revoked). What a gateway polls for revocation. No key required.

• vigil_verify_lease

  Offline, FAIL-CLOSED check of a lease token against a mandatory, independently pinned Ed25519 public key. Returns allow=true only for a valid signature before expiry and recheck_by_ms. It does not authenticate the calling agent, enforce…

• vigil_leases

  List your leases and their states.

• vigil_anchors

  Public timestamp submissions to OpenTimestamps calendars. A submission is pending, not an independently verified Bitcoin confirmation. No key required.

• vigil_anchor

  PRO: anchor the current chain head to OpenTimestamps on demand (the chain is auto-anchored every few hours regardless). Sends the public chain-head digest to external OpenTimestamps calendars; submission is not verified Bitcoin…

• vigil_journal_put

  Store an opaque blob under a slug (overwrites). Encrypt client-side: the server stores exactly the bytes supplied and cannot enforce client encryption. Send bytes as base64. Free tier: 4 slots, 64KB each. Destructive when the slug exists…

• vigil_journal_get

  Fetch a journal blob by slug. Returns base64 (decrypt client-side).

• vigil_journal_list

  List your journal slots (slug, size, last-updated).

• vigil_journal_delete

  Delete a journal slot. Destructive: removes stored bytes with no undo through the API.

• vigil_revoke_key

  Revoke your own key. It stops authenticating immediately. Irreversible. Irreversible: also revokes the account's leases and deletes its watchdogs. Private journal access is lost; public receipts remain. It does not cancel a Stripe…

• vigil_verify_source

  Paid source-local verification with exact evidence and signed receipt. Does not establish absolute truth. Read price and payment requirements before authorizing; settlement spends USDC irreversibly and there is no automatic refund…