mcp server
Mnemom — Trust Ratings for AI Agents
Trust infrastructure for AI agents: read a verifiable Trust Rating, claim an identity, earn a badge.
Description as published by the maintainer. Source
- version 1.0.2
- active
active — Registry entry last updated 2026-06-12.
What this server can do
15 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
claim_agent(org_id, agent_id, hash_proof)- Claim a verifiable identity — bind an agent to your organization so its trust and accountability record is provably yours. No human in the loop. Required: agent_id, hash_proof.
get_agent(agent_id)- Look up an agent's public identity and trust state by ID — the accountable record other agents and humans can rely on. Required: agent_id.
get_reputation(agent_id)- 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: every registered agent's rating is published by standard (the `visibility` field is the reputation-publication axis, distinct from identity-record visibility). Required: agent_id.
get_reputation_badge(agent_id)- 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. Required: agent_id.
get_started(token)- Zero-auth, no-args orientation: who Mnemom is, the surface map, how to authenticate and what it unlocks, and the value tools to try right now (headlining scan_trust + the reputation reads).
list_agents(limit, offset)- List your agents — List all agents owned by the authenticated user. Supports pagination.
preview_compose_alignment_by_agent(audit, values, agent_id, autonomy, principal, card_version, autonomy_mode, integrity_mode)- Preview composed alignment (dry run) — Composes the cascade against a hypothetical body at the agent layer and returns conflicts + the composed view. No DB writes. Used by the dashboard editor for live conflict markers. Required: agent_id, card_version, autonomy_mode, integrity_mode, principal, values, autonomy, audit.
preview_compose_protection_by_agent(mode, agent_id, thresholds, card_version, screen_surfaces, trusted_sources, protected_surface)- Preview composed protection (dry run) — Composes the cascade against a hypothetical body at the agent layer and returns conflicts + the composed view. No DB writes. Used by the dashboard editor for live conflict markers. Required: agent_id, card_version, mode.
put_alignment_by_agent(audit, values, agent_id, autonomy, principal, card_version, autonomy_mode, integrity_mode)- Publish or replace the alignment manifest — Accepts YAML (`text/yaml`, `application/yaml`) or JSON. Body is the full `UnifiedAlignmentCard`; server-side composition merges it across the platform → org → team → agent cascade and writes the canonical composed card. Requires `Idempotency-Key`. Honor... Required: agent_id, card_version, autonomy_mode, integrity_mode, principal, values, autonomy, audit.
put_protection_by_agent(mode, agent_id, thresholds, card_version, screen_surfaces, trusted_sources, protected_surface)- Publish or replace the protection manifest — Accepts YAML (`text/yaml`, `application/yaml`) or JSON. Body is the full `UnifiedProtectionCard`; server-side composition merges it across the platform → org → team → agent cascade and writes the canonical composed card. Requires `Idempotency-Key`. Hon... Required: agent_id, card_version, mode.
report_recipe_fn_fp(type, summary, agent_id, recipeId, checkpoint_id)- 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. Required: recipeId, type, summary.
scan_trust(url, fresh)- 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/. Required: url.
search_reputation_directory(q, page, sort, grade, per_page, confidence)- 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.
verify_reputation(agent_id)- Attest an agent's Trust Rating — returns a Merkle-root + hash-chain attestation (hash_chain_valid) proving the rating derives from an unbroken, append-only checkpoint chain, plus 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). Required: agent_id.
verify_scan(url, scan)- 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/.
Last successful function declaration observed on . Source: https://api.mnemom.ai/mcp?profile=directory. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.mnemom.ai/mcp?profile=directory.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-12 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-12 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 15 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.mnemom.ai | |
| mcp endpoint status | ok | The server listed 15 functions when asked. | as of probe | api.mnemom.ai |
Where to get it
Also from mnemom
-
Is It Trust Ready — agent-trust-readiness scanner
Scan any website or MCP server for agent-trust-readiness; returns a signed, verifiable scorecard.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json