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.
npx agentmods add mcp/ruali-dev/riven-analyst/riven-toolsgit clone --depth 1 https://github.com/ruali-dev/Riven-AnalystWrote 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/ruali-dev/riven-analyst/riven-tools)<a href="https://agentmods.dev/mcp/ruali-dev/riven-analyst/riven-tools"><img src="https://agentmods.dev/badge/mcp/ruali-dev/riven-analyst/riven-tools.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
riven-tools 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 4d 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
{
"riven-tools": {
"command": "uv",
"args": [
"run",
"--project",
".",
"--locked",
"--no-dev",
"riven-analyst-mcp"
],
"env_vars": [
"RIVEN_VISION_PROVIDER",
"RIVEN_VISION_BASE_URL",
"RIVEN_VISION_MODEL",
"RIVEN_VISION_API_KEY",
"RIVEN_WORKSPACE_ROOT",
"RIVEN_VISION_TIMEOUT_SECONDS",
"RIVEN_VISION_MAX_RETRIES",
"RIVEN_IMAGE_EXTRA_ROOTS",
"RIVEN_IMAGE_MAX_BYTES",
"RIVEN_IMAGE_MAX_PIXELS",
"RIVEN_ALLOW_WEB_RESEARCH"
],
"cwd": "."
}
}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.
- 4d ago First seen · 27 lines scan A 9ed218fb72cb
riven-tools is an MCP server published in the GitHub repository ruali-dev/Riven-Analyst (3 stars, last pushed 1mo ago), licensed Apache-2.0. 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
awsknowledge
MCP server "awsknowledge", hosted remotely at knowledge-mcp.global.api.aws, as configured in theagenticguy/erpaval.
playwright
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
reference-langchain
MCP server "reference-langchain", hosted remotely at reference.langchain.com, as configured in langchain-ai/langchain.
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.