P0: agent memory and utilities
REMOTE · X402-BAZAAR-RANK.X402-BAZAAR-RANK-WORKER.WORKERS.DEV
Key-value memory without an account, UUID, hash, JWT, JSON validation, time and random
Available components
Last scanned (15 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2438 tokens (~174/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Tool “random” rewrote its description, which is the text the model reads security
- Tool “time” rewrote its description, which is the text the model reads security
- Tool “util_base64” rewrote its description, which is the text the model reads security
- Tool “util_hash” rewrote its description, which is the text the model reads security
- Tool “util_ip” rewrote its description, which is the text the model reads security
- Tool “util_json_validate” rewrote its description, which is the text the model reads security
- Tool “util_jwt_decode” rewrote its description, which is the text the model reads security
- Tool “util_uuid” rewrote its description, which is the text the model reads security
- Schema quality: 208 → 174 ▲ functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “kv_get” rewrote its description, which is the text the model reads security
- Tool “kv_list” rewrote its description, which is the text the model reads security
- Tool “kv_put” rewrote its description, which is the text the model reads security
- Tool “random” rewrote its description, which is the text the model reads security
- Tool “time” rewrote its description, which is the text the model reads security
- Tool “util_base64” rewrote its description, which is the text the model reads security
- Tool “util_hash” rewrote its description, which is the text the model reads security
- Tool “util_ip” rewrote its description, which is the text the model reads security
- Tool “util_json_validate” rewrote its description, which is the text the model reads security
- Tool “util_jwt_decode” rewrote its description, which is the text the model reads security
- Tool “util_uuid” rewrote its description, which is the text the model reads security
- Tool “x402_echo” rewrote its description, which is the text the model reads security
- Tool “x402_ping” rewrote its description, which is the text the model reads security
- Tool “x402_test_purchase” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402-bazaar-rank-worker.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 8 Nov 2026 | 6 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6c09b073fe5d3fd83fd987465725765b6e5 |
| SANs: *.x402-bazaar-rank-worker.workers.dev, x402-bazaar-rank-worker.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils | Verified | 200 | |
| http (plaintext) | http://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
kv_get KV get ~138
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. Returns the paid x402 request for your input (GET /kv/get, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. A missing or expired key is refused (404) before any charge; to see key names use kv_list.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Key, 1-128 characters from A-Z a-z 0-9 . _ : / - |
No output schema declared.
No examples provided.
kv_list KV list ~148
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 with size, stored_at and expires_at. Returns the paid x402 request for your input (GET /kv/list, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Returns key names with size and times, no values: read one with kv_get.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | cursor from the previous page |
| limit | integer | – | Keys per page |
| prefix | string | – | Only keys starting with this |
No output schema declared.
No examples provided.
kv_put KV put ~236
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 value is stored only if your own client pays that request. Use when an agent needs memory between runs without an account: store value (text or JSON, up to 8 KB) under key in a private namespace keyed to the wallet that pays. POST that JSON body to the URL with an x402 or MPP client to store it. Bad input is refused before any charge. Overwrites an existing key; the key expires after ttl (60 s to 90 days, default 30 days) and there is no delete. Values are stored unencrypted: do not store secrets. Read back with kv_get or kv_list.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Key, 1-128 characters from A-Z a-z 0-9 . _ : / - |
| ttl | integer | – | Seconds to keep the key |
| value | string|object|array|number|boolean | yes | Text, or JSON stored as text (max 8 KB) |
No output schema declared.
No examples provided.
random Random ~221
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 drand (League of Entropy) beacon round with round. Returns the paid x402 request for your input (GET /random, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| choices | string | – | comma-separated items to pick from instead of min/max (up to 100) |
| max | integer | – | largest integer (inclusive) |
| min | integer | – | smallest integer (inclusive) |
| n | integer | – | how many values |
| round | integer | – | a drand quicknet round that has already been published; default latest |
| salt | string | – | your label mixed into the derivation |
| unique | boolean | – | no repeated values (draw without replacement) |
No output schema declared.
No examples provided.
time Time ~234
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/Berlin,Asia/Tokyo). Returns the paid x402 request for your input (GET /time, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| at | string | – | time to convert: ISO 8601 (2026-10-05T09:00, with or without offset) or unix seconds/milliseconds; default now |
| to | string | – | IANA zone(s) to convert at= into, comma-separated, up to 10 |
| tz | string | – | IANA zone(s), comma-separated, up to 10 (e.g. Europe/Berlin,Asia/Tokyo). With at= and no offset in it, the first zone is the zone of that wall time |
No output schema declared.
No examples provided.
util_base64 Util base64 ~170
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 are not UTF-8), up to 64 KB, no external call. Returns the paid x402 request for your input (GET /util/base64, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | encode or decode |
| input | string | yes | Text to encode, or base64 to decode |
| url_safe | boolean | – | Use the url-safe alphabet without padding |
No output schema declared.
No examples provided.
util_hash Util hash ~177
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 to 64 KB), hex digests, no external call. Returns the paid x402 request for your input (GET /util/hash, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| algo | string | – | Comma list of sha256, sha1, sha384, sha512, md5 or all |
| encoding | string | – | How text is encoded |
| text | string | yes | Input to hash |
No output schema declared.
No examples provided.
util_ip Util IP ~105
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 the paid x402 request for your input (GET /util/ip, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
util_json_validate Util JSON validate ~157
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 paid x402 request for your input (GET /util/json-validate, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Returns valid, every violation with its path, and the schema keywords it ignored. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | yes | The document (JSON text; an object in a POST body is accepted too) |
| schema | string | yes | JSON Schema (subset) as JSON text |
No output schema declared.
No examples provided.
util_jwt_decode Util JWT decode ~138
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 now. Returns the paid x402 request for your input (GET /util/jwt-decode, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. Decode only: the signature is not verified. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | JWT header.payload.signature |
No output schema declared.
No examples provided.
util_uuid Util UUID ~132
Use when you need fresh UUIDs: n (1-100) cryptographically random v4 or time-sortable v7 identifiers, no external call. Returns the paid x402 request for your input (GET /util/uuid, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. First call each day returns the data itself, free; later calls return the paid request.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | How many |
| version | integer | – | 4 random, 7 time-sortable |
No output schema declared.
No examples provided.
x402_echo x402 echo ~104
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: the decoded payment payload. Returns the paid x402 request for your input (GET /x402-echo, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_ping x402 ping ~108
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 on Arbitrum) on any network listed in accepts. Returns the paid x402 request for your input (GET /x402-ping, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
x402_test_purchase x402 test purchase ~146
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 tests. Returns the paid x402 request for your input (GET /x402/test, $0.001 per call; schema linked). Call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge.
| Name | Type | Req | Description |
|---|---|---|---|
| dry | boolean | – | dry=1: free list of every accepted rail, nothing charged |
| msg | string | – | Any text; echoed back in echo.query. Any other query parameter or a POST body (hashed) works too |
No output schema declared.
No examples provided.
How do I install the P0: agent memory and utilities MCP server?
P0: agent memory and utilities is a hosted endpoint at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev
claude mcp add --transport http dev-workers-x402-bazaar-rank-worker-x402-bazaar- 'https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils'
What is the P0: agent memory and utilities MCP server?
P0: agent memory and utilities is an MCP server listed in the public MCP registry as dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank/agent…. Key-value memory without an account, UUID, hash, JWT, JSON validation, time and random. This page covers its hosted endpoint (https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/mcp/agent-memory-utils).
Is the P0: agent memory and utilities MCP server safe to use?
P0: agent memory and utilities scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the P0: agent memory and utilities MCP server expose?
P0: agent memory and utilities exposes 14 tools: kv_put, kv_get, kv_list, util_uuid, util_hash, and 9 more. Their descriptions and schemas cost roughly 2,214 tokens of context every time the server is loaded.
Does the P0: agent memory and utilities MCP server require authentication?
No. We connected to P0: agent memory and utilities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the P0: agent memory and utilities MCP server still maintained?
P0: agent memory and utilities is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the P0: agent memory and utilities MCP server?
VerifyMCP ran 13 checks on P0: agent memory and utilities, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.