Mnemom
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.
- Website: https://www.mnemom.ai · for agents: https://www.mnemom.ai/for-agents
- Docs: https://docs.mnemom.ai
- Rubric (isittrustready): https://www.isittrustready.ai/rubric
- Official MCP registry:
io.github.mnemom/mnemom - Maintainer: support@mnemom.ai
Connect
Streamable‑HTTP MCP endpoint (curated directory profile, 15 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
401with aWWW‑Authenticateheader 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
- Protected Resource Metadata:
- An
X-Mnemom-Api-Keyheader is accepted as an alternative to OAuth.
What's in the directory profile
A curated 15‑tool surface, grouped:
- Reputation —
get_reputation,get_reputation_badge,get_risk_history,search_reputation_directory,verify_reputation,list_agents,get_agent - Website trust scanning —
scan_trust,verify_scan - Identity & declarations —
claim_agent,preview_compose_alignment_by_agent,put_alignment_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
verificationblock (algorithm, key id, canonicalization rule) so a holder can reconstruct and check the signature.
Links
| Website | https://www.mnemom.ai |
| For agents | https://www.mnemom.ai/for-agents |
| Documentation | https://docs.mnemom.ai |
| Trust‑readiness rubric | https://www.isittrustready.ai/rubric |
| Contact | support@mnemom.ai |
© Mnemom. The server implementation is operated by Mnemom; this repository is its public manifest and documentation home.
Server Config
{
"mcpServers": {
"mnemom": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.mnemom.ai/mcp?profile=directory"
]
}
}
}