Developer · Remote MCP server
Mnemom - Trust Ratings for AI Agents
Trust infrastructure for AI agents: read a verifiable Trust Rating, claim an identity, earn a badge.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mnemom/mnemom- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-06-12
- Updated
- 2026-06-12
- Publisher
- mnemom (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mnemom) · how
- Website
- www.mnemom.ai
- Repository
- github.com/mnemom/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.mnemom.ai/mcp?profile=directory | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- mnemom 2.0.0 · protocol 2025-06-18
- Tools discovered
15 - show names
claim_agent,get_agent,get_reputation,get_reputation_badge,get_started,list_agents,preview_compose_alignment_by_agent,preview_compose_protection_by_agent,put_alignment_by_agent,put_protection_by_agent,report_recipe_fn_fp,scan_trust,search_reputation_directory,verify_reputation,verify_scan- Checked on
- 2026-10-05
How to connect Mnemom - Trust Ratings for AI Agents
Mnemom - Trust Ratings for AI Agents is a remote MCP server: there is nothing to install. Its endpoint is https://api.mnemom.ai/mcp?profile=directory, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from mnemom (GitHub)
| Server | Runs |
|---|---|
| Is It Trust Ready - agent-trust-readiness scannerScan any website or MCP server for agent-trust-readiness; returns a signed, verifiable scorecard. | Remote · HTTPLive check: ✗ no handshake |
More developer servers
| Server | Runs |
|---|---|
| mneme RecordVault-native, accountable memory for Claude Code and MCP clients. Markdown is ground truth. | Local · stdio |
| MnemoSelf-correcting agent memory + MCP server: recall, supersede/revert/review corrections, erasure. | Local · stdio |
| MnemodbPersistent agent memory as plain Markdown in your repo - readable, diffable, with provenance. | Local · stdio |
| MnemographEvent-sourced knowledge graph memory for AI coding agents with semantic search. | Local · stdio |
| Mnemon MCPPersistent layered memory for AI agents. SQLite FTS5, fact versioning, zero-cloud. | Local · stdio |
| Mnemosyne OSMemory the human governs, on their own machine, plus what other coding agents here wrote. | Local · stdio |
| Mnemoverse MemoryHosted AI agent memory that learns from outcomes, with shared rooms, in Claude, Cursor and ChatGPT. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Mnki MCPMCP proxy that checks every tools/call against Agent Trust policy, with evidence, before it runs. | Local · stdio |