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/sjkim1127/Reversecore_MCPWrote 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/sjkim1127/reversecore_mcp/reversecore-mcp)<a href="https://agentmods.dev/mcp/sjkim1127/reversecore_mcp/reversecore-mcp"><img src="https://agentmods.dev/badge/mcp/sjkim1127/reversecore_mcp/reversecore-mcp/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/sjkim1127/reversecore_mcp/reversecore-mcp"><img src="https://agentmods.dev/badge/mcp/sjkim1127/reversecore_mcp/reversecore-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
reversecore-mcp 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 1mo 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
{
"reversecore-mcp": {
"command": "uvx",
"args": [
"reversecore-mcp"
],
"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.
- 1mo ago First seen · 9 lines scan A c58751c52b33
reversecore-mcp is an MCP server published in the GitHub repository sjkim1127/Reversecore_MCP (214 stars, last pushed 6d 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-30.
Other mcp servers, from other repositories
rbinmcp
MCP server "rbinmcp" as configured in kirkderp/rbinmcp. Runs in Docker (ghcr.io/kirkderp/rbinmcp:1.3.0).
mastyf.ai
Runtime proxy for MCP security, cost governance & audit. Runs locally from the @mastyf_ai/server npm package. Needs 3 environment variables to run.
mcp-scribe
Transcribe any OpenAPI schema into a production-grade MCP server. Runs locally from the mcp-scribe Python package.
attestd-mcp
CVE checks, supply chain signals, live catalog, and CVE detail for MCP clients (infra, PyPI, npm). Runs locally from the @attestd/mcp npm package. Needs 2 environment variables to run.
sqlite
MCP server "sqlite" as configured in alexmmatos/arthur-mcp. Runs locally from the mcp-server-sqlite-npx npm package.
mcp-fortress
MCP server "mcp-fortress", hosted remotely at server.smithery.ai, as configured in mcp-fortress/mcp-fortress.