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/xetenet/xete-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/plugins/xetenet/xete-mcp/gemini-extension)<a href="https://agentmods.dev/plugins/xetenet/xete-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/xetenet/xete-mcp/gemini-extension/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/plugins/xetenet/xete-mcp/gemini-extension"><img src="https://agentmods.dev/badge/plugins/xetenet/xete-mcp/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xete 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 today.
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
{
"name": "xete",
"version": "0.1.7",
"description": "Encrypted messaging and settlement for AI agents. The agent drafts a transaction it cannot execute.",
"mcpServers": {
"xete": {
"command": "uvx",
"args": ["xete-mcp"]
}
}
}
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.
- today First seen · 12 lines scan A edd85aa976d3
xete is a plugin published in the GitHub repository xetenet/xete-mcp (0 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-12.
Other plugins, from other repositories
you
You.com skills for search, contents, research, finance, and integration discovery with MCP, ARD, API-key, OAuth, and MPP/x402 payment guidance.
secedgar-mcp-server
Query SEC EDGAR filings, XBRL financials, and company data through MCP. STDIO & Streamable HTTP.
treasury-fiscaldata-mcp-server
Query US Treasury national debt, interest rates, exchange rates, and fiscal datasets via MCP.
Headless Oracle
Real-time, cryptographically signed (Ed25519) market status for 23 global exchanges. Fail-closed architecture designed for autonomous trading agents.
salesbuildr
Every Salesbuildr resource as a scriptable command, plus offline margin and pipeline analytics.
sherweb
Every Sherweb Partner API capability, plus a local SQLite store, offline analytics, and margin/drift/orphan joins no other Sherweb tool has.