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/bjyoe2016/dyoe-agent-tools-mcpWrote 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/bjyoe2016/dyoe-agent-tools-mcp/dyoe-trust-mcp)<a href="https://agentmods.dev/mcp/bjyoe2016/dyoe-agent-tools-mcp/dyoe-trust-mcp"><img src="https://agentmods.dev/badge/mcp/bjyoe2016/dyoe-agent-tools-mcp/dyoe-trust-mcp/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/bjyoe2016/dyoe-agent-tools-mcp/dyoe-trust-mcp"><img src="https://agentmods.dev/badge/mcp/bjyoe2016/dyoe-agent-tools-mcp/dyoe-trust-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
dyoe-trust-mcp 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 6d 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
{
"dyoe-trust-mcp": {
"command": "npx",
"args": [
"-y",
"dyoe-trust-mcp"
],
"env": {
"WALLET_PRIVATE_KEY": "",
"DYOE_MAX_PAYMENT_USD": "0.10"
}
}
}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.
- 6d ago First seen · 13 lines scan A 4e763b0ff2fd
dyoe-trust-mcp is an MCP server published in the GitHub repository bjyoe2016/dyoe-agent-tools-mcp (0 stars, last pushed 6d 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-10-22.
Other mcp servers, from other repositories
whale-data-mcp
Signed settled outcomes (Polymarket, sports, Kalshi) + whale signals as agent tools, paid via x402. Runs locally from the @predge/whale-data-mcp npm package. Needs 7 environment variables to run.
z-zero-mcp
Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context. Runs locally from the z-zero-mcp-server npm package. Needs 1 environment variable to run.
thebuyside-x402-agent
Buyer-side MCP gateway for x402 and MPP (pay.sh) — let any agent pay any metered API on Base or Solana without seeing a 402 or a wallet. Runs locally from the thebuyside-x402-agent npm package.
mcp-server
Smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents. Runs locally from the @azeth/mcp-server npm package. Needs 8 environment variables to run.
tereno
Check a Base contract, transaction or web page before you act. Free pricing, paid per call in USDC. Runs locally from the tereno-mcp npm package.
telemost-mcp-server
Telegram channel analytics and statistics for AI agents, pay-per-call in USDC via x402. Runs locally from the telemost-mcp-server npm package. Needs 5 environment variables to run.