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/AstravueOrg/astravue-mcp-serverWrote 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/astravueorg/astravue-mcp-server/astravue-mcp)<a href="https://agentmods.dev/mcp/astravueorg/astravue-mcp-server/astravue-mcp"><img src="https://agentmods.dev/badge/mcp/astravueorg/astravue-mcp-server/astravue-mcp/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/astravueorg/astravue-mcp-server/astravue-mcp"><img src="https://agentmods.dev/badge/mcp/astravueorg/astravue-mcp-server/astravue-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
astravue-mcp 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 11d 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
{
"astravue-mcp": {
"url": "https://api.astravue.com/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.
- 11d ago First seen · 6 lines scan A 3d7626452340
astravue-mcp is an MCP server published in the GitHub repository AstravueOrg/astravue-mcp-server (12 stars, last pushed 17d ago), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
azure-devops-mcp
Model Context Protocol server for Azure DevOps integration - enables Claude to interact with work items, projects, and boards. Runs locally from the @jybrd/azure-devops-mcp npm package.
task-master-ai
A task management system for ambitious AI-driven development that doesn't overwhelm and confuse Cursor. Runs locally from the task-master-ai npm package. Needs 9 environment variables to run.
autotask-mcp
MCP server "autotask-mcp" as configured in WYRE-AI/autotask-mcp. Runs in Docker (ghcr.io/wyre-ai/autotask-mcp:v2.33.0). Needs 7 environment variables to run.
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in WYRE-AI/connectwise-manage-mcp. Runs in Docker (ghcr.io/wyre-ai/connectwise-manage-mcp:v1.8.8). Needs 8 environment variables to run.
syncro-mcp
MCP server "syncro-mcp" as configured in WYRE-AI/syncro-mcp. Runs in Docker (ghcr.io/wyre-ai/syncro-mcp:v1.4.9). Needs 5 environment variables to run.
halopsa-mcp
MCP server "halopsa-mcp" as configured in WYRE-AI/halopsa-mcp. Runs in Docker (ghcr.io/wyre-ai/halopsa-mcp:v1.7.13). Needs 7 environment variables to run.