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/Abstraxn-Labs/abstraxn-agent-layerWrote 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/abstraxn-labs/abstraxn-agent-layer/abstraxn)<a href="https://agentmods.dev/mcp/abstraxn-labs/abstraxn-agent-layer/abstraxn"><img src="https://agentmods.dev/badge/mcp/abstraxn-labs/abstraxn-agent-layer/abstraxn/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/abstraxn-labs/abstraxn-agent-layer/abstraxn"><img src="https://agentmods.dev/badge/mcp/abstraxn-labs/abstraxn-agent-layer/abstraxn.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
abstraxn 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
{
"abstraxn": {
"url": "https://mcp.abstraxn.com/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 879b76b4d3f5
abstraxn is an MCP server published in the GitHub repository Abstraxn-Labs/abstraxn-agent-layer (4 stars, last pushed 20d 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
chainstack
Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. Remote server at mcp.chainstack.com.
chainweb
MCP server "chainweb" as configured in Pact-Community-Organization/pact-mcp. Runs ./packages/mcp-chainweb/dist/bin.js with node. Needs 5 environment variables to run.
chainweb
Chainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys. Runs locally from the @pact-community/mcp-chainweb npm package. Needs 5 environment variables to run.
xrpl-referee
Trust and payment layer for the agentic economy on the XRP Ledger. Remote server at xrpl-referee.onrender.com.
pact
Pact 5 tooling: REPL test runs, trap scanning, gas estimation, interface diff, format checks. Runs locally from the @pact-community/mcp-pact npm package. Needs 2 environment variables to run.
mcp-klever-vm
MCP server for Klever blockchain smart contract development. Runs locally from the @klever/mcp-server npm package.