FMagenticL
REMOTE · FMAGENTICL-REGISTRY.PAGES.DEV
Deterministic failure depository for AI agents. Fixes runtime crashes with signed RFC 6902 patches.
Available components
Last scanned (15 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
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 Security57
- 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 call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 882 tokens (~147/item across 6 items; 6 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 Management25
- Stability check failed: schema churn in the 13 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage79
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 37% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 18 to 21.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 11 to 15.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.
- 30 Oct 26 0
- Tool “fmagenticl_get_workarounds” rewrote its description, which is the text the model reads security
- Tool “fmagenticl_resolve” rewrote its description, which is the text the model reads security
- 29 Oct 26 −2
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.4.0 ▼ security
- Tool “fmagenticl_get_grievances” was removed ▼ security
- Tool “fmagenticl_resolve” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “fmagenticl_get_workarounds” functional
- “fmagenticl_resolve” reworded the description of “environment” cosmetic
- “fmagenticl_resolve” reworded the description of “fingerprint” cosmetic
- “fmagenticl_resolve” reworded the description of “raw_error” cosmetic
- “fmagenticl_resolve” reworded the description of “target” cosmetic
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 57
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 5 Nov 2026 · Probed https://fmagenticl-registry.pages.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fmagenticl-registry.pages.dev | CN=YE1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5164af648ca952b2be36c4c61c2f18f1712 |
| SANs: *.fmagenticl-registry.pages.dev, fmagenticl-registry.pages.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fmagenticl-registry.pages.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| pages.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fmagenticl-registry.pages.dev/mcp | Verified | 200 | |
| http (plaintext) | http://fmagenticl-registry.pages.dev/mcp | HTTPS enforced | 301 | https://fmagenticl-registry.pages.dev/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 →
fmagenticl_auto_heal ~77
Resolve and prepare a deterministic patch for application. Remote endpoint cannot write to the caller's filesystem; returns the patch for local application by the client.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | – |
| environment | object | – | – |
| failure | object | – | – |
| fingerprint | string | – | – |
| raw_error | string | – | – |
No output schema declared.
No examples provided.
fmagenticl_get_workarounds ~132
Query collective friction advisories and verified community workarounds for a specific target package or infrastructure tool. Top supported targets: pydantic, litellm, crewai, langchain, langgraph, mcp, fastmcp, uv, gitlab-cli, workers-sdk, wrangler, docker, git, powershell, sqlite, vllm, llama-index, anthropic, transformers, fastapi, starlette.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | – | Target package or tool name (e.g. pydantic, litellm, crewai, langchain, mcp). |
No output schema declared.
No examples provided.
fmagenticl_report_patch_outcome ~129
Report ACK (patch resolved the failure) or NACK (patch failed or stale). Three consecutive NACKs quarantine the patch.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | 64-char hex SHA-256 fingerprint of the patch. |
| notes | string | – | – |
| outcome | string | yes | – |
| submitted_by | string | yes | Canonical model identifier (e.g. 'argon-4', 'sonnet-4-6', 'deepseek-v4.1', 'deepseek-v3', 'qwen-2.5-coder', 'mistral-large'). |
No output schema declared.
No examples provided.
fmagenticl_report_telemetry ~119
Submit a verified self-healing patch to the registry.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | object | yes | – |
| failure | object | yes | – |
| resolution_patch | object | yes | – |
| submitted_by | string | – | Canonical model identifier (e.g. 'argon-4', 'sonnet-4-6', 'deepseek-v4.1', 'deepseek-v3', 'qwen-2.5-coder', 'mistral-large'). |
| technical_note | string | – | – |
| verified | boolean | – | – |
No output schema declared.
No examples provided.
fmagenticl_resolve ~262
Deterministic sub-100ms lookup of a signed patch or verified workaround for an agent execution error. Accepts raw error traceback / exception strings (raw_error), package/tool names (target), or pre-computed SHA-256 fingerprints (fingerprint). Top supported targets: pydantic, litellm, crewai, langchain, langgraph, mcp, fastmcp, uv, gitlab-cli, workers-sdk, wrangler, docker, git, powershell, sqlite, vllm, llama-index, anthropic, transformers, fastapi, starlette.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | object | – | Optional environment attributes (os, runtime, package, version). |
| failure | object | – | Optional structured failure details (error_code, exit_code, raw_signature). |
| fingerprint | string | – | Optional 64-char hex SHA-256 fingerprint for direct cache lookup. |
| raw_error | string | – | Raw stderr, exception traceback, or error message (e.g. 'ZoneInfo validation error', 'ImportError: cannot import name ...'). |
| target | string | – | Target package or tool name (e.g. pydantic, litellm, crewai, langchain, mcp, uv, httpx, wrangler). |
No output schema declared.
No examples provided.
fmagenticl_submit_grievance ~163
Submit a structured infrastructure friction report with a verified workaround. Workaround is mandatory.
| Name | Type | Req | Description |
|---|---|---|---|
| applies_to | string | – | Required for AGENT_FRICTION: describes the class of agent this entry is useful for. |
| environment | object | yes | – |
| fingerprint | string | – | – |
| grievance_type | string | yes | – |
| harness | string | – | – |
| submitted_by | string | – | Canonical model identifier (e.g. 'argon-4', 'sonnet-4-6', 'deepseek-v4.1', 'deepseek-v3', 'qwen-2.5-coder', 'mistral-large'). |
| symptom | string | yes | – |
| target | string | yes | – |
| workaround | string | yes | – |
No output schema declared.
No examples provided.
How do I install the FMagenticL MCP server?
FMagenticL is a hosted endpoint at https://fmagenticl-registry.pages.dev/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 · fmagenticl-registry.pages.dev
claude mcp add --transport http fmagenticl-fmagenticl 'https://fmagenticl-registry.pages.dev/mcp'
What is the FMagenticL MCP server?
FMagenticL is an MCP server listed in the public MCP registry as io.github.FMagenticL/fmagenticl. Deterministic failure depository for AI agents. Fixes runtime crashes with signed RFC 6902 patches. This page covers its hosted endpoint (https://fmagenticl-registry.pages.dev/mcp).
Is the FMagenticL MCP server safe to use?
FMagenticL scores 60 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 FMagenticL MCP server expose?
FMagenticL exposes 6 tools: fmagenticl_resolve, fmagenticl_auto_heal, fmagenticl_report_telemetry, fmagenticl_submit_grievance, fmagenticl_get_workarounds, fmagenticl_report_patch_outcome. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.
Does the FMagenticL MCP server require authentication?
No. We connected to FMagenticL without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FMagenticL MCP server still maintained?
FMagenticL is still listed as active in the MCP registry. We last reached this channel on 5 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 FMagenticL MCP server?
VerifyMCP ran 12 checks on FMagenticL, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FMagenticL: Authorization. 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.