Categories › AI & Agents › Agent memory & context
Key-value memory without an account, UUID, hash, JWT, JSON validation, time and random
Remote server: your requests and data go to x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. Claude Code: claude mcp add --transport http p0-agent-memory-and-utilities https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
kv_put — Returns the paid x402 request that would store your value (POST /kv/put, $0.001 per call; schema linked); this call stores nothing, and a vakv_get — Use when an agent needs a value it stored earlier with /kv/put: returns the text (and parsed json when it was stored as JSON), size. Returnskv_list — Use when an agent needs to see what it has stored: lists up to 100 keys (optionally under prefix) in the namespace of the paying wallet withutil_uuid — Use when you need fresh UUIDs: n (1-100) cryptographically random v4 or time-sortable v7 identifiers, no external call. Returns the paid x40util_hash — Use when you need a checksum or digest of a string: sha256 (default), sha1, sha384, sha512 and md5 of text given as utf8, hex or base64 (up util_ip — Use when an agent needs to know how it is seen from outside: its public IP plus the country, region, city, ASN, AS organization. Returns theutil_jwt_decode — Use when you need to inspect a JWT without a key: decoded header and payload, alg, kid, iat/nbf/exp as ISO times and whether it is expired nutil_json_validate — Use when you need to check that a JSON document fits a schema before acting on it: validates json against a JSON Schema subset. Returns the util_base64 — Use when you need base64 in or out: encode UTF-8 text to base64 (standard or url_safe) or decode base64 back to text (hex when the bytes aretime — Use when you need the current UTC time from a server clock, the local time, UTC offset and DST flag in up to 10 IANA time zones (tz=Europe/Brandom — Use when you need publicly verifiable random numbers: n integers in [min,max], a pick from choices=a,b,c or a unique draw, derived from a drx402_test_purchase — Use when you test an x402 or MPP client, wallet, SDK, facilitator or CI: a test target for x402/MPP clients, use it in your integration testx402_ping — Use for testing that your x402 client can pay and settle a real payment end to end at the smallest useful price: $0.001 in USDC (or USDT0 onx402_echo — Use for debugging an x402 client: pay $0.001 in USDC (or USDT0 on Arbitrum) on any network in accepts and get back what the server received:Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.