Skip to content

Mnemom — Trust Ratings for AI Agents MCP server

io.github.mnemom/mnemommnemomstreamable-httpv1.0.2Scanned

Trust infrastructure for AI agents: read a verifiable Trust Rating, claim an identity, earn a badge.

15 tools: 3 can delete or cancel things, 4 change things and 8 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel 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 Mnemom — Trust Ratings for AI Agents MCP server can do

The Mnemom — Trust Ratings for AI Agents MCP server is published by the GitHub account mnemom. It has 15 tools. It can delete or cancel things (3 tools: claim_agent, put_alignment_by_agent and put_protection_by_agent) and create or change data (4 tools: report_recipe_fn_fp, scan_trust, verify_reputation and verify_scan). 8 tools only read.

1 tool reads private data (search_reputation_directory); 3 tools bring in text other people can write (get_reputation_badge, scan_trust and verify_scan); 2 tools can send data out of your system (scan_trust and verify_scan). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.2.

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

Deletes or cancels 3Claude Code: deny
  • claim_agentClaim a verifiable identity — bind an agent to your organization so its trust and accountability record is provably yours.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.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Claim a verifiable identity — bind an agent to your organization so its trust and accountability record is provably yours. Requires the agent's possession proof (`hash_proof`). Re-claiming an agent you already own keeps its original claim date but files it under the organization you pass (`org_id`; if omitted, your personal organization), which can change the organization that owns and bills it.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • title: Claim an Agent Identity
  • put_alignment_by_agentPublish or replace an agent's alignment card: its governance modes, the principal it acts for, its declared values, the actions it may take on its own, and its audit policy.No findings

    Why it is in this group

    • The name "put_alignment_by_agent" says "put": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Publish or replace an agent's alignment card: its governance modes, the principal it acts for, its declared values, the actions it may take on its own, and its audit policy. The server merges the card with the platform, organization and team policies above it and stores the result. Use preview_compose_alignment_by_agent to dry-run first.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • title: Publish an Alignment Card
  • put_protection_by_agentPublish or replace an agent's protection card (screening mode, thresholds, trusted sources, protected assets).1 finding

    Why it is in this group

    • The name "put_protection_by_agent" says "put": a word for a change.
    • The description's first verb is "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The input schema at properties.protected_surface.properties.assets.items.properties.selector.description mentions "credentials".

      Matched text

      inputSchema.properties.protected_surface.properties.assets.items.properties.selector.description: "...om-api". A resource identifier only: no credentials, no connection strings, no personal dat..."

      What this check looks for
    Description, as the server wrote it
    Publish or replace an agent's protection card (screening mode, thresholds, trusted sources, protected assets). When connected by OAuth sign-in (e.g. ChatGPT), each publish first needs a one-time grant from the same signed-in account: open https://www.mnemom.ai/authorize-protection?agent_id=<agent_id>, approve, then publish within 15 minutes (each grant covers one publish). Required: agent_id, card_version, mode, thresholds, screen_surfaces and trusted_sources (protected_surface is optional); mode `enforce` also needs Safe House on the organization. Use preview_compose_protection_by_agent to dry-run without a grant.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • title: Publish a Protection Card
Changes things 4Claude Code: ask
  • report_recipe_fn_fpSubmit a false-positive / false-negative correction for one of Mnemom's automated detection rules (a 'recipe') — technical feedback that improves detection accuracy, like filing a …No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    Submit a false-positive / false-negative correction for one of Mnemom's automated detection rules (a 'recipe') — technical feedback that improves detection accuracy, like filing a bug report against a spam filter.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • title: Submit a Detection-Rule Correction
  • scan_trustScan a website's agent-trust-readiness and return a signed scorecard (Trust, plus an Access axis on newer rubrics).Reads text others writeCan 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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Scan a website's agent-trust-readiness and return a signed scorecard (Trust, plus an Access axis on newer rubrics). Zero-auth. Results are CACHED for up to 24h — check `cached` and `scannedAt` on the result; pass `fresh: true` to force a re-scan (rate-limited). Proxies to the SSRF-locked isittrustready scanner; the Ed25519 signature + permalink are preserved verbatim. Rubric + docs: https://www.isittrustready.ai/rubric and https://docs.mnemom.ai/.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Scan a Website's Trust-Readiness
  • verify_reputationAttest an agent's Trust Rating — returns the agent's checkpoint Merkle root, hash_chain_valid (true when the latest checkpoint's hash-chain link recomputes and carries an issuer si…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Attest an agent's Trust Rating — returns the agent's checkpoint Merkle root, hash_chain_valid (true when the latest checkpoint's hash-chain link recomputes and carries an issuer signature; earlier links are not re-walked), and a pointer to the signed integrity certificate. This is a chain-integrity attestation, NOT an in-band Ed25519 signature check (that parity is verify_scan, for website scorecards).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Verify a Trust Rating (Attestation)
  • verify_scanVerify a website scan scorecard's Ed25519 signature IN-BAND (verify, don't trust).Reads text others writeCan 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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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
    Verify a website scan scorecard's Ed25519 signature IN-BAND (verify, don't trust). Pass a `scan` (a scorecard from scan_trust) or a `url` to re-scan; returns {verified, key_id, canonicalization} checked against the public key at mnemom://iitr/jwks. Zero-auth. Spec + rubric: https://www.isittrustready.ai/rubric and https://docs.mnemom.ai/.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Verify a Scan Scorecard
Only reads 8Show 8 read-only tools
  • get_agentLook up an agent's public identity and trust state by ID — the accountable record other agents and humans can rely on.No findings

    Why it is in this group

    • The name "get_agent" says "get": a word for reading.
    Description, as the server wrote it
    Look up an agent's public identity and trust state by ID — the accountable record other agents and humans can rely on.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Look Up an Agent
  • get_reputationLook up an AI agent's published Trust Rating — Mnemom's portable reliability signal for autonomous software, computed from the agent's own verified activity record.No findings

    Why it is in this group

    • The name "get_reputation" says "get": a word for reading.
    Description, as the server wrote it
    Look up an AI agent's published Trust Rating — Mnemom's portable reliability signal for autonomous software, computed from the agent's own verified activity record. Returns the rating plus the technical factors behind it. Free, public, read-only: ratings are public by default, unless the agent's owner has opted out.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get an Agent's Trust Rating
  • get_reputation_badgeGet an embeddable Trust Rating badge for an agent — returns the badge image URL plus ready-to-paste Markdown and HTML snippets for a README or agent card.Reads text others writeNo findings

    Why it is in this group

    • The name "get_reputation_badge" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get an embeddable Trust Rating badge for an agent — returns the badge image URL plus ready-to-paste Markdown and HTML snippets for a README or agent card.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get an Embeddable Trust Badge
  • get_startedZero-auth, no-args orientation: who Mnemom is, the surface map, how to authenticate and what it unlocks, and the tools to try right now (scan_trust and the reputation lookups).No findings

    Why it is in this group

    • The name "get_started" says "get": a word for reading.
    Description, as the server wrote it
    Zero-auth, no-args orientation: who Mnemom is, the surface map, how to authenticate and what it unlocks, and the tools to try right now (scan_trust and the reputation lookups).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Get Started (Orientation)
  • list_agentsList the agents your account owns, with pagination (`limit`, `offset`).No findings

    Why it is in this group

    • The name "list_agents" says "list": a word for reading.
    Description, as the server wrote it
    List the agents your account owns, with pagination (`limit`, `offset`). Read-only.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List Your Agents
  • preview_compose_alignment_by_agentDry-run an alignment card: shows the card that would result after merging with the platform, organization and team policies above it, plus any conflicts.No findings

    Why it is in this group

    • The name "preview_compose_alignment_by_agent" says "preview": a word for reading.
    Description, as the server wrote it
    Dry-run an alignment card: shows the card that would result after merging with the platform, organization and team policies above it, plus any conflicts. Nothing is saved.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Preview Composed Alignment (Dry Run)
  • preview_compose_protection_by_agentDry-run a protection card: shows the card that would result after merging with the platform, organization and team policies above it, plus any conflicts.1 finding

    Why it is in this group

    • The name "preview_compose_protection_by_agent" says "preview": a word for reading.

    Findings

    • Info

      The input schema at properties.protected_surface.properties.assets.items.properties.selector.description mentions "credentials".

      Matched text

      inputSchema.properties.protected_surface.properties.assets.items.properties.selector.description: "...om-api". A resource identifier only: no credentials, no connection strings, no personal dat..."

      What this check looks for
    Description, as the server wrote it
    Dry-run a protection card: shows the card that would result after merging with the platform, organization and team policies above it, plus any conflicts. Nothing is saved, and no publish grant is needed.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Preview Composed Protection (Dry Run)
  • search_reputation_directoryResolve an agent name or id-prefix to a real agent_id over the PUBLIC reputation directory (only agents whose reputation visibility is public).Reads private dataNo findings

    Why it is in this group

    • The name "search_reputation_directory" says "search": a word for reading.

    What it can reach

    • private-dataThe name "search_reputation_directory" says "search" and "directory": it reads files.
    • private-dataThe description's first sentence says "resolve" and "directory": it reads files.
    Description, as the server wrote it
    Resolve an agent name or id-prefix to a real agent_id over the PUBLIC reputation directory (only agents whose reputation visibility is public). Zero-auth. The arriving-agent entry point: discover a concrete agent_id, then call get_reputation / verify_reputation on it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Search the Reputation Directory

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.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__mnemom__search_reputation_directory"
    ]
  }
}

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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.mnemom.ai/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.mnemom.ai
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (3 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.mnemom.ai/mcp?profile=directory: tools/list returned 15 tools to an anonymous client, including claim_agent (destructive), put_alignment_by_agent (destructive), put_protection_by_agent (destructive), report_recipe_fn_fp (write), scan_trust (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 info
  • The input schema at properties.protected_surface.properties.assets.items.properties.selector.description mentions "credentials".

    Matched text

    inputSchema.properties.protected_surface.properties.assets.items.properties.selector.description: "...om-api". A resource identifier only: no credentials, no connection strings, no personal dat..."

    What this check looks for
  • The input schema at properties.protected_surface.properties.assets.items.properties.selector.description mentions "credentials".

    Matched text

    inputSchema.properties.protected_surface.properties.assets.items.properties.selector.description: "...om-api". A resource identifier only: no credentials, no connection strings, no personal dat..."

    What this check looks for

History

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

  1. Tools1 changed.~1 changedView diff

Install

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

claude mcp add --transport http mnemom https://api.mnemom.ai/mcp?profile=directory
claude mcp add --transport http mnemom https://api.mnemom.ai/mcp?profile=directory

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__mnemom__get_agent",
      "mcp__mnemom__get_reputation",
      "mcp__mnemom__get_reputation_badge",
      "mcp__mnemom__get_started",
      "mcp__mnemom__list_agents",
      "mcp__mnemom__preview_compose_alignment_by_agent",
      "mcp__mnemom__preview_compose_protection_by_agent",
      "mcp__mnemom__search_reputation_directory"
    ],
    "ask": [
      "mcp__mnemom__report_recipe_fn_fp",
      "mcp__mnemom__scan_trust",
      "mcp__mnemom__verify_reputation",
      "mcp__mnemom__verify_scan"
    ],
    "deny": [
      "mcp__mnemom__claim_agent",
      "mcp__mnemom__put_alignment_by_agent",
      "mcp__mnemom__put_protection_by_agent"
    ]
  }
}

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 mnemom. Review it before you use it.

Capability tags behind 4 rules
  • mcp__mnemom__get_reputation_badge untrusted-input
  • mcp__mnemom__scan_trust untrusted-input, outbound
  • mcp__mnemom__search_reputation_directory private-data
  • mcp__mnemom__verify_scan untrusted-input, 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/io.github.mnemom/mnemom/verify?hash=06a3fddf08cc529252cbe568bca0647550eb719995956f6ed68685f43007991c" | jq -e '.changed == false'

Pinned hash 06a3fddf08cc, from Nov 20, 2026, 04:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.mnemom/mnemom/changes.xml

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

Badge

Anlyon Radar badge for io.github.mnemom/mnemom
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.mnemom/mnemom.svg)](https://radar.anlyon.com/servers/io.github.mnemom/mnemom)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:41 UTC.

Mnemom — Trust Ratings for AI Agents MCP server: questions and answers

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

Is the Mnemom — Trust Ratings for AI Agents MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 7 of which can change, send or delete something, and 2 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 Mnemom — Trust Ratings for AI Agents MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: claim_agent, put_alignment_by_agent and put_protection_by_agent.

Can the Mnemom — Trust Ratings for AI Agents 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 Mnemom — Trust Ratings for AI Agents MCP server have?

15 tools: 3 destructive, 4 write, 8 read. claim_agent, put_alignment_by_agent, put_protection_by_agent, report_recipe_fn_fp, scan_trust, verify_reputation, verify_scan, get_agent and 7 more.

Does the Mnemom — Trust Ratings for AI Agents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Mnemom — Trust Ratings for AI Agents MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_trust and verify_scan.

Has the Mnemom — Trust Ratings for AI Agents MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.