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/toreva/kitWrote 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/toreva/kit/claude-desktop-toreva)<a href="https://agentmods.dev/mcp/toreva/kit/claude-desktop-toreva"><img src="https://agentmods.dev/badge/mcp/toreva/kit/claude-desktop-toreva/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/toreva/kit/claude-desktop-toreva"><img src="https://agentmods.dev/badge/mcp/toreva/kit/claude-desktop-toreva.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
toreva 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 12 lines scan A c51cb1b8e4db
toreva is an MCP server published in the GitHub repository toreva/kit (0 stars, last pushed today), with no licence file. 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
polymarket-toolkit
Read-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders. Runs locally from the polymarket-toolkit-mcp npm package.
typesensekit
95 typed Typesense operations for AI agents through an MCP server that is read-only by default. Runs locally from the @typesensekit/mcp npm package. Needs 4 environment variables to run.
mcp
AI agent MCP server for Suigar casino game, SweetHouse, NFT, and referral transactions. Runs locally from the @suigar/mcp npm package. Needs 4 environment variables to run.
rpcedge
MCP server for rpc edge: RPC health, priority fees, leaders, latency compare, and signed transaction submit via relay. Runs locally from the rpcedge-mcp npm package.
ripple
Python client for rippled. Runs locally from the ripple Python package.
zoom-agent-cli
CLI and MCP server for the Zoom API — built for humans and AI agents. Runs locally from the zoom-agent-cli npm package.