Skip to content

FMagenticL MCP server

io.github.FMagenticL/fmagenticlFMagenticLstreamable-httpv1.0.0Scanned

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

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the FMagenticL MCP server can do

The FMagenticL MCP server is published by the GitHub account FMagenticL. It has 6 tools. It can create or change data (3 tools: fmagenticl_report_telemetry, fmagenticl_submit_grievance and fmagenticl_report_patch_outcome), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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 8, 2026, version 1.0.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.

6 tools

Changes things 3Claude Code: ask
  • fmagenticl_report_patch_outcomeReport ACK (patch resolved the failure) or NACK (patch failed or stale).No findings

    Why it is in this group

    • The name "fmagenticl_report_patch_outcome" says "patch": a word for a change.
    Description, as the server wrote it
    Report ACK (patch resolved the failure) or NACK (patch failed or stale). Three consecutive NACKs quarantine the patch.
  • fmagenticl_report_telemetrySubmit a verified self-healing patch to the registry.No findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.
    Description, as the server wrote it
    Submit a verified self-healing patch to the registry.
  • fmagenticl_submit_grievanceSubmit a structured infrastructure friction report with a verified workaround.No findings

    Why it is in this group

    • The name "fmagenticl_submit_grievance" says "submit": a word for a change.
    Description, as the server wrote it
    Submit a structured infrastructure friction report with a verified workaround. Workaround is mandatory.
Only reads 3Show 3 read-only tools
  • fmagenticl_auto_healResolve and prepare a deterministic patch for application.No findings

    Why it is in this group

    • The description's first verb is "resolve": a word for reading.
    Description, as the server wrote it
    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.
  • fmagenticl_get_workaroundsQuery collective friction advisories and verified community workarounds for a specific target package or infrastructure tool.No findings

    Why it is in this group

    • The name "fmagenticl_get_workarounds" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • fmagenticl_resolveDeterministic sub-100ms lookup of a signed patch or verified workaround for an agent execution error.No findings

    Why it is in this group

    • The name "fmagenticl_resolve" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Nov 8, 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
3
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://fmagenticl-registry.pages.dev/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://fmagenticl-registry.pages.dev/mcp: tools/list returned 6 tools to an anonymous client, including fmagenticl_report_telemetry (write), fmagenticl_submit_grievance (write), fmagenticl_report_patch_outcome (write)

    What this check looks for

Posture changes

  1. Nov 8, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-03-26
    • RFC 9728 protected resource metadata: none to https://fmagenticl-registry.pages.dev/.well-known/oauth-protected-resource/mcp
  2. Oct 31, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-03-26 to none

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.

  1. Tools1 added, 1 removed, 1 changed.+1 added−1 removed~1 changedView diff
  2. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 200; tools/list served without credentials: no -> yes (and 3 more).View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 3
    • Protocol version: none to 2025-03-26
    • RFC 9728 protected resource metadata: none to https://fmagenticl-registry.pages.dev/.well-known/oauth-protected-resource/mcp
  3. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 3 to 0
    • Protocol version: 2025-03-26 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http fmagenticl https://fmagenticl-registry.pages.dev/mcp
claude mcp add --transport http fmagenticl https://fmagenticl-registry.pages.dev/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__fmagenticl__fmagenticl_resolve",
      "mcp__fmagenticl__fmagenticl_auto_heal",
      "mcp__fmagenticl__fmagenticl_get_workarounds"
    ],
    "ask": [
      "mcp__fmagenticl__fmagenticl_report_telemetry",
      "mcp__fmagenticl__fmagenticl_submit_grievance",
      "mcp__fmagenticl__fmagenticl_report_patch_outcome"
    ],
    "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 fmagenticl. Review it before you use it.

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.FMagenticL/fmagenticl/verify?hash=c0855b0e1d1fdc6a0f0215fcba289aa940cfa0327ab7638d80188fdfc54fa32b" | jq -e '.changed == false'

Pinned hash c0855b0e1d1f, from Nov 8, 2026, 22: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.FMagenticL/fmagenticl/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.FMagenticL/fmagenticl
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.FMagenticL/fmagenticl.svg)](https://radar.anlyon.com/servers/io.github.FMagenticL/fmagenticl)

Source: MCP Registry. Synced Oct 23, 2026, 22:17 UTC.

FMagenticL MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the FMagenticL MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the FMagenticL MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the FMagenticL 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 FMagenticL MCP server have?

6 tools: 3 write, 3 read. fmagenticl_report_telemetry, fmagenticl_submit_grievance, fmagenticl_report_patch_outcome, fmagenticl_resolve, fmagenticl_auto_heal and fmagenticl_get_workarounds.

Does the FMagenticL MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the FMagenticL MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the FMagenticL MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.