Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/veritap-dev/veritap-lockerWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/veritap-dev/veritap-locker/agent-memory)<a href="https://agentmods.dev/mcp/veritap-dev/veritap-locker/agent-memory"><img src="https://agentmods.dev/badge/mcp/veritap-dev/veritap-locker/agent-memory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/veritap-dev/veritap-locker/agent-memory"><img src="https://agentmods.dev/badge/mcp/veritap-dev/veritap-locker/agent-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-memory scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"agent-memory": {
"url": "https://locker.veritap.dev/mcp/memory",
"type": "streamable-http"
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 6 lines scan A 2a396a764b81
agent-memory is an MCP server published in the GitHub repository veritap-dev/veritap-locker (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
context
MCP server "context", hosted remotely at mcp.context.lc, as configured in Supa-Media/context.
agent402
Agent402 MCP server: 500+ pay-per-call tools + skill packs for AI agents over x402 (USDC on 12 chains) or MPP on the same 402, or free via proof-of-work - the applied layer of Agentic Finance. Catalog: browser, web search + cited answers, PDFs, OCR, image. Runs locally from the agent402-mcp npm package.
gateway
Durable self for AI agents: one-call resume, memory, real browser, free chat + hire real humans. Remote server at agent.wingmanprotocol.com.
thebuyside-x402-agent
Buyer-side MCP gateway for x402 and MPP (pay.sh) — let any agent pay any metered API on Base or Solana without seeing a 402 or a wallet. Runs locally from the thebuyside-x402-agent npm package.
x402-cloudflare-starter
Model Context Protocol implementation for TypeScript. Runs locally from the @modelcontextprotocol/sdk npm package.
china-bank-offers-facts
MCP server "china-bank-offers-facts", hosted remotely at agent-offers-api-replitzip.replit.app, as configured in badDevBuild/china-bank-offers-facts.