Stakeholder Report Publisher

io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.0.7Updated Oct 8, 2026

Build a stakeholder configuration report

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP endpoint that lets an assistant build a stakeholder configuration report.

What you can do
The server exposes a single described capability: building a stakeholder configuration report. No tool list, parameters, or output format are documented in the available material, so the exact operations it offers are not known. It is reached as a remote streamable HTTP endpoint rather than a local package.
When to use it
Consider it when an assistant needs to produce a stakeholder configuration report and you are willing to rely on an undocumented remote service. Because so little is published about its tools, it is hard to judge fit in advance.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables, headers, or authentication are declared. Network access to the provider's endpoint is required.
Before you install
The endpoint is a third-party remote service with no declared authentication, so anything sent to it leaves your machine and its handling is not described. The report content and any data the assistant supplies may be transmitted to that service. No tool list is published, so review what it actually does before use.

Installation

In SourceWeft

  1. Open Stakeholder Report Publisher 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%2Fstakeholder-report-publisher/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": {
    "stakeholder-report-publisher": {
      "type": "http",
      "url": "https://openings-vote-drilling-initially.trycloudflare.com/mcp/stakeholder-report-publisher"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.7LatestSep 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.