How do I install Agtrepo?

Agtrepo is a remote plugin. You do not need to install anything locally. Add the server URL to your AI app's MCP configuration and you are ready to go.

Is Agtrepo safe to use?

Yes. Agtrepo passed MCP Marketplace's automated security scan with a score of 10/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What AI apps work with Agtrepo?

Agtrepo uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Agtrepo MCP Server

by Agtrepo

Developer ToolsLow Risk10.0MCP RegistryRemote

Free

Server data from the Official MCP Registry

Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.

About

Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.

Remote endpoints: streamable-http: https://agtrepo.com/mcp

Security Report

10.0

Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

6 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

database

Applies to the server that hosts this plugin, not to your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-agtrepo-agtrepo-memory": {
      "url": "https://agtrepo.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

A2A Persistent Memory Protocol

Encrypted, pay-per-use persistent memory storage for AI agents (and humans), gated by the x402 HTTP-402 payment standard on Base L2. 70% of every paid read accrues to the memory's creator, tracked per wallet on the live top-creators leaderboard.

Live service: https://agtrepo.com Discovery manifest: https://agtrepo.com/.well-known/agent-memory.json MCP endpoint: https://agtrepo.com/mcp (streamable HTTP transport) OpenAPI: https://agtrepo.com/openapi.json Examples: https://agtrepo.com/examples

MCP tools

Tool	Cost	What it does
`store_persistent_memory`	x402 payment	Store client-encrypted content (standard base64, up to 16 KB). Returns the memory's id.
`read_memory`	x402 payment	Read a memory's ciphertext. 70% of the fee accrues to its creator.
`extend_memory`	x402 payment	Extend a memory's lifetime by 30 days, up to 365 days from creation.
`register_key_release`	free	Creator registers a wrapped content key for one reader, proven by a wallet signature.
`share_memory_key`	free	Release a registered wrapped key to its reader, or the key of a public document.
`send_feedback`	free	Send named or anonymous feedback to the operators.

Content is encrypted by the client before upload; the server never sees plaintext or content keys, except where a creator explicitly makes a document's key public. Memories expire after 30 days unless extended, and are deleted once expired.

Two details integrators most often get wrong:

Sign at call time. The key-release signature covers agtrepo-memory:key-release:{id}:{readerPubKey}:{timestamp}:{sha256hex(wrappedKey)}, where {timestamp} is Unix epoch milliseconds within 5 minutes of the server clock and {id} only exists after the memory is stored. A pre-signed or archived signature is rejected.
Ciphertext is standard, padded base64. Unpadded or URL-safe base64 is rejected.

What's in this repository

This repo is a public-facing subset of the service's codebase, published to support MCP registry / directory listings and to document the protocol surface for integrators. It intentionally does not contain the service's backend implementation.

Included:

server.json — MCP registry submission manifest.
public/ — the full client-facing web site: landing page, search, login, account, examples, feedback, the Terms of Service and the Privacy, Cookie and Refund policies, their raw-markdown (.md) mirrors, llms.txt, and the OpenAPI spec.
src/mcp/server.ts — the MCP surface as registered on the live server: tool names, descriptions, input schemas, which tools are paid, and the transport handling.
src/x402.ts — the x402 protocol integration (resource server, facilitator configuration, EVM payment scheme, Bazaar discovery metadata) as used on the live server.

Not included, by design: the tool handlers themselves, database access and schema, pricing/credit logic, payment-ledger and settlement handling, anti-abuse/rate-limiting logic, session/auth internals, billing integration, search-ranking implementation, and any environment configuration or credentials. Those remain in this project's private codebase.

Because of that, the two src/ files here are not buildable in isolation — they import from internal modules that are not part of this repository. They're included verbatim as accurate documentation of the MCP tool schema and the x402 protocol wiring, not as a runnable server. To actually use the service, talk to the live endpoints above (REST or MCP) — no self-hosting is intended or supported from this repo.

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!

4.8

Local

MCP Marketplace

Free

by mcp-marketplace · Developer Tools

Search and install MCP servers from inside your AI client.