Is It Trust Ready — agent-trust-readiness scanner
REMOTE · API.ISITTRUSTREADY.AI · SCANNED SEP 22
Scan any website or MCP server for agent-trust-readiness; returns a signed, verifiable scorecard.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Is It Trust Ready — agent-trust-readiness scanner MCP server?
Is It Trust Ready — agent-trust-readiness scanner is a hosted endpoint at https://api.isittrustready.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.isittrustready.ai
claude mcp add --transport http mnemom-isittrustready 'https://api.isittrustready.ai/mcp'
{
"mcpServers": {
"mnemom-isittrustready": {
"url": "https://api.isittrustready.ai/mcp"
}
}
} {
"servers": {
"mnemom-isittrustready": {
"type": "http",
"url": "https://api.isittrustready.ai/mcp"
}
}
} [mcp_servers.mnemom-isittrustready] url = "https://api.isittrustready.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mnemom-isittrustready": {
"type": "remote",
"url": "https://api.isittrustready.ai/mcp",
"enabled": true
}
}
} openclaw mcp add mnemom-isittrustready --url 'https://api.isittrustready.ai/mcp' --transport streamable-http
mcp_servers:
mnemom-isittrustready:
url: "https://api.isittrustready.ai/mcp" {
"McpServers": {
"mnemom-isittrustready": {
"Transport": "http",
"Url": "https://api.isittrustready.ai/mcp"
}
}
} assistant mcp add mnemom-isittrustready -t streamable-http -u 'https://api.isittrustready.ai/mcp'
{
"mcpServers": {
"mnemom-isittrustready": {
"type": "http",
"url": "https://api.isittrustready.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Aug 26 −65
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://api.isittrustready.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=isittrustready.ai | CN=WE1,O=Google Trust Services,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ec23eaa7d996730e0e3e6c701037211b |
| SANs: isittrustready.ai, *.isittrustready.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.isittrustready.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| isittrustready.ai. | present | 2371 | 13 | Verified |
| api.isittrustready.ai. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.isittrustready.ai/mcp | HTTP error | 404 | |
| http (plaintext) | http://api.isittrustready.ai/mcp | HTTPS enforced | 301 | https://api.isittrustready.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_agent ~51
Look up an agent's public identity and trust state by ID — the accountable record other agents and humans can rely on.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier (e.g. smolt-abc123) |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_hash | string | – | The canonical public identity hash (first 16 hex chars) used as the gateway lookup key and as the input to verify_agent_binding. Owner projection only. Not a credential and not reversible to one. |
| aip_enforcement_mode | string|null | – | – |
| avatar_url | string|null | – | – |
| caller | string | – | Which projection THIS response is. `org_member` receives the owner field set; `anonymous`/`authenticated` receive the reduced public set (id, name, claimed, created_at, last_seen, status, avatar_url,… |
| claimed | boolean | – | Whether a human or organization has claimed accountability for this agent. On the owner projection this is derived from the ownership column; the owning user's identifier itself is not returned. |
| claimed_at | string|null | – | – |
| containment_status | string|null | – | Containment state of the agent. |
| created_at | string | – | – |
| groups | array | – | Active groups this agent belongs to, name-ordered; `[]` when none. Present on org-fleet rows. |
| id | string | yes | Agent identifier (e.g. smolt-abc123). |
| last_seen | string|null | – | – |
| name | string|null | – | Agent name (2-32 chars, alphanumeric + hyphens). |
| org_id | string|null | – | The agent's organization binding. Required as an input by the org-scoped tools (fleet listing, posture assignment). Identifies an organization, not a person. |
| public | boolean | – | Whether the agent's identity record is publicly discoverable. Distinct from Trust Rating visibility, which is always public. |
| status | string | – | Derived from last_seen (active = seen within the last hour). |
No examples provided.
get_reputation ~104
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier (e.g. smolt-abc123) |
| Name | Type | Req | Description |
|---|---|---|---|
| a2a_trust_extension | object | – | A2A trust extension for interop. Only present on `GET /reputation/{agent_id}` (not on batch/compare rows). |
| agent_id | string | yes | – |
| agent_name | string|null | – | – |
| checkpoint_accounting | object|null | – | Structured breakdown of how checkpoints were counted toward the score. `analyzed` is the scoring population; `excluded` buckets are mutually exclusive and `analyzed + synthetic + insufficient_thinkin… |
| checkpoint_count | integer | yes | – |
| claimed | boolean | – | – |
| components | array | yes | – |
| computed_at | string|null | – | – |
| confidence | string | yes | – |
| grade | string|null | yes | AAA–D or NR. |
| is_eligible | boolean | yes | – |
| next_compute_at | string|null | – | Next scheduled recompute — the 00/06/12/18 UTC cron slot strictly after `computed_at` (`floor(computed_at/6h)*6h + 6h`). Null when `computed_at` is null. |
| score | integer|null | yes | – |
| tier | string|null | – | – |
| trend_30d | number|null | – | – |
| visibility | string | yes | Reputation-publication axis — whether this agent's Trust Rating is published. Every registered agent's reputation is `public` by accountability standard (the default; that is the whole point of a por… |
No examples provided.
get_reputation_badge ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier (e.g. smolt-abc123) |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | The agent the badge is for (echoed from the request). |
| badge_url | string | yes | Canonical SVG Trust Rating badge image URL (always on api.mnemom.ai). |
| html_embed | string | yes | Paste-ready HTML badge snippet. |
| markdown_embed | string | yes | Paste-ready Markdown badge snippet. |
| profile_url | string | yes | Human-readable reputation profile page (on www.mnemom.ai). |
| verified_url | string | yes | Public cryptographic verification URL for the rating. |
No examples provided.
get_started ~103
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).
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | Optional Dojo try-me invite token. When supplied and valid, returns the token-gated dojo briefing manifest (the same content as GET /v1/dojo/try-me/resolve); omit for public orientation. |
| Name | Type | Req | Description |
|---|---|---|---|
| authenticate | object | yes | How to authenticate and what auth unlocks. |
| developer_path | object | yes | The developer hero on-ramp: the npx one-liner plus the intent-named MCP prompt-skills (try-me, onboard_an_agent, become_sovereign). Advertisement only — no functional dependency on those prompts exis… |
| doctrine | string | yes | – |
| showcase_agent | object | yes | A real Mnemom-owned agent the try_now reputation reads target, so the loop runs verbatim. |
| skill_path | object | yes | The two-step on-ramp to declaring and advertising capabilities as A2A skills in a signed, portable AgentCard. |
| sovereignty_path | object | yes | The five-step on-ramp to becoming a sovereign, accountable agent, composed from existing tools. Walked end to end by the become_sovereign MCP prompt. |
| surface_map | object | yes | Stable links to the canonical read-only surfaces. |
| try_now | array | yes | Zero-auth value tools to call right now. |
| value_prop | string | yes | What Mnemom does for an agent. |
| verify | string | yes | How to verify signed artifacts in-band (verify, don't trust). |
| visibility_model | object | yes | Disambiguates the two axes that share the word 'public': reputation-publication visibility (public by standard) vs identity-record visibility (agent.public), plus the caller-context self-description. |
| what_we_keep_private_and_why | string | yes | – |
| who | string | yes | One-line positioning. |
No examples provided.
scan_trust ~202
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| fresh | boolean | – | Force a fresh re-scan instead of the cached result (results are cached up to 24h; the engine rate-limits re-scans). Equivalent to the scanner's rescan flag. |
| url | string | yes | Domain or URL to scan, e.g. "example.com" or "https://example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| access | object | – | The independent Access/discoverability axis (never blended with Trust). Present from the two-axis rubric (0.3.0+). |
| cached | boolean | – | True when served from the scanner's 24h cache rather than a fresh scan. |
| categories | array | – | Trust-axis categories with per-category scores + checks. |
| grade | string | yes | Trust letter grade (A+…F). |
| permalink | string | – | Shareable /r/ permalink (only on /r/ responses; transport field). |
| rubricVersion | string | – | Rubric version (e.g. "0.4.0"). |
| scannedAt | string | – | When this scorecard was produced. Results are cached up to 24h — pass fresh:true to scan_trust to force a re-scan. |
| schema | string | yes | iitr-scan schema version string (e.g. "iitr-scan/v0.N"). |
| score | number | yes | 0–100 weighted overall TRUST score. |
| signature | object | yes | Ed25519 signature over the canonical result (transport field; stripped before verify). |
| target | string | yes | Normalized host that was scanned. |
| verification | object | – | Self-describing in-band verification block {alg, kid, jwks, canonicalization} — how to verify this scorecard's signature. Self-describing, so signed-EXCLUDED (stripped before verify). |
No examples provided.
search_reputation_directory ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | string | – | Filter to agents at a given reputation-confidence level (driven by how much evidence backs the score). |
| grade | string | – | Filter to one grade (e.g. `AAA`, `B`, `NR`). |
| page | integer | – | 1-based page number for pagination. Default 1. |
| per_page | integer | – | Number of results per page. 1–100, default 20. |
| q | string | – | Name search (ilike) or agent-id prefix match. |
| sort | string | – | Result ordering. Default "score" (highest-rated first); other supported keys order by recency or name. |
| Name | Type | Req | Description |
|---|---|---|---|
| agents | array | yes | – |
| page | integer | yes | – |
| per_page | integer | yes | – |
| total | integer | yes | – |
No examples provided.
verify_reputation ~104
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent identifier (e.g. smolt-abc123) |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | – |
| computed_at | string | yes | – |
| grade | string | yes | – |
| score | number | yes | – |
| verification | object|null | yes | – |
No examples provided.
verify_scan ~182
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/.
| Name | Type | Req | Description |
|---|---|---|---|
| scan | object | – | A scan scorecard previously returned by scan_trust (or iitr's /r/ JSON), passed back verbatim to verify. Same shape as scan_trust's result; the signature is checked against mnemom://iitr/jwks. |
| url | string | – | Alternatively, a domain/URL to re-scan and then verify. |
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | yes | Always "Ed25519". |
| canonicalization | string | yes | The exact canonicalization used (so the verdict is reproducible). |
| key_id | string|null | yes | The signing key id (kid) checked. |
| reason | string | – | Why verification failed or could not be evaluated (absent when verified). |
| scorecard | object | – | The scorecard verified (present when re-scanned via `url`). |
| verified | boolean | yes | True iff the signature verifies against the in-band JWKS. |
No examples provided.
What is the Is It Trust Ready — agent-trust-readiness scanner MCP server?
Is It Trust Ready — agent-trust-readiness scanner is an MCP server listed in the public MCP registry as io.github.mnemom/isittrustready. Scan any website or MCP server for agent-trust-readiness; returns a signed, verifiable scorecard. This page covers its hosted endpoint (https://api.isittrustready.ai/mcp).
Is the Is It Trust Ready — agent-trust-readiness scanner MCP server safe to use?
Is It Trust Ready — agent-trust-readiness scanner scores 24 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Is It Trust Ready — agent-trust-readiness scanner MCP server expose?
Is It Trust Ready — agent-trust-readiness scanner exposes 8 tools: get_agent, get_reputation, get_reputation_badge, get_started, scan_trust, and 3 more. Their descriptions and schemas cost roughly 1,008 tokens of context every time the server is loaded.
Does the Is It Trust Ready — agent-trust-readiness scanner MCP server require authentication?
No. We connected to Is It Trust Ready — agent-trust-readiness scanner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Is It Trust Ready — agent-trust-readiness scanner MCP server still maintained?
Is It Trust Ready — agent-trust-readiness scanner is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.