Status Report Formatter

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.3.0Updated Oct 15, 2026

Format a status report for stakeholders.

The publisher's own server: status.live national parks

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant format a status report for stakeholders.

What you can do
This remote MCP server exposes a single capability: formatting a status report intended for stakeholders. The registry description states only that it formats a status report; no tool list, parameters, or output format are documented. It runs as a remote HTTP endpoint rather than a local package.
When to use it
Consider it when an assistant needs to turn status information into a report aimed at stakeholders. Because the description is minimal, verify the actual behavior before relying on it for anything important.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, or headers are declared. No authentication is declared, and network access to the endpoint is required.
Before you install
The endpoint is a trycloudflare.com address, a temporary tunnel hostname that may change or disappear, so availability is uncertain. No authentication is declared, so anything sent to it may not be protected; avoid sending confidential status data. The server's behavior is undocumented beyond one sentence.

Installation

In SourceWeft

  1. Open Status Report Formatter 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.Wxt-ai%2Freport-style-guidance-workbench/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": {
    "status-report-formatter": {
      "type": "http",
      "url": "https://determination-unlimited-consultancy-spy.trycloudflare.com/mcp/report-style-guidance-workbench"
    }
  }
}

Tools

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

Version history

3
  1. v1.3.0LatestOct 15, 2026
  2. v1.1.1Oct 7, 2026
  3. v1.0.4Sep 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.

Other Status integrations