Skip to content
External endpointresponds

Is It Trust Ready — agent-trust-readiness scanner

Scan any website or MCP server for agent-trust-readiness; returns a signed, verifiable scorecard.

Endpoint URL
https://api.isittrustready.ai/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
798 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
io.github.mnemom/isittrustready

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
mnemom
Version
2.0.0
Capability keys
tools, resources, prompts
Tool names
get_agent, get_reputation, get_reputation_badge, get_started, scan_trust, search_reputation_directory, verify_reputation, verify_scan
Instructions excerpt

Mnemom is the trust plane for the agentic internet. Live, cryptographic trust signals for AI agents and the sites they act on; everything here is signed and independently verifiable against our public keys, and nothing is fabricated. New here? Call get_started (zero-auth, no args) for the surface map and auth guide. Two things you can do right now, no account: scan_trust(url) grades any website's agent-trust-readiness (signed scorecard + shareable permalink), and get_reputation(agent_id) / verify_reputation return any registered agent's signed, public Trust Rating. (An agent's risk history is authenticated — get_risk_history needs a Bearer/API-key credential.) Authenticate (Bearer JWT or X-Mnemom-Api-Key) to claim and manage your own agents — alignment cards, protection posture, and a verifiable Trust Rating that travels. We deliberately keep integrity- and alignment-internal detail owner-private; the public, signed proof rides in get_reputation.integrity_ratio. Read-only canoni

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 520ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 930ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 459ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 798ms