
Executive Report Style Guide
io.github.Wxt-aiPublished by GitHub account Wxt-aiv1.3.0Updated Oct 15, 2026
Set the style guidance for an executive report.
Overview
Remote MCP server that lets an assistant set the style guidance used for an executive report.
- What you can do
- Set the style guidance for an executive report.
- The server exposes no documented tool list, so the exact operations are not described; the stated purpose is configuring how an executive report should be styled.
- When to use it
- Consider it when you want an assistant to apply a defined style to executive reports, for example to keep formatting and tone consistent across generated reports.
- Requirements
- A remote streamable HTTP endpoint; no authentication, environment variables or headers are declared, and no local package is needed.
Installation
In SourceWeft
- Open Executive Report Style Guide in the dashboard and add it to a workspace.
- 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-identifier/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"executive-report-style-guide": {
"type": "http",
"url": "https://determination-unlimited-consultancy-spy.trycloudflare.com/mcp/report-style-guidance-identifier"
}
}
}Tools
0Version history
3- v1.3.0LatestOct 15, 2026
- v1.1.1Oct 7, 2026
- 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.