
Vigilnotary MCP server
Which servers in the official MCP registry are Vigilnotary's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry namecom.vigilnotary/vigilverified in the MCP registry
The registry name sits under vigilnotary.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools26
- Server calls itselfvigil
- Server version0.1-mvp
- Protocol version2025-06-18
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 174 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 2 of the 7 days it takes to judge reliability.
Once connected
- vigil_set_watchdog, vigil_delete_watchdog change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer534 ms
- Space in an agent's context≈ 5,017 tokensthe definitions of all its tools (26), which an agent carries on every turn
- Tool definitionsA · 99 of 100
- Typed results1 of 26 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 26
Worth a look
- Tools that change data, on a server that answers without a sign-in: vigil_set_watchdog, vigil_delete_watchdog
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
vigil_infoService description, the Ed25519 signing pubkey to verify receipts against, current chain head, and free-tier limits. No key required.
vigil_registerCreate 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_pricingThe plans and per-tier limits (free, dev, pro). No key required.
vigil_usageYour current tier, its limits, and how much you've used today. Requires your key.
vigil_notarizeNotarize 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_receiptFetch a receipt by serial number. Public — anyone can read any receipt.
vigil_verify_receiptVerify 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_chainRead a range of receipts to audit chain continuity. Max 1000 per call.
vigil_set_watchdogArm 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_statusRead a watchdog's state: interval, last beat, whether it is overdue, fired, or exhausted.
vigil_delete_watchdogRemove a watchdog. Destructive: deletes its configuration and stops future alerts. No undo or restoration of the previous timer is provided.
vigil_grant_leaseGrant 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_leaseExtend 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_leaseRevoke 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_statusPublic status of a lease (active / expired / revoked). What a gateway polls for revocation. No key required.
vigil_verify_leaseOffline, 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_leasesList your leases and their states.
vigil_anchorsPublic timestamp submissions to OpenTimestamps calendars. A submission is pending, not an independently verified Bitcoin confirmation. No key required.
vigil_anchorPRO: 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_putStore 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_getFetch a journal blob by slug. Returns base64 (decrypt client-side).
vigil_journal_listList your journal slots (slug, size, last-updated).
vigil_journal_deleteDelete a journal slot. Destructive: removes stored bytes with no undo through the API.
vigil_revoke_keyRevoke 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_sourcePaid 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"vigil": {
"type": "http",
"url": "https://vigilnotary.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http vigilnotary https://vigilnotary.com/mcpclaude.ai, ChatGPT and other clients: add https://vigilnotary.com/mcp as a custom connector in the settings.
OpenAPI spec
3 paths, read 2026-10-25. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.