Servidor MCP de Vigilnotary

• Nome no registrocom.vigilnotary/vigilverificado no registro MCP

O nome no registro fica sob vigilnotary.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-25
• Ferramentas26
• O servidor se chamavigil
• Versão do servidor0.1-mvp
• Versão do protocolo2025-06-18

Em 2026-10-25 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 174 ms.

• Ainda não avaliamos se as ferramentas fazem o trabalho do produto.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta534 ms
• Espaço no contexto do agente≈ 5.017 tokensas definições de todas as ferramentas (26), que o agente carrega a cada turno
• Definições das ferramentasA · 99 de 100
• Resultados tipados1 de 26 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 1 de 26

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e 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…