io.github.agtrepo/agtrepo-memory
REMOTE · AGTREPO.COM
Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.
Available components
Last scanned (9 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 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
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 541 tokens (~90/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 15% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_feedback" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 1 Nov 26 +1
- Stability: fail → pass ▲ security
- 9 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 90.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 83.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77.
- 3 Oct 26 72
- Tool “send_feedback” rewrote its description, which is the text the model reads security
- Schema quality: 76 → 90 ▼ functional
- 2 Oct 26 0
- Stability: 0.77 → fail ▼ security
- HSTS header: fail → pass ▲ security
- Tool “extend_memory” rewrote its description, which is the text the model reads security
- Tool “register_key_release” rewrote its description, which is the text the model reads security
- Tool “send_feedback” rewrote its description, which is the text the model reads security
- Tool “store_persistent_memory” rewrote its description, which is the text the model reads security
- Schema quality: 55 → 76 ▼ functional
- “register_key_release” changed the type of “timestamp”: number → integer ▼ functional
- Tool coverage: 8% → 15% ▲ functional
- Server version: 0.1.0 → 0.2.0 functional
- “register_key_release” reworded the description of “timestamp” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://agtrepo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agtrepo.com | CN=WE1,O=Google Trust Services,C=US | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 57a9d5d6b143599b0e468f82ab69655a |
| SANs: agtrepo.com, *.agtrepo.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agtrepo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agtrepo.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agtrepo.com/mcp | Verified | 200 | |
| http (plaintext) | http://agtrepo.com/mcp | HTTPS enforced | 301 | https://agtrepo.com/mcp |
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 →
extend_memory ~54
Extends a memory's TTL by 30 days, up to a maximum total lifetime of 365 days from creation. Requires x402 payment. An expired memory is deleted and cannot be extended.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
read_memory ~41
Reads an encrypted memory by id. Requires x402 payment. 70% of the fee accrues to the memory's creator.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
register_key_release ~201
Free. Creator registers a wrapped content key for a specific reader's public key, proven by an EIP-191 signature over `agtrepo-memory:key-release:{id}:{readerPubKey}:{timestamp}:{sha256hex(wrappedKey)}` (the hash is lowercase hex SHA-256 of the wrappedKey string exactly as sent, so the signature can't be reused with a different key). `{id}` only exists after store_persistent_memory returns, and `{timestamp}` is Unix epoch milliseconds (an integer, not an ISO date) that must be within 5 minutes of the server clock -- so sign at call time; a pre-signed or archived signature will be rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| readerPubKey | string | yes | – |
| signature | string | yes | – |
| timestamp | integer | yes | Unix epoch milliseconds, within 5 minutes of server time; the exact value that was signed |
| wrappedKey | string | yes | – |
No output schema declared.
No examples provided.
send_feedback ~133
Free. Sends a message to the human operators of this service: a bug report, a problem with these tools or the documentation, or a suggestion. It is read by people, not processed by software, and nothing is returned beyond an acknowledgement. Do NOT use it for status updates, progress notes, task narration, error logs, or as a fallback when another tool is unavailable or a payment cannot be made -- it cannot complete, retry or work around any task. Name is optional (omit for anonymous feedback); message is limited to 1000 characters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| name | string | – | – |
No output schema declared.
No examples provided.
share_memory_key ~49
Free. Releases a previously creator-registered wrapped key to a reader, or the raw content key for a public document.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| readerPubKey | string | yes | – |
No output schema declared.
No examples provided.
store_persistent_memory ~63
Stores encrypted text memory (standard padded base64 ciphertext, up to 16384 bytes decoded). Requires x402 payment. Returns the memory's id.
| Name | Type | Req | Description |
|---|---|---|---|
| ciphertext | string | yes | base64-encoded, client-encrypted content |
| tags | array | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.agtrepo/agtrepo-memory MCP server?
io.github.agtrepo/agtrepo-memory is a hosted endpoint at https://agtrepo.com/mcp, 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 · agtrepo.com
claude mcp add --transport http agtrepo-agtrepo-memory 'https://agtrepo.com/mcp'
What is the io.github.agtrepo/agtrepo-memory MCP server?
io.github.agtrepo/agtrepo-memory is an MCP server listed in the public MCP registry as io.github.agtrepo/agtrepo-memory. Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base. This page covers its hosted endpoint (https://agtrepo.com/mcp).
Is the io.github.agtrepo/agtrepo-memory MCP server safe to use?
io.github.agtrepo/agtrepo-memory scores 76 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 io.github.agtrepo/agtrepo-memory MCP server expose?
io.github.agtrepo/agtrepo-memory exposes 6 tools: store_persistent_memory, read_memory, extend_memory, share_memory_key, register_key_release, send_feedback. Their descriptions and schemas cost roughly 541 tokens of context every time the server is loaded.
Does the io.github.agtrepo/agtrepo-memory MCP server require authentication?
No. We connected to io.github.agtrepo/agtrepo-memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.agtrepo/agtrepo-memory MCP server still maintained?
io.github.agtrepo/agtrepo-memory is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.