Ironfang

uk.ironfangPublished by ironfang.ukOfficial publisherv1.0.0Updated Oct 24, 2026

Screenshots, PDFs, QR codes, clips and template renders with a normal OAuth sign-in.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

Ironfang is a remote MCP server that lets an assistant produce screenshots, PDFs, QR codes, clips and template renders after a normal OAuth sign-in.

What you can do
Generate screenshots and PDFs from content the assistant supplies or references, according to the registry description. Create QR codes and short clips. Render templates into finished output. Access is granted through an OAuth sign-in rather than an API key.
When to use it
Useful when you want an assistant to turn text or templates into shareable artifacts such as screenshots, PDFs, QR codes or short clips without running local tooling.
Requirements
A remote MCP endpoint at over streamable HTTP, plus an OAuth sign-in. No packages, environment variables or headers are declared.
Before you install
The server is remote, so the content you send for rendering leaves your machine and is processed by a third party. It requires an OAuth sign-in, which grants it access tied to your account. No tool list is published, so confirm what it can read or change before relying on it.

Installation

In SourceWeft

  1. Open Ironfang 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/uk.ironfang%2Fironfang/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": {
    "ironfang": {
      "type": "http",
      "url": "https://mcp.ironfang.uk/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

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