
State Of Company Publisher
io.github.dailyaiagents-cpuPublished by GitHub account dailyaiagents-cpuv0.1.0Updated Oct 24, 2026
Sundays 18:00 CDT. Composes a public state-of-the-company narrative covering the past 7 days — wh...
Overview
A local desktop MCP server that composes a public state-of-the-company narrative covering the past seven days, apparently on a weekly Sunday schedule.
- What you can do
- Composes a public state-of-the-company narrative covering the past seven days, based on the registry description. The description is truncated, so the full set of capabilities and any tools it exposes are not documented. It runs as a local process on the user's machine with no declared tools, packages, or authentication.
- When to use it
- Consider it only if you want an assistant to help draft a recurring weekly public company update. Because the description is cut off and no tools or README are provided, most users should wait for fuller documentation before installing.
- Requirements
- Runs as a local desktop process over stdio. No packages, environment variables, headers, or authentication are declared, so the actual runtime requirements are unknown.
Installation
In SourceWeft
- Open State Of Company Publisher in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
35% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 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.
- License10 pts