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/csacanam/lotero-coreWrote 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/csacanam/lotero-core/lotero)<a href="https://agentmods.dev/mcp/csacanam/lotero-core/lotero"><img src="https://agentmods.dev/badge/mcp/csacanam/lotero-core/lotero/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/csacanam/lotero-core/lotero"><img src="https://agentmods.dev/badge/mcp/csacanam/lotero-core/lotero.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lotero 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 10d 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
{
"lotero": {
"command": "npx",
"args": [
"-y",
"lotero-mcp"
],
"env": {
"LOTERO_WALLET_PRIVATE_KEY": "",
"LOTERO_PLAYER_ADDRESS": "",
"LOTERO_MAX_SPINS_PER_SESSION": ""
}
}
}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.
- 10d ago First seen · 14 lines scan A 22ee00d27f58
lotero is an MCP server published in the GitHub repository csacanam/lotero-core (0 stars, last pushed 2mo 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
mcp-mercado-bitcoin
MCP server for Mercado Bitcoin — Brazilian crypto exchange, trading, orderbook, withdrawals. Runs locally from the @codespar/mcp-mercado-bitcoin npm package. Needs 1 environment variable to run.
stellar-rpc
MCP server "stellar-rpc" as configured in rylsherdamz-rgb/stellar-forge. Runs locally from the @stellar/mcp-server npm package. Needs 2 environment variables to run.
bug-bounty-intelligence-mcp
AI security scanner for Solidity + free CC0 dataset of Sherlock audit-competition acceptance rates. Remote server at wazir-x402.duckdns.org.
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
neo-mcp
MCP server and HTTP API for Neo N3 and Neo X blockchain integration. Runs locally from the @r3e/neo-mcp npm package.
mcp
MCP server "mcp" as configured in grokloop/grokchain-mcp. Runs locally from the @grokchain/mcp npm package.