naxytra
From $0.01 per useActively maintained
- Is it safe? We have not read the data policy of naxytra yet. Read it on the official site before you upload anything.naxytra.com ↗
- Is it free? From $0.01 per use · pricing page, read Oct 21, 2026See ↓
- What else does this? We have not measured alternatives for this one yet. If you know one, add it below.See ↓
41 installs/mo
Emerging
- For
- Agents, developers and enterprises that want paid, verifiable machine tool calls over MCP or x402.
- Price
- From $0.01 per usepricing page, read Oct 21, 2026
- Activity
- Actively maintainedrelease 10 days ago · site updated 8 days ago
- Used for
- Check whether an x402 payment actually settled
- Encode and decode ABI call data
- Extract plain text from HTML pages
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsnaxytra.com ↗
- MCP servercom.naxytra/xytara-mcp-executorverified in the MCP registry
- Stateanswers, 17 toolschecked 2026-10-22
- Address to connectxytara-mcp-executor.onrender.com/mcp
- MCP docsnaxytra.com/.well-known/mcp/server-card.jsonthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use naxytra for?
Sign in to leave a noteWhat is naxytra?
Runs paid machine-to-machine transactions with quoting, payment, execution and proof records, via the xytara runtime and xoonya review layer.
Who is naxytra for?
Agents, developers and enterprises that want paid, verifiable machine tool calls over MCP or x402.
How much does naxytra cost?
Paid plans start at $0.01 per use, per naxytra's pricing page on 2026-10-21.
Do people use naxytra?
Emerging: 41 installs/mo (npm).
Is naxytra still maintained?
Actively maintained: release 10 days ago · site updated 8 days ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.