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/assister-xyz/quality-oracleWrote 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/assister-xyz/quality-oracle/agenttrust)<a href="https://agentmods.dev/mcp/assister-xyz/quality-oracle/agenttrust"><img src="https://agentmods.dev/badge/mcp/assister-xyz/quality-oracle/agenttrust/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/assister-xyz/quality-oracle/agenttrust"><img src="https://agentmods.dev/badge/mcp/assister-xyz/quality-oracle/agenttrust.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agenttrust 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
{
"agenttrust": {
"command": "uvx",
"args": [
"mcp-agenttrust"
],
"env": {
"GROQ_API_KEY": "",
"CEREBRAS_API_KEY": "",
"MONGODB_URL": ""
}
}
}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 · 13 lines scan A daed85b7f083
agenttrust is an MCP server published in the GitHub repository assister-xyz/quality-oracle (0 stars, last pushed 4mo 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
cargo
Structured Rust cargo operations (build, test, clippy) as typed JSON. Runs locally from the @paretools/cargo npm package.
evalview
MCP server "evalview" as configured in hidai25/eval-view. Launched with evalview mcp serve. Needs 2 environment variables to run.
evalview-mcp
Open-source testing and regression detection framework for AI agents. Golden baseline diffing, CI/CD integration, works with LangGraph, CrewAI, OpenAI, Anthropic Claude, HuggingFace, Ollama, and MCP. Runs locally from the evalview Python package. Needs 1 environment variable to run.
zendesk-local
MCP server "zendesk-local" as configured in fruggr/zendesk-mcp-server. Launched with pnpm exec tsx src/index.ts --mode all --dev. Needs 1 environment variable to run.
sauce-api-mcp
MCP servers for Sauce Labs APIs (Core & RDC OpenAPI). Runs locally from the sauce-api-mcp Python package. Needs 2 environment variables to run.
opengate-mcp
Check whether an AI answer is grounded in its context — deterministic, no LLM judge. Runs locally from the @pharmatools/opengate-mcp npm package.