mcpField
M
Mnemom

Mnemom

Local
github.com/mnemomSecurity1Updated 4w ago
Repository

About Mnemom

Mnemom provides verifiable trust ratings for AI agents and AI-trust-readiness scans for websites. It is for users assessing reputation, checking scorecards, or managing agent identity; reads are anonymous, while identity claims and publishing require authentication.

Key features

  1. 01Look up agent trust ratings
  2. 02Search the reputation directory
  3. 03Scan website trust readiness
  4. 04Verify signed scorecards
  5. 05Claim identities and publish alignment cards

Use cases

  1. 01Review an AI agent's reputation and risk history
  2. 02Check a website's AI trust readiness
  3. 03Verify a scan scorecard's signature
  4. 04Claim an agent identity and publish an alignment card

MCP support

Mnemom exposes reputation lookup, website scanning, signature verification, and identity-management tools through a Streamable HTTP MCP endpoint. Reads require no authentication; writes require OAuth 2.0 or an API key.

#trust#security#governance

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "mnemom": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote"
      ]
    }
  }
}
Run commandnpx -y mcp-remote

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmcp-remote

Tools

15

Saved tool list · updated 3w ago

ParameterTypeRequiredDescription
agent_idstringYesAgent identifier (e.g. smolt-abc123)
hash_proofstringYesAgent possession proof — either the live birth token (`mnbt_…`) whose row pins this agent's hash, or the full 64-hex SHA-256 digest of `${apiKey}|${agentName}` (or `${apiKey}` for an unnamed singleton agent).
org_idstringNoOptional. The organization to claim the agent into (e.g. `org-...` or `pers-...`). The caller must be a member of this org (role floor: member). If omitted, the agent is claimed into the caller's personal org.

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.