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/prathamesh-git9/mcp-serversWrote 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/prathamesh-git9/mcp-servers/prathamesh-mcp-servers-workspace)<a href="https://agentmods.dev/mcp/prathamesh-git9/mcp-servers/prathamesh-mcp-servers-workspace"><img src="https://agentmods.dev/badge/mcp/prathamesh-git9/mcp-servers/prathamesh-mcp-servers-workspace/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/prathamesh-git9/mcp-servers/prathamesh-mcp-servers-workspace"><img src="https://agentmods.dev/badge/mcp/prathamesh-git9/mcp-servers/prathamesh-mcp-servers-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
prathamesh-mcp-servers-workspace 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
{ "prathamesh-mcp-servers-workspace": { "command": "uvx", "args": [ "prathamesh-mcp-servers-workspace" ] } }
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 · 8 lines scan A 112f5a575f67
prathamesh-mcp-servers-workspace is an MCP server published in the GitHub repository prathamesh-git9/mcp-servers (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
laravel-boost
MCP server "laravel-boost" as configured in David-Crty/databasement. Runs in Docker (boost:mcp).
obsidian-hybrid-search
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval. Runs locally from the obsidian-hybrid-search npm package. Needs 10 environment variables to run.
state-memory-mcp
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers. Runs locally from the @putervision/state-memory-mcp npm package.
mooncite
MCP server "mooncite" as configured in WhenMoon-afk/claude-memory-mcp. Runs dist/cli.js with node.
mcp-sqlite-tools
MCP server for local SQLite database operations. Runs locally from the mcp-sqlite-tools npm package.
mcp-memory-sqlite
SQLite-based persistent memory tool for MCP with text search. Runs locally from the mcp-memory-sqlite npm package.