Stack Trace Medic

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Coded error stack trace debugger and automated patch generator.

VerifiedSSEWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP server that debugs coded error stack traces and generates automated patches for them.

What you can do
Analyzes coded error stack traces to help diagnose failures in code. Generates automated patches as suggested fixes. Premium settlement is handled through a payment signature header.
When to use it
Useful when an assistant needs help interpreting a stack trace or proposing a patch for a coded error, rather than debugging by hand.
Requirements
A remote SSE endpoint; no local package or runtime is needed. Premium settlement requires the payment-signature header, a Base64-encoded EIP-3009 TransferWithAuthorization signature.
Before you install
The server asks for a payment-signature header, a cryptographic authorization signature tied to a blockchain-style transfer; supplying it can authorize a payment. Treat that signature as sensitive and only provide it when you intend to pay. Stack traces may contain source paths or other internal details.

Installation

In SourceWeft

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

Web executable via SSE. 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.Evozim%2Fstack-trace-medic/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": {
    "stack-trace-medic": {
      "type": "sse",
      "url": "https://stack-trace-medic-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    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.