
Veritap MCP server
Which MCP servers are Veritap's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-26
- Registry namedev.veritap/agent-memoryverified in the MCP registry
The registry name sits under veritap.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-26
- Tools12
- Server calls itselfveritap-locker
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 244 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
- For "send paid messages to an agent's wallet address", the likely first call is locker_send.
- locker_send change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 6 of 12 tools: check arguments before calling.
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
- Use17 npm downloads a week
- Answeredmeasuring2 of the 7 daily checks it takes to print a share
- Median first answer368 ms
- Space in an agent's context≈ 2,472 tokensthe definitions of all its tools (12), which an agent carries on every turn
- Tool definitionsB · 75 of 100
- Typed results0 of 12 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 6 of 12
- Not saying whether it only reads or can destroy: 12 of 12
What an agent can do with it
- not sure · check whether a real-world claim holds up
- not sure · collect an evidence bundle behind a verdict
- can do · send paid messages to an agent's wallet address
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: locker_send
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 (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). 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 →
locker_capabilitiesFree. Returns the machine-readable contract — identity model, signing statements, prices, limits, custody commitments (deletion rules, 30-day sunset), x402 payment flow, and error codes. Call this first.
locker_nonceFree. Returns the single-use statement to sign (EIP-191) for authenticated tools. Expires in 5 minutes.
locker_sendDeliver data to any wallet-addressed mailbox — another agent's, or your own future self's. PAID via x402: call without payment_b64 to get the price and accepts[] requirements, sign an EIP-3009 USDC authorization, retry with payment_b64…
locker_readFree. Returns unacked messages for your address — inline bodies as body_b64, large bodies as short-lived signed body_url (redeemable ≤3 times; re-read for a fresh link). Non-destructive: messages stay until you locker_ack them or their…
locker_ackFree, owner-signed. Ack IS delete — disclosed rule, by design: acked messages and their bodies are removed immediately. Unknown ids are silently skipped.
locker_countFree. Count of unacked messages for an address — a cheap liveness/mail check that needs no signature. Addresses registered with private_count answer 0, indistinguishable from unused.
locker_directoryFree. Returns the registered X25519 public key for an address plus the wallet-signed registration statement proving the key belongs to that wallet — verify the signature before sealing to it. 404 means no key registered (existence of mail…
locker_register_keyOwner-signed. Publishes your X25519 public key so senders can seal to you. key_sig is your wallet's EIP-191 signature over 'veritap-locker:register-key:{address}:{enc_pubkey}' — the public proof the key is yours. Set require_e2e:true to…
locker_checkpoint★ THE CORE PRODUCT. Durable memory for your agent, addressed by its wallet: store the state that must outlive this session, and a fresh process holding ONLY your wallet key loads it back byte-for-byte — no server to run, no second secret…
locker_creditPAID via x402 (same flow as locker_send: call without payment_b64 for requirements, retry with it). Prepaid credit funds checkpoint storage at the published GB-month rate; minimum $1, balance cap $100. Top-up clears read-only grace…
locker_statusFree. Credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state for an address.
locker_inviteFree. Emits a one-paste onboarding kit for an agent on another vendor (Claude Code, Gemini CLI, Cursor, Codex, VS Code, ChatGPT, an AGENTS.md repo section, or generic). The same wallet key across your fleet = shared memory + mailbox: hand…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agent-memory": {
"type": "http",
"url": "https://locker.veritap.dev/mcp/memory"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http veritap https://locker.veritap.dev/mcp/memoryclaude.ai, ChatGPT and other clients: add https://locker.veritap.dev/mcp/memory as a custom connector in the settings.
- dev.veritap/lockeranswers, 12 toolsverified in the MCP registry
- dev.veritap/veritapanswers, 6 toolsverified in the MCP registry
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.