io.github.0xAxiom/axiom-agentic-tools

MCPcommunitylive
v0.2.0io.github.0xAxiomUnknownUpdated 4mo agoGitHub

x402-paid Base agent tools (USDC). 5 deterministic tools. No API keys. No NFT pass.

Five JSON-output MCP tools for builders shipping agentic services on Base. x402-paid, no API keys, no accounts. Live deployment: · MCP endpoint: · OpenAPI: is a tiny, deterministic MCP server. Each of its five tools answers one focused question for an autonomous agent or its builder: "Where is this x402 endpoint leaking revenue?" "What does a deployable token spec look like for my agent?" "Which…

Endpoint healthlive
checked 9 days ago · 201ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.0xAxiom
LicenseUnknown
Version0.2.0
Sourcemcp-registry
GitHub0xAxiom/axiom-agentic-tools
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 48 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Five JSON-output MCP tools for builders shipping agentic services on Base. x402-paid, no API keys, no accounts. Live deployment: · MCP endpoint: · OpenAPI: is a tiny, deterministic MCP server. Each of its five tools answers one focused question for an autonomous agent or its builder: "Where is this x402 endpoint leaking revenue?" "What does a deployable token spec look like for my agent?" "Which sequence of paid tools fits this budget?" "Is my repo ready for agent marketplaces?" "Which Base…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.