Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Savirinc/unfragile

REMOTE · UNFRAGILE.AI · 2 COMPONENTS

Find the AI infrastructure or agent tool for a task, labelled by our checks, with signed receipts.

72 Trust /100

Last scanned (14 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 735 tokens (~183/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Nov 26 71

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://unfragile.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=unfragile.ai CN=YR1,O=Let's Encrypt,C=US 2 Nov 2026 31 Jan 2027 RSA 2048 SHA256-RSA 51dbe1ae43f6ed5270de6b470f1215a63c9
SANs: unfragile.ai
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of unfragile.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
unfragile.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://unfragile.ai/api/mcp Verified 200
http (plaintext) http://unfragile.ai/api/mcp HTTPS enforced 308 https://unfragile.ai/api/mcp
MCP tools · 4 exposed · ~666 tokens

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 →

Tool Tokens
unfragile_find ~429

Finds the product, and the specific tool action, that does a task, across AI infrastructure (search APIs, models, inference, browsers, harnesses, compute) and the MCP servers, APIs, CLIs, SDKs and models in our index. Each result carries the label from our checks (verified and signed · official · checked: not enough evidence yet · found in code, not yet checked · demo or tutorial · failed its last check) and a signed receipt. answer: true adds a written, cited answer; false returns the ranked list. A fact we hold (a price, a limit, a model id) arrives in structuredContent.blocks (type 'fact') and at the start of the answer, never in results.

NameTypeReqDescription
answerboolean–Also return a written answer: the products that do it, each cited to its maker's own pages. Default here: true (this door has always answered); false lists the products without writing
client_modelstring–The model that will read the answer (recorded on the receipt)
intentstring–Deprecated: the old name of `kind` (kept so 0.10 callers work)
kindstring–With search: 'product' (which product does X), 'action' (the one operation to call) or 'model' (which AI model)
lanestring–fast: ranked results only · standard: results and a written, cited answer (default) · best: a freshly written answer
limitinteger–How many results (default 5)
max_ageinteger–Seconds: a remembered answer older than this is written afresh
namedarray–With search: products the task names, so they lead
searchstring–Optional: your own 3-10 word search phrase; skips our reading step
session_idstring–Your own id for this task (recorded on the receipt)
taskstringyesWhat you need done, in plain words

No output schema declared.

No examples provided.

unfragile_passport ~72

Fetch the raw Ed25519-signed trust passport JSON for a record (by record page slug, record id, or npm package). For programmatic policy checks; verify offline against the published public key.

NameTypeReqDescription
slugstringyesRecord page slug, record id (npm:…), or package name

No output schema declared.

No examples provided.

unfragile_resolve ~64

Returns one checked record for a task, with its verdict, its Ed25519-signed passport and a paste-ready install line, or says that nothing qualifies.

NameTypeReqDescription
intentstringyesThe task, e.g. 'send a slack message from an agent'

No output schema declared.

No examples provided.

unfragile_verify ~101

Returns our verdict on a tool, MCP server or package (trusted · caution · unverified · flagged) and the reason, with its Ed25519-signed passport, checkable offline against https://unfragile.ai/api/v1/trust-passport-public-key. A flagged verdict means it failed our checks.

NameTypeReqDescription
targetstringyesTarget identity, e.g. 'npm:@stripe/mcp', a package name, or a record id

No output schema declared.

No examples provided.

Install

How do I install the io.github.Savirinc/unfragile MCP server?

io.github.Savirinc/unfragile is a hosted endpoint at https://unfragile.ai/api/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 · unfragile.ai

# add to Claude Code
claude mcp add --transport http savirinc-unfragile 'https://unfragile.ai/api/mcp'
Common questions

What is the io.github.Savirinc/unfragile MCP server?

io.github.Savirinc/unfragile is an MCP server listed in the public MCP registry as io.github.Savirinc/unfragile. Find the AI infrastructure or agent tool for a task, labelled by our checks, with signed receipts. This page covers its hosted endpoint (https://unfragile.ai/api/mcp).

Is the io.github.Savirinc/unfragile MCP server safe to use?

io.github.Savirinc/unfragile scores 72 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 io.github.Savirinc/unfragile MCP server expose?

io.github.Savirinc/unfragile exposes 4 tools: unfragile_find, unfragile_verify, unfragile_resolve, unfragile_passport. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.

Does the io.github.Savirinc/unfragile MCP server require authentication?

No. We connected to io.github.Savirinc/unfragile without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.Savirinc/unfragile MCP server still maintained?

io.github.Savirinc/unfragile is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.Savirinc/unfragile MCP server?

VerifyMCP ran 13 checks on io.github.Savirinc/unfragile, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.