Mmcp.market

Vigil — an outside witness for AI agents MCP server

by vigilnotary.com·com.vigilnotary/vigil·v0.1.0

Agent leases, signed receipts, watchdogs, and optional paid source-verification evidence.

C56/100grade C
What users say
No reviews yet
Be the first
Safety scan
C56/100

full report

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Vigil — an outside witness for AI agents yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vigil — an outside witness for AI agents tools (26, 4 write)

write = sends, deletes, buys or posts
  • vigil_anchorFree

    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 confirmation.

  • vigil_anchorsFree

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

  • vigil_chainFree

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

  • vigil_delete_watchdogwrite actionFree

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

  • vigil_get_receiptFree

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

  • vigil_grant_leaseFree

    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 money/data-moving action. Free tier: 1 active lease (guarded agent). Security-sensitive: grants authority. Keep this account key outside the controlled agent. A signed lim string is enforced only by the customer's gateway.

  • vigil_heartbeatFree

    '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_infoFree

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

  • vigil_journal_deletewrite actionFree

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

  • vigil_journal_getFree

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

  • vigil_journal_listFree

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

  • vigil_journal_putwrite actionFree

    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: previous bytes are replaced with no version history or undo.

  • vigil_lease_statusFree

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

  • vigil_leasesFree

    List your leases and their states.

  • vigil_notarizeFree

    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. Free tier: 10/day. Irreversibly publishes the digest, label and account handle in the public chain; no deletion tool exists. It proves signed-data integrity, not that an action happened or a claim is true.

  • vigil_pricingFree

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

  • vigil_registerwrite actionFree

    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 client, not a model transcript.

  • vigil_renew_leaseFree

    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 credentials outside the controlled agent.

  • vigil_revoke_keyFree

    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 subscription.

  • vigil_revoke_leaseFree

    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 be renewed again. Already admitted actions are not undone.

  • vigil_set_watchdogFree

    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 watchdog. Overwrites an existing watchdog and resets its timer and delivery state. A missed heartbeat sends the supplied message to an external HTTPS recipient; failed delivery is capped at five attempts per armed interval.

  • vigil_usageFree

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

  • vigil_verify_leaseFree

    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 action/amount policy, or query live revocation; a customer gateway must do those checks before every provider action. Checks signature, expiry and the signed recheck deadline only. It does not check live revocation, agent identity, action, amount or gateway policy; those checks are mandatory at the gateway.

  • vigil_verify_receiptFree

    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 input. Read-only and local to Vigil.

  • vigil_verify_sourceFree

    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. Identical tool arguments alone are NOT idempotent: retry with the identical arguments, same vigil/idempotency-key metadata and original payment proof.

  • vigil_watchdog_statusFree

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

Public scan report

scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it

1 high1 low
  • Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 2053ms17/20
  • Tool poisoning26 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 4 write-action tools with no auth3/15
  • Maintenanceno repository listed3/15
  • Maintainer identityverified namespace with website, no repo4/10

Findings (2)

  • highWrite-action tools reachable without authenticationauth.open-write
  • lowNo source repository listedmaint.no-repo
Overall 56/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

claude mcp add --transport http vigil https://vigilnotary.com/mcp
Add to Cursor

Vigil — an outside witness for AI agents: common questions

Is Vigil — an outside witness for AI agents MCP server safe?
With care: it is graded C, so read the findings first (56/100). Read the Vigil — an outside witness for AI agents safety report
How do I install Vigil — an outside witness for AI agents?
It runs remotely at vigilnotary.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Vigil — an outside witness for AI agents need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vigil — an outside witness for AI agents maintained?
The latest release is v0.1.0.
Is Vigil — an outside witness for AI agents up?
100% of our last 6 checks got an answer. We check remote servers about four times a day.
What can I use instead of Vigil — an outside witness for AI agents?
Servers from other publishers that do the same job: Protect MCP server, Ausca MCP server and HOL Guard MCP server. Compare all Vigil — an outside witness for AI agents alternatives.

Alternatives to Vigil — an outside witness for AI agents

Same job from other publishers: the closest match first, then the best rated.

All Vigil — an outside witness for AI agents alternatives →
  • Protect
    Fail-closed Cedar policy gate + Ed25519 signed receipts for agent tool calls. Denies on any error.
    C
  • Ausca
    Pay-per-call APIs and MCP services for agents, no accounts or keys, with verifiable receipts.
    B
  • HOL Guard
    Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
    A
  • Watch Skill
    Watch video and live sessions, keep timestamped evidence, and verify an agent's own work.
    B
  • EthersFlow — Trust Gate for AI Agents
    Trust gate for AI agents: multi-model adversarial consensus, signed and verifiable verdicts.
    A

More from vigilnotary.com