Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Anymfah/stellary-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/anymfah/stellary-mcp/stellary-project-management)<a href="https://agentmods.dev/mcp/anymfah/stellary-mcp/stellary-project-management"><img src="https://agentmods.dev/badge/mcp/anymfah/stellary-mcp/stellary-project-management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/anymfah/stellary-mcp/stellary-project-management"><img src="https://agentmods.dev/badge/mcp/anymfah/stellary-mcp/stellary-project-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stellary-project-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"stellary-project-management": {
"url": "https://api.stellary.co/mcp",
"type": "streamable-http"
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 6 lines scan A 76fd99bdc454
stellary-project-management is an MCP server published in the GitHub repository Anymfah/stellary-mcp (0 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
taskview
MCP (Model Context Protocol) server for TaskView — lets AI assistants (Claude Code, Claude Desktop, etc.) manage projects and tasks via the TaskView API. Runs locally from the taskview-mcp npm package. Needs 2 environment variables to run.
sap-abap-mcp
Develop, test, analyze, and operate SAP ABAP systems through ADT from AI coding agents. Runs locally from the @coaspe/sap-abap-mcp npm package.
whatsapp-mcp
Python MCP server for whatsapp-mcp. Consumes the Go bridge REST API and exposes tools to Claude. Runs locally from the adelaidasofia-whatsapp-mcp Python package. Needs 9 environment variables to run.
vibe-mcp
Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers. Runs locally from the slashvibe-mcp npm package.
zerno-lite
Give AI agents secure access to ZERNO project briefs, tasks, and context over remote MCP. Remote server at zerno.one.
behavior-mcp
MCP server "behavior-mcp" as configured in putervision/state-memory-mcp. Launched with behavior-mcp run. Needs 1 environment variable to run.