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/oaslananka/mcp-suiteWrote 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/oaslananka/mcp-suite/composer-composer)<a href="https://agentmods.dev/mcp/oaslananka/mcp-suite/composer-composer"><img src="https://agentmods.dev/badge/mcp/oaslananka/mcp-suite/composer-composer/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/oaslananka/mcp-suite/composer-composer"><img src="https://agentmods.dev/badge/mcp/oaslananka/mcp-suite/composer-composer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
composer 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 9d 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
{
"composer": {
"command": "npx",
"args": [
"-y",
"@oaslananka/composer"
],
"env": {
"COMPOSER_CONFIG": ""
}
}
}What else server.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.
- 9d ago First seen · 12 lines scan A a8a5e90dd0fa
composer is an MCP server published in the GitHub repository oaslananka/mcp-suite (2 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. 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
zapier-dev-mcp
For Zapier integration developers: inspect, lint, and validate zapier-platform-cli projects. Runs locally from the zapier-dev-mcp npm package.
performance_profiler
MCP server "performanceprofiler" as configured in probelabs/visor. Runs ./tools/performance-analyzer.js with node. Needs 2 environment variables to run.
dependency_checker
Check for outdated, incorrect, and unused dependencies. Runs locally from the npm-check npm package. Needs 1 environment variable to run.
sage
Local-first command wrapper for AI coding agents with compressed terminal output and privacy-safe proof metrics. Runs locally from the psycgod-sage Python package.
gha-doctor
MCP server "gha-doctor" as configured in linnea-bakshi/gha-doctor. Runs in Docker (ghcr.io/linnea-bakshi/gha-doctor:0.61.0). Needs 1 environment variable to run.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.