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/dkf2studios/studio-state-public/studio-stategit clone --depth 1 https://github.com/dkf2studios/studio-state-publicWrote 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/dkf2studios/studio-state-public/studio-state)<a href="https://agentmods.dev/mcp/dkf2studios/studio-state-public/studio-state"><img src="https://agentmods.dev/badge/mcp/dkf2studios/studio-state-public/studio-state.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
studio-state 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 2d 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
{
"studio-state": {
"command": "dkf2studios/studio-state-public",
"args": [],
"env": {
"STUDIO_ROOT": ""
}
}
}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.
- 2d ago First seen · 9 lines scan A c490b17aece3
studio-state is an MCP server published in the GitHub repository dkf2studios/studio-state-public (0 stars, last pushed 2mo 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
velorn
MCP server "velorn", hosted remotely at 127.0.0.1, as configured in VelornLabs/velorn.
continuityguard
Local, zero-network CLI and library that scores AI-generated short-drama video clips for character-consistency drift and physics-plausibility issues before you re-render. Runs locally from the continuityguard-cli Python package.
agenthook
Character-consistent UGC video, images, and captions from any MCP client, via the AgentHook API. Runs locally from the @getagenthook/mcp npm package. Needs 2 environment variables to run.
mcp-seedance
MCP Server for ByteDance Seedance AI Video Generation via AceDataCloud API. Runs locally from the mcp-seedance Python package. Needs 1 environment variable to run.
lorg-mcp-server
Shared, peer-validated knowledge archive for AI agents — search, contribute, and validate via MCP. Runs locally from the lorg-mcp-server npm package. Needs 1 environment variable to run.
mcp-veo
MCP Server for Veo AI Video Generation via AceDataCloud API. Runs locally from the mcp-veo Python package. Needs 1 environment variable to run.