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/twzrd-sol/twzrd-trustWrote 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/twzrd-sol/twzrd-trust/twzrd-agent-intel)<a href="https://agentmods.dev/mcp/twzrd-sol/twzrd-trust/twzrd-agent-intel"><img src="https://agentmods.dev/badge/mcp/twzrd-sol/twzrd-trust/twzrd-agent-intel/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/twzrd-sol/twzrd-trust/twzrd-agent-intel"><img src="https://agentmods.dev/badge/mcp/twzrd-sol/twzrd-trust/twzrd-agent-intel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
twzrd-agent-intel 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
{ "twzrd-agent-intel": { "command": "uvx", "args": [ "twzrd-agent-intel" ], "env": { "TWZRD_SIGNAL_SOURCE": "" } } }
What else
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 11 lines scan A ee203304beaf
twzrd-agent-intel is an MCP server published in the GitHub repository twzrd-sol/twzrd-trust (0 stars, last pushed today), 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
agenticpay
Real MCP server (stdio + @modelcontextprotocol/sdk) that exposes x402-paywalled HTTP endpoints as MCP tools. Drop into Claude Desktop, Cursor, or any MCP client. Runs locally from the @agenticpay/mcp-bridge npm package. Needs 6 environment variables to run.
madeonsol
Solana KOL trading intelligence & deployer analytics via x402 micropayments or API key. Runs locally from the mcp-server-madeonsol npm package.
tnt-house-risk-data-api
Solana token risk-scoring MCP server for AI trading agents with insider wallet cluster detection. Remote server at tnt-audit.com.
agentfeed
AgentFeed: 47 tools — our own liquidation tape + tokenized-equity peg data, paid in USDC. Remote server at x402.ochinimus.app.
agent-gateway
Thirty-one guarded pay-per-call preflights and evidence products over USDC x402. Runs locally from the @justhandledlabs/agent-client npm package. Needs 1 environment variable to run.
solana-preflight
Solana transaction diagnosis, simulation, token-risk evidence, and priority fees via x402 USDC. Runs locally from the utilia-solana-agent npm package. Needs 1 environment variable to run.