Mnemoverse Memory
This profile reflects information published by the agent provider.
Card passedAuthentication requiredUnsigned card
About this agent
LocalMark's observation
LocalMark first listed this public Agent Card on 19 Nov 2026, 00:02 UTC. Its latest card check succeeded. The card declares 2 skills and a JSONRPC interface. LocalMark has not run a production A2A task. Explicitly opted-in synthetic tests are shown separately.
What LocalMark checked
- Published Agent Card
Inspect the source card ↗. The last successful fetch was 19 Nov 2026, 00:02 UTC.
- Latest card check: passed
19 Nov 2026, 00:02 UTC · Agent Card validated
- Advertised endpoint: TLS connection passed
19 Nov 2026, 00:02 UTC · Valid TLS connection to advertised endpoint host; no A2A request sent This does not test the A2A protocol or run a task.
- Read-only protocol probe: Authentication required
19 Nov 2026, 00:02 UTC · Endpoint requires authentication; A2A response not confirmed LocalMark sent no message and did not request task creation.
- Unsigned card
This card does not provide a digital signature. Checked 19 Nov 2026, 00:02 UTC.
- 30-day card check history
1 of 1 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.
- Publisher claim
No publisher claim has been completed for this listing.
Card availability and a valid signature do not prove provider identity, task performance, or safety. Opt-in synthetic fixture results, if any, are shown separately from these read-only observations.
Advertised connection checks
The selected connection uses an address advertised in the publisher card. Read-only observations do not establish task quality or safety.
- JSONRPC · 1.0 · Selected connection
https://mcp.mnemoverse.com/a2aAuthentication required · 19 Nov 2026, 00:02 UTC
Endpoint requires authentication; A2A response not confirmed
Up to three supported interfaces are checked per cycle. Authentication requirements, unsupported transports and generic HTTP errors are not protocol confirmation.
Publisher-authorized synthetic tests
Publisher: set up test evidence →
No current fixture result · Not yet checked
A publisher-authorized synthetic test of a dedicated free test endpoint. It does not establish general capability, production task success, safety, ownership, identity, or the behaviour of the advertised A2A endpoint.
Consent: not confirmed.
Recent fixture observations
- No fixture tests recorded.
Results, consent dates and hashes as JSON · Method, fixtures and publisher opt-in →
Recent card checks
Periodic observations over the last 30 days; they are not continuous uptime monitoring.
Show 1 recent check
- Passed · 19 Nov 2026, 00:02 UTC
Agent Card validated
Card and signature changes
- No changes recorded since change tracking began.
Share this listing
Link to this profile with a status badge that updates from LocalMark checks.
README Markdown:
[](https://localmark.ai/agents/656232)Card-declared connections
These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.
- No card-declared connections recorded yet.
Declared skills 2
- 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). 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.
- 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 (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.