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/score-technologies/score-studio-agent-plugins/score-studio-score-studiogit clone --depth 1 https://github.com/score-technologies/score-studio-agent-pluginsWrote 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/score-technologies/score-studio-agent-plugins/score-studio-score-studio)<a href="https://agentmods.dev/mcp/score-technologies/score-studio-agent-plugins/score-studio-score-studio"><img src="https://agentmods.dev/badge/mcp/score-technologies/score-studio-agent-plugins/score-studio-score-studio.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
score-studio 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 4d 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
{
"score-studio": {
"command": "npx",
"args": [
"-y",
"@score-technologies/score-studio-mcp"
],
"env": {
"SCORESTUDIO_TOKEN": "${SCORESTUDIO_TOKEN}"
}
}
}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.
- 4d ago First seen · 12 lines scan A 807283475eef
score-studio is an MCP server published in the GitHub repository score-technologies/score-studio-agent-plugins (0 stars, last pushed 3d 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
grpvn
MCP server "grpvn" as configured in frane/grpvn. Launched with grpvn serve.
anyapi
MCP server "anyapi", hosted remotely at api.getanyapi.com, as configured in getanyapi-com/skills.
horizon-shield-webmcp
Agent intake desk for property renovation. Read only, CORS open, fail closed, receipts recompute. Remote server at web.horizonshield.dev.
hs-audit-app
MCP server "hs-audit-app", hosted remotely at hs-audit-app.oga-surf-project.workers.dev, as configured in ogasurfproject-jpg/horizon-shield.
bring-photo-mcp
Add products to Bring! from a photo — MCP for AI recognition, catalog matching, and verified writes. Runs locally from the bring-photo-mcp npm package. Needs 8 environment variables to run.
toolrouter
MCP server "toolrouter", hosted remotely at api.toolrouter.com, as configured in Humanleap/toolrouter-mcp.