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.
npx agentmods add mcp/starling-browser/starling/aspiregit clone --depth 1 https://github.com/starling-browser/starlingWrote 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/starling-browser/starling/aspire)<a href="https://agentmods.dev/mcp/starling-browser/starling/aspire"><img src="https://agentmods.dev/badge/mcp/starling-browser/starling/aspire.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
aspire 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 5d 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.
This is a copy
100% identical to aspire — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"aspire": {
"command": "aspire",
"args": [
"agent",
"mcp"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 5d ago First seen · 9 lines scan A 61dae4608f12
aspire is an MCP server published in the GitHub repository starling-browser/starling (57 stars, last pushed 1mo 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. It is 100% identical to aspire, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
design-copier
MCP server "design-copier" as configured in chipsxp/design-copier. Runs locally from the design-copier npm package.
generator-agent
MCP server "generator-agent" as configured in Azure/azure-sdk-for-net. Launched with dotnet run --project sdk/tools/Azure.GeneratorAgent/src/Azure.GeneratorAgent.csp.
xaf-logic-explainer
MCP server "xaf-logic-explainer" as configured in peopleworks/XAFLogicExplainer. Launched with XafLogicExplainer.Mcp. Needs 1 environment variable to run.
resharper-cli-mcp
MCP server "resharper-cli-mcp" as configured in andypgray/resharper-cli-mcp. Launched with Zphil.ReSharperCli. Needs 9 environment variables to run.
groupdocs-metadata-mcp
MCP server "groupdocs-metadata-mcp" as configured in groupdocs-metadata/GroupDocs.Metadata.Mcp. Launched with GroupDocs.Metadata.Mcp. Needs 3 environment variables to run.
layout-doctor-mcp
MCP server "layout-doctor-mcp" as configured in h-kazuki-pixel/layout-doctor-mcp. Runs locally from the layout-doctor-mcp npm package.