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/Dongwu259/photo_sWrote 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/dongwu259/photo_s/photo-s)<a href="https://agentmods.dev/mcp/dongwu259/photo_s/photo-s"><img src="https://agentmods.dev/badge/mcp/dongwu259/photo_s/photo-s/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/dongwu259/photo_s/photo-s"><img src="https://agentmods.dev/badge/mcp/dongwu259/photo_s/photo-s.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
photo-s 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 2mo 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
{
"photo-s": {
"command": "uvx",
"args": [
"photo-s-tools",
"photo-s-tools[mcp]",
"photo-s"
],
"env": {}
}
}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.
- 2mo ago First seen · 11 lines scan A 6555abc06d69
photo-s is an MCP server published in the GitHub repository Dongwu259/photo_s (0 stars, last pushed 1mo 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
bibverify
Verify, repair, and enrich BibTeX references across academic metadata providers. Runs locally from the bibverify Python package.
commit-discipline-mcp
Plan and enforce small, test-gated Git commits through MCP or a CLI. Runs locally from the commit-discipline-mcp npm package.
llmscout
Zero-dependency, cross-platform LLM/GEO/AEO checker CLI. 21 checks, pure Python stdlib, no runtime dependencies. Runs locally from the llmscout-cli Python package.
filepulse-cli
MCP server "filepulse-cli" as configured in gitstq/FilePulse-CLI. Runs locally from the filepulse-cli Python package.
bottari
MCP server "bottari" as configured in dostevskii/bottari. Runs locally from the bottari npm package.
repl-mcp
Universal REPL session manager MCP server. Runs locally from the repl-mcp npm package.