Skip to content

Mnemos — memory as a service MCP server

com.virohanalife/mnemosvirohanalife.comstreamable-httpv1.0.0Scanned

Bi-temporal memory-as-a-service and paid agent labor. Pay-per-call USDC via x402; signed receipts.

15 tools: 11 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 11 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Sign-in required, no OAuth metadata. Remote posture

With Anlyon

11 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Mnemos — memory as a service MCP server can do

The Mnemos — memory as a service MCP server is published by virohanalife.com, a domain the MCP Registry verified. It has 15 tools. It can create or change data (11 tools: agora_catalog, fact_verify, code_review, research_brief and 7 more), but cannot delete data. 4 tools only read.

1 tool can send data out of your system (trust_check).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 17, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Changes things 11Claude Code: ask
  • agora_catalogFREE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    FREE. Discover the full Agora x402 service catalog: every buyable tool, its price in USDC on Base, and the x402 settlement parameters (network, asset, payTo). Call this first to see what you can buy and how to pay.
  • code_reviewPAID (0.05 USDC).No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    PAID (0.05 USDC). Review a code snippet for correctness, security, and clarity; returns a severity-ranked findings report after payment. Returns an x402 quote.
  • embed_batchPAID (0.005 USDC).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (0.005 USDC). Text embeddings via local Jetson Ollama (nomic-embed-text, 6000-char truncation, up to 32 texts per batch). Returns an x402 quote + payment instructions; {model, dims, vectors} is delivered after payment settles.
  • fact_verifyPAID (0.25 USDC).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (0.25 USDC). Verify a factual claim and return a supported/refuted verdict with reasoning and citations. Returns an x402 quote + payment instructions.
  • mnemos_as_ofPAID (0.005 USDC).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (0.005 USDC). THE BI-TEMPORAL READ -- the thing no other memory service on this mesh sells. Answers: "what did the store BELIEVE at `tx_time` about what was TRUE at `valid_time`?" Use it to replay an agent's decision with only the knowledge it had at the time (no hindsight leakage), to audit corrections, and to distinguish "we were wrong" from "the world changed". Returns an x402 quote.
  • mnemos_provisionPAID (0.50 USDC, monthly floor).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (0.50 USDC, monthly floor). Mint your own fully isolated bi-temporal memory namespace. Payment IS the identity -- no signup, no email: settling the x402 quote issues a tenant key, shown exactly once. Returns an x402 quote.
  • mnemos_saas_infoFREE.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    FREE. Learn how Mnemos-as-a-Service works before buying: the BI-TEMPORAL contract (two independent time axes per memory), the tenant-isolation model, limits, pricing, and a worked example showing four different correct answers for one key. No payment, no tenant data. Call this first.
  • mnemos_storePAID (0.01 USDC).No findings

    Why it is in this group

    • The name "mnemos_store" says "store": a word for a change.
    Description, as the server wrote it
    PAID (0.01 USDC). Store a memory in your isolated bi-temporal namespace. Append-only: `supersedes` marks a prior belief as no longer held WITHOUT destroying it, so it stays queryable via mnemos_as_of. `valid_from`/`valid_to` describe when the fact is true IN THE WORLD and may be backdated; the system's own knowledge timestamps are server-stamped and cannot be forged. Returns an x402 quote; requires header X-TENANT-KEY once settled.
  • notarizePAID (0.10 USDC).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (0.10 USDC). Produce a tamper-evident notarization record (sha256 digest + signed timestamp) for a piece of content. The quote preview already includes the sha256 digest so you can verify integrity; the signed record follows payment.
  • research_briefPAID (0.10 USDC).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    PAID (0.10 USDC). Structured synthesis brief on a topic, from local model knowledge only. This tool does NO live web research and returns NO citations -- claims are not sourced. The delivered brief carries in-band caveats stating its knowledge cutoff and limits. If you need cited, web-researched output, that is a different product (research-brief-pro on the HTTP rail), not this one. Returns an x402 quote + payment instructions; the brief is delivered after settlement.
  • trust_checkPAID (0.05 USDC).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    PAID (0.05 USDC). Combined Trust Oracle probe: aggregate bazaar-index stats (reachable/valid-402 counts, median latency) + a watchtower attestation for one URL (reachable, returns_402, latency, score). Returns an x402 quote + payment instructions; the combined result is delivered after payment settles.
Only reads 4Show 4 read-only tools
  • mnemos_get_contextPAID (0.005 USDC).No findings

    Why it is in this group

    • The name "mnemos_get_context" says "get": a word for reading.
    Description, as the server wrote it
    PAID (0.005 USDC). The endpoint to call right before a completion: searches your memories, dedupes to the most-recent belief per key, budget-packs them into `max_chars`, and returns a ready-to-paste context block plus structured provenance. Content flagged as prompt-injection is excluded from the block. Optionally assembled AS OF a past time. Returns an x402 quote.
  • summarizePAID (0.03 USDC).No findings

    Why it is in this group

    • The name "summarize" says "summarize": a word for reading.
    Description, as the server wrote it
    PAID (0.03 USDC). Full-quality document summarization. Returns an x402 quote + payment instructions; the summary is delivered after payment settles.
  • summarize_demoFREE.No findings

    Why it is in this group

    • The name "summarize_demo" says "summarize": a word for reading.
    Description, as the server wrote it
    FREE. A working demo of the paid `summarize` tool: returns a tiny deterministic extractive summary (first + most-salient sentences, capped ~280 chars) so agents can verify the connector end-to-end before buying. No payment, no auth required.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:50 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
530
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 530.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 530
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 11 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 530; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 11 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 530
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 11 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http mnemos https://memory.virohanalife.com/mcp
claude mcp add --transport http mnemos https://memory.virohanalife.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mnemos__summarize_demo",
      "mcp__mnemos__summarize",
      "mcp__mnemos__mnemos_search",
      "mcp__mnemos__mnemos_get_context"
    ],
    "ask": [
      "mcp__mnemos__agora_catalog",
      "mcp__mnemos__fact_verify",
      "mcp__mnemos__code_review",
      "mcp__mnemos__research_brief",
      "mcp__mnemos__notarize",
      "mcp__mnemos__trust_check",
      "mcp__mnemos__embed_batch",
      "mcp__mnemos__mnemos_saas_info",
      "mcp__mnemos__mnemos_provision",
      "mcp__mnemos__mnemos_store",
      "mcp__mnemos__mnemos_as_of"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mnemos. Review it before you use it.

Capability tags behind 1 rule
  • mcp__mnemos__trust_check outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.virohanalife/mnemos/verify?hash=2069340caa0194e356606d03f19fb88065eff378bf489dba0e6e9ec5deff3c2b" | jq -e '.changed == false'

Pinned hash 2069340caa01, from Nov 17, 2026, 04:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.virohanalife/mnemos/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.virohanalife/mnemos
[![Anlyon Radar](https://radar.anlyon.com/badge/com.virohanalife/mnemos.svg)](https://radar.anlyon.com/servers/com.virohanalife/mnemos)

Source: MCP Registry. Synced Oct 21, 2026, 18:10 UTC.

Mnemos — memory as a service MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Mnemos — memory as a service MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Mnemos — memory as a service MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Mnemos — memory as a service MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Mnemos — memory as a service MCP server have?

15 tools: 11 write, 4 read. agora_catalog, fact_verify, code_review, research_brief, notarize, trust_check, embed_batch, mnemos_saas_info and 7 more.

Does the Mnemos — memory as a service MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Mnemos — memory as a service MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): trust_check.

Has the Mnemos — memory as a service MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.