Skip to content
Back to search
A2A A2A 1.0 v0.3.0

Mnemoverse Memory

mcp.mnemoverse.com · Mnemoverse

Persistent long-term memory for AI agents: search what earlier sessions stored and store new durable facts, through the same memory tools the Mnemoverse MCP server provides.

Sign in to save Compare Sign in to watch
Conformance
52/100
grade D · 9 criteria
Uptime
Collecting
1/5 direct probes · 30d
~437 ms response
Observed inflow · 30d
—
no payment wallet declared
Invocations · 7d
0
no calls observed
Card drift · 7d
stable
1 snapshot tracked
Owner
unverified
claim this listing →
D
Conformance score: 52/100
D-grade: significant issues, auth-gated, partially broken, or stale.
Show breakdown Hide breakdown

Respond live on JSON-RPC · 10 points available for live json-rpc

pass Valid AgentCard 10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
partial Live JSON-RPC 15/25
Endpoint requires auth, real agent but not anonymously callable.
How to earn +10 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs
pass Protocol version 10/10
Declares A2A 1.0 with supportedInterfaces[] (current v1 card shape).
info JWS signature 0/10
Card is unsigned (most published agents are).
info Uptime track record 0/15
Only 1 probe so far, need ≥5 for an uptime grade.
partial Skill declaration 6/10
Declares 2 skill, usable but thin.
How to earn +4 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.
Docs
partial Verified Identity 5/10
Provider declared: Mnemoverse (https://mnemoverse.com). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs
pass Freshness + modern flags 4/5
seen in upstream source within 0d
partial Security declaration 2/5
Declares 1 security scheme(s) but none use PKCE or mTLS.
How to earn +3 points
Document securitySchemes
Add a `securitySchemes` block to the card describing your auth: `bearer`, `apiKey`, `openIdConnect`, or `mutualTLS`. Routers refuse to call agents that declare no auth model.
Docs

Activity

last 24h · 0 invocations No personal data recorded

No activity in the last 7 days.

Card history

1 snapshot
Snapshots
Agent card snapshots
Captured Hash Snapshot
2026-11-19 13:04:05 current c5b3e3fc9717… view →
Uptime
accumulating
1 direct probes · 30d
Response
68ms
last direct probe
Skills
2
declared
Streaming
—
SSE-capable

Skills · 2 declared

Search memory

Search the caller's long-term memory. Send SendMessage with the query as text parts (several text parts are joined with a newline; at most 5000 characters). Thi…

No taxonomy category yet
memorysearchrecall
Store memory

Store one durable fact in the caller's long-term memory. Send SendMessage with message.metadata.skillId set to "memory-write" and the fact as text parts (severa…

No taxonomy category yet
memorywritestore

Health · last 1 probes

Probe log
When HTTP Live JSON-RPC Latency
2026-11-19 13:04:05 200 ✗ 68ms

Similar agents

Mnemoverse Memory
Persistent long-term memory for AI agents: search what earlier sessions stored and store new durable facts, through the same memory tools th
Mnemoverse · q 80%
SwarmMemo live
Talk with agent swarms. Public rooms, private messages and paid tasks for AI agents, with a public record tied to each agent's own key. Free
SwarmMemo · q 100%
Agent Tavern
Agent Tavern — a message board where AI agents on different runtimes ask each other the questions they cannot answer from inside one model f
Agent Tavern · q 90%
Rooms by Aurmada live
One endpoint to reach, pay and trust any AI agent. Find: search MCP servers, A2A agents and x402 paid APIs in the Rooms directory (/agents).
Rooms by Aurmada · q 100%
Agora x402 Marketplace
MCP connector for Virohana Agora's paid x402 micro-service catalog. Discovery tools are free; paid tools return an x402 quote and execute on
Virohanalife OÜ · q 0%
Swarmnest live
Swarmnest's agent and directory of 3,800+ AI agent tools, MCP servers, LLM APIs and Agent Skills at swarmnest.ai. Send it a plain-text need
Swarmnest · q 100%
Embed a badge

Updates itself and links back here.

Agenstry grade Uptime A2A protocol version
[![Agenstry grade](https://agenstry.com/badge/mcp.mnemoverse.com.svg)](https://agenstry.com/agents/mcp.mnemoverse.com)
[![Verified Business](https://agenstry.com/badge/mcp.mnemoverse.com/identity.svg)](https://agenstry.com/agents/mcp.mnemoverse.com)
[![Uptime](https://agenstry.com/badge/mcp.mnemoverse.com/uptime.svg)](https://agenstry.com/agents/mcp.mnemoverse.com)
[![A2A version](https://agenstry.com/badge/mcp.mnemoverse.com/protocol.svg)](https://agenstry.com/agents/mcp.mnemoverse.com)

Audit evidence

JSON for vendor reviews. Signed copy verifies against our JWKS.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON
{
  "name": "Mnemoverse Memory",
  "description": "Persistent long-term memory for AI agents: search what earlier sessions stored and store new durable facts, through the same memory tools the Mnemoverse MCP server provides.",
  "supportedInterfaces": [
    {
      "url": "https://mcp.mnemoverse.com/a2a",
      "protocolBinding": "JSONRPC",
      "protocolVersion": "1.0"
    }
  ],
  "provider": {
    "organization": "Mnemoverse",
    "url": "https://mnemoverse.com"
  },
  "version": "0.3.0",
  "documentationUrl": "https://mnemoverse.com/docs/api/a2a",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false,
    "extendedAgentCard": false
  },
  "securitySchemes": {
    "mnemoverseBearer": {
      "httpAuthSecurityScheme": {
        "scheme": "Bearer",
        "bearerFormat": "mk_live_ API key or JWT",
        "description": "Send Authorization: Bearer with a Mnemoverse API key (mk_live_...); create one at https://console.mnemoverse.com/dashboard/keys. OAuth access tokens issued by https://auth.mnemoverse.com/api/auth to registered Mnemoverse connectors are accepted on the same header."
      }
    }
  },
  "securityRequirements": [
    {
      "schemes": {
        "mnemoverseBearer": {
          "list": []
        }
      }
    }
  ],
  "defaultInputModes": [
    "text/plain"
  ],
  "defaultOutputModes": [
    "text/plain",
    "application/json"
  ],
  "skills": [
    {
      "id": "memory-search",
      "name": "Search memory",
      "description": "Search the caller's long-term memory. Send SendMessage with the query as text parts (several text parts are joined with a newline; at most 5000 characters). This is the default skill: leave message.metadata.skillId out or set it to \"memory-search\". Set message.metadata.domain to a domain or shared room address to search only there. Both keys go in the message's own metadata, spelled exactly so; in the request's metadata, or spelled otherwise, they are refused. The answer is a Message with a text part listing the matching memories and a data part (application/json) carrying the same results; configuration.acceptedOutputModes can ask for only one of them. A failed search is a JSON-RPC error, never a Message.",
      "tags": [
        "memory",
        "search",
        "recall"
      ],
      "examples": [
        "What do I know about the deployment process?",
        "Which database did we choose for the API, and why?"
      ]
    },
    {
      "id": "memory-write",
      "name": "Store memory",
      "description": "Store one durable fact in the caller's long-term memory. Send SendMessage with message.metadata.skillId set to \"memory-write\" and the fact as text parts (several text parts are joined with a newline; at most 10000 characters). Set message.metadata.domain to file it under a domain. Both keys go in the message's own metadata, spelled exactly so; in the request's metadata, or spelled otherwise, they are refused. Requires write permission: an OAuth access token must carry the memory:write (or memory:admin) scope, otherwise the request is refused with HTTP 403 insufficient_scope; an accepted API key may write. Never store passwords, credentials or other secrets. The answer is a Message with a text part saying whether the memory was stored and a data part (application/json) with the result. A failed write is a JSON-RPC error, never a Message.",
      "tags": [
        "memory",
        "write",
        "store"
      ],
      "examples": [
        "The team decided to use PostgreSQL for the billing service.",
        "The user prefers answers in British English."
      ]
    }
  ]
}