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/edithatogo/sourcerightWrote 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/edithatogo/sourceright/sourceright)<a href="https://agentmods.dev/mcp/edithatogo/sourceright/sourceright"><img src="https://agentmods.dev/badge/mcp/edithatogo/sourceright/sourceright/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/edithatogo/sourceright/sourceright"><img src="https://agentmods.dev/badge/mcp/edithatogo/sourceright/sourceright.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sourceright 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 8d 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
{
"sourceright": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/edithatogo/sourceright-mcp:0.1.20"
],
"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.
- 8d ago First seen · 12 lines scan A bb2a1fa51632
sourceright is an MCP server published in the GitHub repository edithatogo/sourceright (1 stars, last pushed yesterday), 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
citeguard-cli
Check a bibliography for retracted papers -- retractions, corrections, and expressions of concern via Crossref (including Retraction Watch records). CLI, Python library, MCP server, GitHub Action. Runs locally from the citeguard-cli Python package.
citevahti
CiteVahti — citation-integrity and provenance for research synthesis: a blinded human->AI->adjudication dual-rating workflow with decision-gated, undoable Zotero write-back (single-user, local-first; searches PubMed, OpenAlex, Semantic Scholar, Crossref). Runs locally from the citevahti Python package.
tokens-studio-mcp
MCP server "tokens-studio-mcp" as configured in Blyawon/tokensStudioMCP. Runs locally from the tokens-studio-mcp npm package.
rewynd
MCP server "rewynd" as configured in SrinjoyDev/rewynd. Launched with rewynd mcp.
tracer
MCP server "tracer" as configured in aiquilibria/contAIned. Runs contained.tracer_mcp with python3.
golden-egg
MCP server "golden-egg" as configured in joehwang/goldenegg-tw-holdings-cli. Runs locally from the golden-egg Python package.