ARYSPHERE x402 chain reads and token verdicts
net.ts.tailb4ac3a.ari001Published by ari001.tailb4ac3a.ts.netOfficial publisherv1.0.0Updated Oct 24, 2026
Pay-per-call onchain reads (Base, Ethereum, Gnosis), token verdicts and LLM chat over x402 USDC
The publisher's own server: ARYSPHERE x402 chain reads and token verdicts
Overview
Lets an assistant make pay-per-call onchain reads on Base, Ethereum and Gnosis, get token verdicts, and use LLM chat paid in USDC via x402.
- What you can do
- This remote MCP server exposes onchain read operations for the Base, Ethereum and Gnosis networks, along with token verdicts and an LLM chat capability. Access is metered per call and settled over the x402 protocol in USDC. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
- When to use it
- Consider it when an assistant needs blockchain read data or token assessments across Base, Ethereum or Gnosis and you are willing to pay per request in USDC. It is less suitable if you need free, unmetered access or documented tool schemas before installing.
- Requirements
- A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. Because calls are paid in USDC over x402, a funded wallet or payment credential is implied by the description, though no specific variable or header is named.
Installation
In SourceWeft
- Open ARYSPHERE x402 chain reads and token verdicts in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/net.ts.tailb4ac3a.ari001%2Farysphere-x402/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"arysphere-x402-chain-reads-and-token-ver": {
"type": "http",
"url": "https://ari001.tailb4ac3a.ts.net/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 12, 2026
Score
17% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.