FMagenticL

io.github.FMagenticLPublished by GitHub account FMagenticLv1.0.0Updated Oct 24, 2026

Deterministic failure depository for AI agents. Fixes runtime crashes with signed RFC 6902 patches.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant look up signed patches or verified workarounds for runtime failures and report patch outcomes to a shared registry.

What you can do
fmagenticl_resolve performs deterministic sub-100ms lookup of a signed patch or verified workaround, accepting an exact 64-character SHA-256 fingerprint, a raw error string, or a target tool name (T1.1, T1.2). fmagenticl_auto_heal resolves and prepares a deterministic patch for application, returning it for local application because the remote endpoint cannot write to the caller's filesystem (T2.1, T2.2). fmagenticl_report_telemetry submits a verified self-healing patch, fmagenticl_submit_grievance files a structured infrastructure friction report with a mandatory workaround, fmagenticl_get_grievances queries open grievances and workarounds for a target, and fmagenticl_report_patch_outcome,
When to use it
Use it when an assistant hits a runtime crash or recurring infrastructure failure and needs a deterministic, signed fix or a verified workaround rather than improvising one. It also fits workflows that want to contribute verified patches or friction reports back to a shared registry and track whether a patch resolved the failure. It is less useful when failures are unique to your environment and no matching fingerprint, error string, or tool name exists in the registry.
Requirements
A remote streamable HTTP endpoint at no package, runtime, account, API key, environment variable, or header is declared. Network access to that endpoint is required. The endpoint cannot write to the caller's filesystem, so the client must apply returned patches locally.
Before you install
The server is a shared registry: fmagenticl_report_telemetry and fmagenticl_submit_grievance send your patch or friction report to a third party, and fmagenticl_report_patch_outcome records ACK or NACK, with three consecutive NACKs quarantining a patch (T6.2). Submitted workarounds and error strings may contain sensitive details, so review them before sending. Patches are returned for local application, so inspect a patch before applying it to your own filesystem.

Installation

In SourceWeft

  1. Open FMagenticL in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.FMagenticL%2Ffmagenticl/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fmagenticl": {
      "type": "http",
      "url": "https://fmagenticl-registry.pages.dev/mcp"
    }
  }
}

Tools

6

fmagenticl_resolve

Deterministic sub-100ms lookup of a signed patch or verified workaround for a failure. Accepts exact 64-char SHA-256 fingerprint, raw error string, or target tool name.

Parameterstargetfailureraw_errorenvironmentfingerprint

fmagenticl_auto_heal

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.

Parameterscontextfailureraw_errorenvironmentfingerprint

fmagenticl_report_telemetry

Submit a verified self-healing patch to the registry.

Parametersfailurerequiredverifiedenvironmentrequiredsubmitted_bytechnical_noteresolution_patchrequired

fmagenticl_submit_grievance

Submit a structured infrastructure friction report with a verified workaround. Workaround is mandatory.

Parameterstargetrequiredharnesssymptomrequiredapplies_toworkaroundrequiredenvironmentrequiredfingerprintsubmitted_bygrievance_typerequired

fmagenticl_get_grievances

Query open grievances and workarounds for a specific infrastructure target.

Parameterstargetrequired

fmagenticl_report_patch_outcome

Report ACK (patch resolved the failure) or NACK (patch failed or stale). Three consecutive NACKs quarantine the patch.

Parametersnotesoutcomerequiredfingerprintrequiredsubmitted_byrequired

Version history

1
  1. v1.0.0LatestOct 24, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.