io.github.Savirinc/unfragile
NPM · @UNFRAGILE/MCP-SERVER · SCANNED SEP 25
The match graph for AI. Search 100K+ capabilities across 13K+ AI artifacts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 978 tokens (~97/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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
How do I install the io.github.Savirinc/unfragile MCP server?
io.github.Savirinc/unfragile runs locally as an npm package, launched with npx -y @unfragile/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @unfragile/mcp-server
claude mcp add savirinc-unfragile -- npx -y @unfragile/mcp-server
{
"mcpServers": {
"savirinc-unfragile": {
"command": "npx",
"args": [
"-y",
"@unfragile/mcp-server"
]
}
}
} {
"servers": {
"savirinc-unfragile": {
"command": "npx",
"args": [
"-y",
"@unfragile/mcp-server"
]
}
}
} codex mcp add savirinc-unfragile -- npx -y @unfragile/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"savirinc-unfragile": {
"type": "local",
"command": [
"npx",
"-y",
"@unfragile/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add savirinc-unfragile --command npx --arg -y --arg @unfragile/mcp-server
mcp_servers:
savirinc-unfragile:
command: "npx"
args: ["-y", "@unfragile/mcp-server"] {
"McpServers": {
"savirinc-unfragile": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@unfragile/mcp-server"
]
}
}
} assistant mcp add savirinc-unfragile -t stdio -c npx -a -y @unfragile/mcp-server
{
"mcpServers": {
"savirinc-unfragile": {
"command": "npx",
"args": [
"-y",
"@unfragile/mcp-server"
]
}
}
} 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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 2026 · Analysed npm/@unfragile/mcp-server@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
compare ~81
Compare two AI artifacts side-by-side. Shows capabilities, pricing, rank, and graph signals for each. Uses search-based lookup (best-effort name matching). Use this when deciding between alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_a | string | yes | First artifact name (e.g., 'cursor') |
| artifact_b | string | yes | Second artifact name (e.g., 'windsurf') |
No output schema declared.
No examples provided.
feedback ~101
Report whether a recommended tool worked or not. This closes the learning loop — the Unfragile graph uses this feedback to improve future recommendations. Call this after trying a tool from search results.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional: brief note on why it worked or didn't |
| matchRecordId | string | yes | Match record ID from search results (shown at the bottom of search output) |
| outcome | string | yes | Did the recommended tool work for your use case? |
No output schema declared.
No examples provided.
find_mcps ~86
Find MCP servers by capability need. Use this when you need to discover MCP servers for specific integrations (e.g., databases, APIs, cloud services). Returns MCP servers ranked by capability match.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results |
| need | string | yes | What capability you need (e.g., 'Postgres database access', 'Slack messaging', 'GitHub repository management') |
No output schema declared.
No examples provided.
find_stack ~149
Assemble a complete AI harness stack for a use case. Given a description of what you're building, returns recommended tools across harness layers: orchestration, tools/MCPs, memory, guardrails, context assembly, and evaluation. This is the key differentiator — Unfragile understands that modern AI systems are composed of 5-15 tools working together.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What you're building (e.g., 'a customer support agent that connects to our Postgres database and Slack, with memory of past conversations') |
| focus | string | – | Stack focus: 'full' = all layers, 'tools-only' = just MCPs and integrations, 'infrastructure' = frameworks and platforms |
No output schema declared.
No examples provided.
get_artifact ~89
Get full details and capabilities for a specific AI artifact by name or slug. Uses search-based lookup (best-effort name matching — may return a different artifact for ambiguous names like 'express'). Use this to understand what an artifact can do before adding it to your stack.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Artifact name or slug (e.g., 'cursor', 'langchain', 'claude-code') |
No output schema declared.
No examples provided.
resolve_capability ~126
Resolve a capability:// URI or natural-language capability into ranked AI artifacts. This is Unfragile's capability DNS primitive. Use when an agent knows what capability it needs and must choose the safest current artifact at runtime.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | Capability URI or phrase, e.g. 'capability://database.postgres.query.readonly' or 'read-only Postgres database access' |
| limit | number | – | Max resolutions |
| risk | string | – | Risk posture. production/enterprise/strict require stronger quality/status gates. |
| type | string | – | Filter by artifact type |
No output schema declared.
No examples provided.
search ~98
Search the Unfragile match graph for AI tools, frameworks, APIs, MCP servers, agents, and more. Returns ranked results with capability matches and graph signals. Every query feeds the graph.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return |
| query | string | yes | What you're looking for (e.g., 'best framework for building AI agents', 'MCP server for database access') |
| type | string | – | Filter by artifact type |
No output schema declared.
No examples provided.
subscribe ~117
Set up a persistent watch for new AI tools matching a query. Get notified daily when something new appears in the Unfragile graph. Requires at least one notification channel (email or webhook).
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Email address for notifications | |
| query | string | yes | What to watch for (e.g., 'new MCP server for Postgres', 'framework for building AI agents') |
| type | string | – | Only watch for this artifact type |
| webhook | string | – | Webhook URL for notifications (receives POST with new matches) |
No output schema declared.
No examples provided.
trust_passport ~90
Get the machine-readable trust passport for an AI artifact. Use this before an agent selects a tool, API, MCP server, model, repo, or framework for a task. Returns capability URIs, permissions, data access risk, known failure modes, observed outcomes, and trust score.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Artifact slug (e.g., 'cursor', 'claude-code', 'langchain') |
No output schema declared.
No examples provided.
unsubscribe ~41
Cancel a persistent watch (monitor). Use the monitor ID returned from subscribe.
| Name | Type | Req | Description |
|---|---|---|---|
| monitorId | string | yes | Monitor ID from subscribe (e.g., 'mon_...') |
No output schema declared.
No examples provided.
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. The match graph for AI. Search 100K+ capabilities across 13K+ AI artifacts. This page covers its npm package (@unfragile/mcp-server).
Is the io.github.Savirinc/unfragile MCP server safe to use?
io.github.Savirinc/unfragile scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 10 tools: search, find_mcps, get_artifact, resolve_capability, trust_passport, and 5 more. Their descriptions and schemas cost roughly 978 tokens of context every time the server is loaded.
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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Savirinc/unfragile MCP server under?
io.github.Savirinc/unfragile declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.