MCP servers › net.ts.tailb4ac3a.ari001 › arysphere-x402
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
net.ts.tailb4ac3a.ari001/arysphere-x402
Pay-per-call onchain reads (Base, Ethereum, Gnosis), token verdicts and LLM chat over x402 USDC — the publisher's description
Summary
net.ts.tailb4ac3a.ari001/arysphere-x402 is a remote MCP server listed in the official MCP registry at version 1.0.0, marked deprecated there. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 52 tools, 0 resources and 0 prompts.
Record checks
0 of 2 record checks met · 7 do not apply
- not met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: deprecated in the registry
- Not ranked by stars: deprecated in the registry
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 52
- Described as changing data
- 0 of 52 toolsAI-classified
- Mainly works on
- accounts and data in outside web servicesAI-classified
- Topic
- finance-and-paymentsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- The registry marks this server deprecated.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.0, published 2026-10-12 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-12 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-12).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.
None of its 52 tools are described as changing anything.
“Check this CA: Base ERC-20 verdict of a token contract address.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“token contract, 0x + 40 hex”
“Base contract ABI (ERC-20 / ERC-721 and others) from a contract address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“contract, 0x + 40 hex”
“Base ERC-20 token balance of a holder address.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“holder, 0x + 40 hex”tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Base NFT (ERC-721) owner of a token id.”
Publisher declares: read-only yes
2 inputs, 2 required
idstringrequired“token id, decimal”tokenstringrequired“ERC-721 contract, 0x + 40 hex”
“Base on-chain read: the native balance of an address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Base on-chain read: a block by number or 'latest'.”
Publisher declares: read-only yes
1 input, 1 required
blockstringrequired“a block number, or 'latest'”
“Base on-chain read: a contract's event logs, filtered by topic and block range.”
Publisher declares: read-only yes
3 inputs, 1 required
addressstringrequired“contract, 0x + 40 hex”blocksstring“optional, last N blocks, 1-100 (default 10)”topic0string“optional event signature hash, 0x + 64 hex”
“Base on-chain read: a transaction by its hash.”
Publisher declares: read-only yes
1 input, 1 required
hashstringrequired“transaction hash, 0x + 64 hex”
“Base on-chain read: a block by number or 'latest'.”
Publisher declares: read-only yes
1 input, 1 required
blockstringrequired“a block number, or 'latest'”
“Base bundle: several reads in one paid call.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Check this CA: Base ERC-20 verdict of a token contract address.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“token contract, 0x + 40 hex”
“Explain this tx: Base transaction decoded -- status, transfers, swaps, approvals, USD value.”
Publisher declares: read-only yes
1 input, 1 required
hashstringrequired“transaction hash, 0x + 64 hex”
Show 40 more tools
“Base bundle: several reads in one paid call.”
Publisher declares: read-only yes
2 inputs, 2 required
hashstringrequired“transaction hash, 0x + 64 hex”tokenstringrequired“token contract, 0x + 40 hex”
“Base bundle: several reads in one paid call.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“wallet or contract, 0x + 40 hex”tokenstringrequired“token contract, 0x + 40 hex”
“Check this wallet: Base ETH and top-10 token balances, nonce, contract flag, USD totals.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“wallet or contract, 0x + 40 hex”
“Gnosis Chain network data in one call.”
Publisher declares: read-only yes
Takes no inputs.
“Ethereum mainnet bundle: several reads in one paid call.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“holder, 0x + 40 hex”tokenstringrequired“token contract, 0x + 40 hex”
“Ethereum mainnet on-chain read: the chain id the node reports.”
Publisher declares: read-only yes
Takes no inputs.
“ENS resolver on Ethereum mainnet: pass name (an ASCII .eth name, e.g.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“0x + 40 hex (reverse, verified)”namestringrequired“an ASCII .eth name (forward), OR”
“Ethereum mainnet ERC-20 allowance a holder granted a spender.”
Publisher declares: read-only yes
3 inputs, 3 required
ownerstringrequired“0x + 40 hex”spenderstringrequired“0x + 40 hex”tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Ethereum mainnet ERC-20 token balance of a holder address.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“holder, 0x + 40 hex”tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Ethereum mainnet NFT (ERC-721) owner of a token id.”
Publisher declares: read-only yes
2 inputs, 2 required
ownerstringrequired“0x + 40 hex”tokenstringrequired“ERC-721 contract (Enumerable), 0x + 40 hex”
“Ethereum mainnet on-chain read: the native balance of an address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Ethereum mainnet on-chain read: a block by number or 'latest'.”
Publisher declares: read-only yes
1 input, 1 required
blockstringrequired“a block number, or 'latest'”
“Ethereum mainnet on-chain read: a transaction by its hash.”
Publisher declares: read-only yes
1 input, 1 required
hashstringrequired“transaction hash, 0x + 64 hex”
“Ethereum mainnet on-chain read: a contract's event logs, filtered by topic and block range.”
Publisher declares: read-only yes
3 inputs, 1 required
addressstringrequired“contract, 0x + 40 hex”blocksstring“optional, last N blocks, 1-100 (default 10)”topic0string“optional event signature hash, 0x + 64 hex”
“Check this CA: Ethereum mainnet ERC-20 verdict of a token contract address.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“token contract, 0x + 40 hex”
“Explain this tx: Ethereum mainnet transaction decoded -- status, transfers, swaps, approvals, USD value.”
Publisher declares: read-only yes
1 input, 1 required
hashstringrequired“transaction hash, 0x + 64 hex”
“Ethereum mainnet bundle: several reads in one paid call.”
Publisher declares: read-only yes
2 inputs, 2 required
hashstringrequired“transaction hash, 0x + 64 hex”tokenstringrequired“token contract, 0x + 40 hex”
“Ethereum mainnet bundle: several reads in one paid call.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“token contract, 0x + 40 hex”
“Gnosis Chain on-chain read: the native balance of an address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Gnosis Chain on-chain read: a contract's event logs, filtered by topic and block range.”
Publisher declares: read-only yes
3 inputs, 1 required
addressstringrequired“contract, 0x + 40 hex”blocksstring“optional, last N blocks, 1-100 (default 10)”topic0string“optional event signature hash, 0x + 64 hex”
“Base on-chain read: the latest block number.”
Publisher declares: read-only yes
Takes no inputs.
“Base bundle: several reads in one paid call.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Base network data in one call.”
Publisher declares: read-only yes
Takes no inputs.
“Ethereum mainnet contract ABI (ERC-20 / ERC-721 and others) from a contract address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“contract, 0x + 40 hex”
“Ethereum mainnet ERC-20 allowance a holder granted a spender.”
Publisher declares: read-only yes
3 inputs, 3 required
ownerstringrequired“0x + 40 hex”spenderstringrequired“0x + 40 hex”tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Ethereum mainnet ERC-20 token balance of a holder address.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“holder, 0x + 40 hex”tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Ethereum mainnet ERC-20 total supply of a token contract.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Ethereum mainnet NFT (ERC-721) owner of a token id.”
Publisher declares: read-only yes
2 inputs, 2 required
idstringrequired“token id, decimal”tokenstringrequired“ERC-721 contract, 0x + 40 hex”
“Ethereum mainnet on-chain read: the latest block number.”
Publisher declares: read-only yes
Takes no inputs.
“Ethereum mainnet on-chain read: the native balance of an address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Ethereum mainnet on-chain read: the deployed bytecode at an address.”
Publisher declares: read-only yes
1 input, 1 required
addressstringrequired“0x + 40 hex”
“Ethereum mainnet on-chain read: a contract's event logs, filtered by topic and block range.”
Publisher declares: read-only yes
3 inputs, 1 required
addressstringrequired“contract, 0x + 40 hex”blocksstring“optional, last N blocks, 1-100 (default 10)”topic0string“optional event signature hash, 0x + 64 hex”
“Ethereum mainnet on-chain read: a transaction by its hash.”
Publisher declares: read-only yes
1 input, 1 required
hashstringrequired“transaction hash, 0x + 64 hex”
“Ethereum mainnet on-chain read: the current gas price in wei.”
Publisher declares: read-only yes
Takes no inputs.
“Ethereum mainnet on-chain read: a block by number or 'latest'.”
Publisher declares: read-only yes
1 input, 1 required
blockstringrequired“a block number, or 'latest'”
“Ethereum mainnet bundle: several reads in one paid call.”
Publisher declares: read-only yes
4 inputs, 2 required
addressstringrequired“contract, 0x + 40 hex”blocksstring“optional, last N blocks, 1-100 (default 10)”hashstringrequired“transaction hash, 0x + 64 hex”topic0string“optional event signature hash, 0x + 64 hex”
“Ethereum mainnet bundle: several reads in one paid call.”
Publisher declares: read-only yes
2 inputs, 2 required
addressstringrequired“0x + 40 hex”tokenstringrequired“ERC-20 contract, 0x + 40 hex”
“Ethereum mainnet on-chain read: a transaction receipt (status, gas used, logs) by hash.”
Publisher declares: read-only yes
1 input, 1 required
hashstringrequired“transaction hash, 0x + 64 hex”
“Check this CA: Ethereum mainnet ERC-20 verdict of a token contract address.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“token contract, 0x + 40 hex”
“Check this CA: Ethereum mainnet ERC-20 verdict of a token contract address.”
Publisher declares: read-only yes
1 input, 1 required
tokenstringrequired“token contract, 0x + 40 hex”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 52 tools
- Says what it returns
- 100% of 52 tools
- States limits, defaults or errors
- 15% of 40 tools
- Says when to use it
- 0% of 40 tools
- Items covered per tool
- 2.2 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 73
- Tools with a description
- 100% of 52
- Typical description length
- 1,067 characters
The tool set
Counted from the listing
- Tools
- 52
- Size of the list
- about 18,497 tokens for an agent to load (characters ÷ 4)
- Naming
- 52 of 52 names use mixed or other styles
AI reading: easy to mix up
No pair found.
The AI items cover 52 of 52 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://ari001.tailb4ac3a.ts.net/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"arysphere-x402": {
"url": "https://ari001.tailb4ac3a.ts.net/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"arysphere-x402": {
"type": "http",
"url": "https://ari001.tailb4ac3a.ts.net/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"arysphere-x402","type":"http","url":"https://ari001.tailb4ac3a.ts.net/mcp"}'Claude Code
claude mcp add --transport http arysphere-x402 https://ari001.tailb4ac3a.ts.net/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://ari001.tailb4ac3a.ts.net/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint ari001.tailb4ac3a.ts.net/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Same tools as other registry entries
Tool lists read · names comparedIts 52 tools have exactly the same names as the tools of 1 other registry entry (published under 2 registry namespaces). Their tool descriptions are also word for word the same.
This can be one publisher's family of servers or one template reused under many names. It is a fact about the published tool lists, not a judgement of the publisher and not a safety finding; we compared tool names, not code.
Shared tool names (12 of 52 shown):
x402_bazaar_token_verdict_v2__base_token_verdict_v3x402_chain_reads_v1__base_contract_abix402_chain_reads_v1__base_erc20_balanceofx402_chain_reads_v1__base_erc721_ownerofx402_chain_reads_v1__base_eth_getbalancex402_chain_reads_v1__base_eth_getblockbynumberx402_chain_reads_v1__base_eth_getlogsx402_chain_reads_v1__base_eth_gettransactionbyhashx402_chain_reads_v1__base_latest_block_timex402_chain_reads_v1__base_reads_bundlex402_chain_reads_v1__base_token_verdict_readx402_chain_reads_v1__base_tx_explainThe other entries
All groups of servers with identical tool lists
Source: our read-only reads of each server's tool list · 2026-10-23. No tool was called.
Choosing
Record checks
Public records · not a safety rating0 of 2 record checks met · 7 do not apply
- Not ranked by downloads: deprecated in the registry
- Not ranked by stars: deprecated in the registry
- Not metRegistry entry is active and says how to run itThe registry marks this entry as deprecated.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about net.ts.tailb4ac3a.ari001/arysphere-x402
Answered from the data aboveIs net.ts.tailb4ac3a.ari001/arysphere-x402 safe to install?
We do not rate servers as safe or unsafe. 0 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its registry entry is marked deprecated. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does net.ts.tailb4ac3a.ari001/arysphere-x402 need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has net.ts.tailb4ac3a.ari001/arysphere-x402 been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
What can net.ts.tailb4ac3a.ari001/arysphere-x402 do?
It lists 52 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search. We did not call any tool, so this describes the text, not the behaviour.
Can net.ts.tailb4ac3a.ari001/arysphere-x402 change or delete data?
None of its 52 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.vybenetwork/solana-mcp-vybeSolana MCP by Vybealso has tools that reads or searchescompare with this one
- io.github.mnemox-ai/tradememory-protocolalso has tools that reads or searchescompare with this one
- io.github.agent-next/polymarket-paper-traderPolymarket Paper Traderalso has tools that reads or searchescompare with this one
- io.github.openaccountants/openaccountantsOpenAccountantsalso has tools that reads or searchescompare with this one
- io.github.koreal6803/finlab-aialso has tools that reads or searchescompare with this one
- io.github.xang1234/stockscreen-mcpStock Screeneralso has tools that reads or searchescompare with this one
Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 5,931 msConnected after 1 redirect. No credential was sent or needed.
- Read the inventory: 52 tools, 0 resources, 0 prompts.
- 8,704 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “net.ts.tailb4ac3a.ari001/arysphere-x402: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/net.ts.tailb4ac3a.ari001/arysphere-x402
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/net.ts.tailb4ac3a.ari001/arysphere-x402)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology