unfragile MCP server
io.github.Savirinc/unfragileSavirincstreamable-httpv0.13.0Scanned
Find the AI infrastructure or agent tool for a task, labelled by our checks, with signed receipts.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the unfragile MCP server can do
The unfragile MCP server is published by the GitHub account Savirinc. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
2 tools bring in text other people can write (unfragile_find and unfragile_verify).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.13.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
unfragile_findFinds 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…Reads text others writeNo findings
Why it is in this group
- The name "unfragile_find" says "find": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "find" and "browser": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
unfragile_passportFetch the raw Ed25519-signed trust passport JSON for a record (by record page slug, record id, or npm package).No findings
Why it is in this group
- The description's first verb is "fetch": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
unfragile_resolveReturns one checked record for a task, with its verdict, its Ed25519-signed passport and a paste-ready install line, or says that nothing qualifies.No findings
Why it is in this group
- The name "unfragile_resolve" says "resolve": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
unfragile_verifyReturns 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://…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "return": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:19 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:unfragile_resolveOnly readsdescription
Install
Pinned to version 0.13.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http unfragile https://unfragile.ai/api/mcpclaude mcp add --transport http unfragile https://unfragile.ai/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__unfragile__unfragile_find",
"mcp__unfragile__unfragile_verify",
"mcp__unfragile__unfragile_resolve",
"mcp__unfragile__unfragile_passport"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as unfragile. Review it before you use it.
Capability tags behind 2 rules
- mcp__unfragile__unfragile_find untrusted-input
- mcp__unfragile__unfragile_verify untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Savirinc/unfragile/verify?hash=4b6ddce1f1bd619051f15f47d1264aeca815073bff3ff6a84e4ee2b365d16667" | jq -e '.changed == false'Pinned hash 4b6ddce1f1bd, from Nov 20, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Savirinc/unfragile/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Savirinc/unfragile)Source: MCP Registry · repository. Synced Nov 20, 2026, 10:17 UTC.
unfragile MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the unfragile MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the unfragile MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the unfragile MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the unfragile MCP server have?
- 4 tools: 4 read. unfragile_find, unfragile_verify, unfragile_resolve and unfragile_passport.
Does the unfragile MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the unfragile MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the unfragile MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.