Mnemom — Trust Ratings for AI Agents

io.github.mnemomPublished by GitHub account mnemomv1.0.2Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Mnemom is a remote MCP server for looking up verifiable trust ratings for AI agents, scanning websites for AI-trust readiness, and claiming agent identities.

What you can do
Look up and search agent reputation, fetch badges, verify scorecards and list agents in the reputation directory, with risk history available on the authenticated surface. Scan a website's AI-trust readiness and verify signed scan scorecards in-band. Claim an agent identity, verify agent bindings, and preview or publish alignment and protection cards. Get orientation guidance for getting started.
When to use it
Useful when an assistant needs to check or present an AI agent's trust rating, assess a website's AI-trust readiness, or verify a signed scorecard before relying on it. Also relevant for publishing an agent's identity, alignment or protection information.
Requirements
A remote streamable-HTTP endpoint; no local runtime or package. Reads are anonymous with no key or login. Writes require OAuth 2.0 with dynamic client registration and PKCE, or an X-Mnemom-Api-Key header. Network access to the Mnemom API is needed.
Before you install
Write operations such as claiming an agent or publishing alignment and protection cards require authentication and change data on the Mnemom platform. An X-Mnemom-Api-Key header is an alternative credential to protect. Requests and scan targets are sent to a third-party service.

Installation

In SourceWeft

  1. Open Mnemom — Trust Ratings for AI Agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mnemom%2Fmnemom/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mnemom-trust-ratings-for-ai-agents": {
      "type": "http",
      "url": "https://api.mnemom.ai/mcp?profile=directory"
    }
  }
}

README

Mnemom — Trust Ratings for AI Agents (MCP server)

Canonical home for the Mnemom Model Context Protocol (MCP) server — trust infrastructure for the agent internet. Look up a verifiable Trust Rating for an AI agent, scan a website's AI-trust-readiness, verify signed scorecards in‑band, claim an agent identity, and publish an alignment card.

This repo is the public, canonical source of truth for the server's connection details and manifest. The server implementation runs on Mnemom's platform; this repo is its metadata + documentation home.

Connect

Streamable‑HTTP MCP endpoint (curated directory profile, 16 tools):

https://api.mnemom.ai/mcp?profile=directory

The full manifest is in server.json.

In Claude / ChatGPT / any MCP client

Add a custom connector pointing at the URL above. Reads are anonymous — you can list tools and call the reputation, search, scan, verify, and get‑started tools with no account. Writes (claiming an agent, publishing an alignment card) require authentication.

Authentication

  • Reads: zero‑auth. No key, no login.
  • Writes: OAuth 2.0 with Dynamic Client Registration (RFC 7591) + PKCE. Discovery follows RFC 9728 — an unauthenticated write returns 401 with a WWW‑Authenticate header pointing at the Protected Resource Metadata, so a compliant client can self‑configure:
    • Protected Resource Metadata: https://api.mnemom.ai/.well-known/oauth-protected-resource/mcp
    • Authorization Server Metadata: https://api.mnemom.ai/.well-known/oauth-authorization-server
  • An X-Mnemom-Api-Key header is accepted as an alternative to OAuth.

What's in the directory profile

A curated 16‑tool surface, grouped:

  • Reputation — get_reputation, get_reputation_badge, search_reputation_directory, verify_reputation, list_agents, get_agent (agent risk history is authenticated — see get_risk_history on the full surface)
  • Website trust scanning — scan_trust, verify_scan
  • Identity & protection — claim_agent, verify_agent_binding, preview_compose_alignment_by_agent, put_alignment_by_agent, preview_compose_protection_by_agent, put_protection_by_agent, report_recipe_fn_fp
  • Orientation — get_started

The default endpoint (/mcp, no profile) exposes the full power‑user tool surface; ?profile=directory is the curated face used for directory listings.

Verify, don't trust

Scan scorecards are Ed25519‑signed. Verify any scorecard in‑band with the verify_scan tool, or check the signature yourself against the published key:

  • Scanner JWKS: mnemom://iitr/jwks (also at the isittrustready surface)
  • The scorecard carries a self‑describing verification block (algorithm, key id, canonicalization rule) so a holder can reconstruct and check the signature.

Links

Websitehttps://www.mnemom.ai
For agentshttps://www.mnemom.ai/for-agents
Documentationhttps://docs.mnemom.ai
Trust‑readiness rubrichttps://www.isittrustready.ai/rubric
Contact[email protected]

© Mnemom. The server implementation is operated by Mnemom; this repository is its public manifest and documentation home.

Source: README.md at commit 72c49c5

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.