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.
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
How to earn +10 points
How to earn +4 points
How to earn +5 points
How to earn +3 points
Activity
last 24h · 0 invocations No personal data recordedNo activity in the last 7 days.
Card history
1 snapshotSnapshots
| Captured | Hash | Snapshot |
|---|---|---|
| 2026-11-19 13:04:05 current | c5b3e3fc9717… |
view → |
Endpoints
| Agent card | https://mcp.mnemoverse.com/.well-known/agent-card.json |
| Provider | https://mnemoverse.com |
| Docs | https://mnemoverse.com/docs/api/a2a |
Skills · 2 declared
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…
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…
Health · last 1 probes
Similar agents
Embed a badge
Updates itself and links back here.
[](https://agenstry.com/agents/mcp.mnemoverse.com) [](https://agenstry.com/agents/mcp.mnemoverse.com) [](https://agenstry.com/agents/mcp.mnemoverse.com) [](https://agenstry.com/agents/mcp.mnemoverse.com)
Audit evidence
JSON for vendor reviews. Signed copy verifies against our JWKS.
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."
]
}
]
}