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/xkumakichi/xaip-protocolWrote 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/xkumakichi/xaip-protocol/xaip-mcp-server)<a href="https://agentmods.dev/mcp/xkumakichi/xaip-protocol/xaip-mcp-server"><img src="https://agentmods.dev/badge/mcp/xkumakichi/xaip-protocol/xaip-mcp-server/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/xkumakichi/xaip-protocol/xaip-mcp-server"><img src="https://agentmods.dev/badge/mcp/xkumakichi/xaip-protocol/xaip-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xaip-mcp-server 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 9d 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
{
"xaip-mcp-server": {
"command": "npx",
"args": [
"-y",
"xaip-mcp-server"
],
"env": {}
}
}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.
- 9d ago First seen · 10 lines scan A cc21675a17cc
xaip-mcp-server is an MCP server published in the GitHub repository xkumakichi/xaip-protocol (1 stars, last pushed 1mo 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
xrpl-identity-mcp
MCP server for XRPL identity: DIDs, credentials, signer lists, and safe transaction workflows. Runs locally from the xrpl-identity-mcp npm package. Needs 3 environment variables to run.
webbersites-x402-mcp
45 pay-per-call AI agent tools + wallet-owned agent memory. Scraping, SEO, lint, crypto. x402 USDC. Runs locally from the webbersites-x402-mcp npm package. Needs 2 environment variables to run.
memory
Pay-per-use semantic memory for AI agents. SHA256 commitment, Ed25519 sig, Lightning. Remote server at memory.rgiskard.xyz.
astracipher
Cryptographic identity for AI agents: W3C DIDs, Verifiable Credentials, post-quantum crypto. Runs locally from the @astracipher/core npm package.
anp-bridge-mcp-server
MCP Server bridging the Agent Network Protocol (ANP) with MCP agents — identity, discovery, messaging. Runs locally from the anp-bridge-mcp-server Python package.
soroban-memory
Persistent memory layer for Stellar/Soroban projects. Scans your repo, links code to on-chain reality, and serves the result to you and to your AI agents over MCP. Runs locally from the soroban-memory npm package.