Toll
REMOTE · T0LL.XYZ · 2 COMPONENTS
Robinhood Chain checks for agents: coins, devs, ERC-8004 agents, pre-sign check, Stock Token data.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
Recent critical change
Authorization (7 Nov 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (unwatch_coin). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11350 tokens (~343/item across 33 items; 33 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- New tool “agent_privacy” functional
- 20 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → excellent functional
- New tool “check_revenue_token” functional
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “larp_check” rewrote its description, which is the text the model reads security
- Tool “pre_buy_check” rewrote its description, which is the text the model reads security
- Tool “watch_wallet” rewrote its description, which is the text the model reads security
- Tool “check_tx” rewrote its description, which is the text the model reads security
- Schema quality: 9332 → 10541 ▼ functional
- New tool “account_permissions” functional
- New tool “ask_toll” functional
- “check_tx” added an optional parameter “summary” cosmetic
- “check_tx” added an optional parameter “lang” cosmetic
- “check_tx” added an optional parameter “intentText” cosmetic
- 17 Nov 26 +1
- Tool “launch_record” rewrote its description, which is the text the model reads security
- Tool “check_coin” rewrote its description, which is the text the model reads security
- Tool “check_coins” rewrote its description, which is the text the model reads security
- Tool “pre_buy_check” rewrote its description, which is the text the model reads security
- Tool “presign_risk_report” rewrote its description, which is the text the model reads security
- Tool “stock_tokens” rewrote its description, which is the text the model reads security
- Tool “unwatch_coin” rewrote its description, which is the text the model reads security
- Tool “unwatch_wallet” rewrote its description, which is the text the model reads security
- Tool “wallet_approvals” rewrote its description, which is the text the model reads security
- Tool “watch_wallet” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “pre_buy_check” added an optional parameter “budget_ms” cosmetic
- “unwatch_coin” reworded the description of “id” cosmetic
- “unwatch_wallet” reworded the description of “id” cosmetic
- 16 Nov 26 0
- Tool “check_tx” rewrote its description, which is the text the model reads security
- 15 Nov 26 +1
- New tool “find_job” functional
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_hook” rewrote its description, which is the text the model reads security
- Tool “check_tx” rewrote its description, which is the text the model reads security
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://t0ll.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=t0ll.xyz | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6e743721eae95c023d821a5baf9392ffe84 |
| SANs: t0ll.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of t0ll.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | DS published | 3599, 18130 | 8, 8 | Verified |
| t0ll.xyz. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https://api.web3modal.org; media-src 'self' blob:; connect-src 'self' https: wss:; frame-src https://dexscreener.com https://verify.walletconnect.org https://verify.walletconnect.com https://secure.walletconnect.org https://secure-mobile.walletconnect.com https://auth.privy.io; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://t0ll.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://t0ll.xyz/mcp | HTTPS enforced | 301 | https://t0ll.xyz/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_permissions Account permissions ~356
The standing permissions of an account on Robinhood Chain: who can move its funds without the owners signing. It reads what the address is (Safe, ERC-7579 smart account, plain wallet, wallet with an EIP-7702 delegate, or another contract), a Safe's owners and threshold (1-of-n flagged, each owner a plain wallet or a contract), every module and the code it runs (Zodiac Roles and Delay named; a module Toll does not know can move everything), each Zodiac Roles member and what each role may call (any function, a function with any arguments, or a function under conditions not read yet; delegatecall and send flagged), who owns the Roles module, a Delay module's waiting period and who may queue on it, the guard, the fallback handler (one that is not Safe's own flagged) and installed ERC-7579 modules. Each finding has a severity (critical / high / medium / info) and a summary line says the strongest one; every part not read is listed as not read, never as none. Facts read from the chain, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The account address (a Safe, a smart account or a wallet) on Robinhood Chain: 0x followed by 40 hex characters |
| lang | string | – | Optional: "ar" for the plain-words line in Arabic; default English |
| summary | boolean | – | Optional: a 1-2 sentence plain-words line on top (AI, rewritten from the summary and findings; dropped if it names a number not in them). Default: added when ready within about 1 s; true waits up to… |
No output schema declared.
No examples provided.
agent_privacy Agent privacy check ~249
What anyone can learn about one ERC-8004 agent on Robinhood Chain from the chain alone, by its agent id: a privacy grade (A to F), a score out of 100 and each leak found, with its proof and a tip. It reads whether payments land on the owner's own account, whether the owner first funded the payment address or sent to it directly (an on-chain transfer, never proof of who owns what), other agents the owner registered, other agents sharing the payment address, how many wallets paid its x402 payTo in 30 days, and the payment wallet's own wallet-privacy leaks (funding trail, linked wallets, holdings, activity hours). What helps (a stealth address registered under ERC-6538, funding from a shielded pool) is listed apart. Every part not read is named, never counted as no leak. The grade measures what anyone can see, not whether the agent is good or bad. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | – | yes | The agent id: its ERC-8004 token id in the Robinhood Chain identity registry, a whole number from 0 to 1000000000 (for example 20030) |
No output schema declared.
No examples provided.
ask_toll Ask Toll ~228
Ask Toll a plain-language question about Robinhood Chain (a coin, a dev wallet, a wallet's approvals or privacy, a smart account, a v4 hook, an ERC-8004 agent, paid x402 APIs, the chain right now, a stock token). Toll's AI picks which of Toll's own read tools to run (at most 4), runs them, and answers in a few plain sentences naming the tool each fact came from; every number, verdict and address in the answer is checked against the tool results, and when the check fails the raw tool results come back instead. Nothing from outside Toll's tools. 500 characters at most; address optional. 3 questions a day free, 30 with a $TOLL holder's key. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional: the address the question is about (a coin, a wallet, a hook or an account on Robinhood Chain): 0x followed by 40 hex characters |
| question | string | yes | Your question in plain words, up to 500 characters |
No output schema declared.
No examples provided.
chain_pulse Chain pulse ~58
How busy Robinhood Chain is right now, as Toll's live engine counts it: launches in the last 5 minutes and hour, graduations, launches by launchpad, new pools, trades a minute and volume. Robinhood Chain only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_agent Check an agent ~272
One ERC-8004 agent registered on Robinhood Chain (identity registry 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432), by its agent id: whether its registration card loads and from which host, its class (real service / site only / card only / broken card), whether its MCP server answered an initialize call, whether its x402 endpoint answered 402 with payment terms and who it pays, whether that payTo is the registered agentWallet, whether the agent's wallet has sent a transaction, when it was last checked and what changed; read live by the id: its reviews in the ERC-8004 reputation registry (count, wallets, average score), its requests in the ERC-8004 validation registry, and whether its card declares a human behind it (the card's claim, not verified). Plain facts from Toll's agent census, with the date and the source they were read from (the live census, or the 2026-10-28 snapshot), never a verdict. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| id | – | yes | The agent id: its ERC-8004 token id in the Robinhood Chain identity registry, a whole number from 0 to 1000000000 (for example 20030) |
No output schema declared.
No examples provided.
check_coin Check a coin ~257
Answers questions like "is this a rug?", "who made this coin?", "was it sniped or bundled?" or "can the dev pull the liquidity?" about a token address. Check one token on Robinhood Chain from the chain itself: who is behind it and how it launched. On Robinhood Chain: where and when it launched, the maker (dev) and its launch record, snipers in the first 3 seconds, wallets the launch made exempt from tax (bundles), flagged wallets, what the maker holds and sold, burned supply, the curve or pool. Toll's findings are tallied as against / careful / clear. On Robinhood Chain a Verdict line (AGAINST / CAREFUL / CLEAR / INCOMPLETE) sits above the tally: INCOMPLETE means some part was not read yet (never read it as clear) and says when to call again. The answer's first line names the chain. Reads Robinhood Chain (4663).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address: 0x followed by 40 hex characters |
| chain | string | – | Which chain: rh = Robinhood Chain (4663). Leave it out and Toll finds which chain the token is on. |
No output schema declared.
No examples provided.
check_coins Many coins at once ~120
Up to 20 Robinhood Chain coins in one call, answered only from checks Toll already holds (read in the last 24 h): for each coin the verdict word (AGAINST / CAREFUL / CLEAR / INCOMPLETE) with its tally and how old the read is, or "not read yet". Reads nothing new and uses no free coin. A coin not read yet says so.
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | Token contract addresses on Robinhood Chain, 1 to 20 (0x followed by 40 hex characters each) |
No output schema declared.
No examples provided.
check_hook Check a hook ~243
One Uniswap v4 hook on Robinhood Chain, by its contract address: its name and where the name was read (the contract's own getter, Blockscout or Sourcify), whether it is a launchpad's shared hook, its 14 permission bits in plain words (runs on every trade, can take a fee or tax, can act when liquidity is removed...), whether its code can be changed by its owner (EIP-1967 proxy) or is a fixed clone, how many pools use it in Toll's chain data (said as "at least" while older pools are still being read), and whether a test sell through one of its most liquid pools reverted (sells fail). Hookr's root hook and its old launchpad's coins are read too. With a $TOLL holder's Toll key: also the measured buy and sell cut in % and its latest coins with how each ended (the launch record, scored 24 h after launch). Facts, never a verdict. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The hook contract's address on Robinhood Chain: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
check_revenue_token Check a revenue token ~362
One Hookr revenue token on Robinhood Chain (hookr.fun: a fixed-supply ERC-20 whose holders share the income of fee rights locked behind it), by its address or by an agent income door's address. It reads which Hookr tokenizer minted it (or says plainly that it is not a revenue token), its name, supply, the assets it pays in, its release period, who made it, who can still add streams, and the ERC-8004 agent linked by an income door. Each stream: what it holds (a pool's Rules ledger, a Hookr family, a Fee Beneficiary NFT, Uniswap v4 or v3 positions, another revenue token, an outside source or an agent income door), its term (locked for good, until a date the creator can move later but never earlier, or revocable) and Hookr's leg. Then where the income came from over the token's whole life, per asset: from trading (delivered by its fee doors) or put in by wallets (bonus deposits, drops, plain sends to the token or a door, payments to an agent income door), each wallet named and whether it is tied to the creator (the creator itself, the stream manager, the agent's owner or wallet, or a wallet one of them sent ETH or the same token to before it put income in; a contract is never tied by this rule). Holders and the largest holder's share. Every part not read is listed as not read, never as zero. Facts read from the chain, never a verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The revenue token's address on Robinhood Chain, or an agent income door's: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
check_tx Check before signing ~2,256
Pre-sign check, before an agent signs anything on Robinhood Chain (chain id 4663): send the transaction (to, data, value, and from), a message to sign (message: {kind: personal_sign | eth_sign, data, origin?}), an EIP-712 signature request (typedData), an ERC-4337 user operation (userOp, with entryPoint), a type-4 authorizationList (alone or with the transaction), the wallet request as the agent would send it (rpc: {method, params} for personal_sign, eth_sign, eth_signTypedData_v4 or eth_sendTransaction), or an x402 payment (x402: the PaymentRequired from the 402, or one accepts entry; agentId optional), and Toll answers ALLOW / WARN / BLOCK with the reasons, as an ERC-8265 RiskAssessment. It reads approvals (unlimited, to a plain wallet, to a contract we do not know, to a wallet the coin's own check names), transfers (to a burn address, the token itself, a router, a flagged wallet, an unknown contract), swaps (the router, who it pays out to, and the coin bought, through Toll's coin check: BLOCK only for findings whose coins rugged at 40% or more in our calibration; a single-pool Uniswap v4 swap off the coin's main pool is quoted on the main pool, WARN when that pays more than 3% more), Uniswap v4 position manager calls (modifyLiquidities, its multicall, initializePool, permit: liquidity paid out or a position minted to anyone but from is a warning), Hookr's calls as its MCP builds them (HookrRouter swap, swapFor, swapGated; HookrLauncher launches, a launch's own withdrawal and fee collection, a pool core's claim, a revenue token's claim, the Agent gate link and reviewer set, the order book fill: each named as Hookr's contract, never trusted; an unknown hook, rules contract or add-on in a launch, or a payout to anyone but from, is a warning), standing power over a smart account (a Safe module, guard, fallback handler, owner or threshold change, a Zodiac Roles grant, an ERC-7579 module install: who can then move the account's funds without the owners signing), Bull'…
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | The x402 seller's ERC-8004 agent id, when known |
| authorizationList | array | – | A type-4 (EIP-7702) transaction's authorizationList, or a signAuthorization alone (no to, no data): [{chainId, address, nonce, yParity, r, s}]. A delegate Toll has verified by code hash is WARN; any… |
| authorization_list | array | – | The same list under its snake_case name |
| chainId | string | – | The chain id: 4663 (Robinhood Chain), the only one read; leave it out for 4663 |
| data | string | – | The calldata, hex (0x for a plain send) |
| entryPoint | string | – | The userOp's EntryPoint address (0x + 40 hex); an EntryPoint Toll does not know is a warning |
| from | string | – | The signer's address (0x + 40 hex): a swap paying out to anyone else is flagged |
| intent | object | – | Optional: what the agent means to do, compared with what the transaction does in the simulation. {action: "swap" | "transfer" | "approve" | "pay", sellToken?, sellAmount? (base units, decimal string)… |
| intentText | string | – | Optional, instead of intent: what the agent means to do in plain words, at most 300 characters (e.g. "swap 10 USDG for HOOD, send to my wallet"). Toll's AI reads it into an intent (tokens only ETH, W… |
| lang | string | – | Optional: "ar" for the plain-words line in Arabic (the action word kept in English, e.g. [BLOCK]); default English |
| message | object | – | A message to sign: {kind: "personal_sign" | "eth_sign", data (0x hex or text), origin? (the site asking), from?}. Sign-In with Ethereum is read (domain against origin, expiry); eth_sign of a hash is… |
| origin | string | – | The site or app asking for the signature (https://...), checked against a Sign-In with Ethereum domain |
| registry | string | – | The identity registry agentId is in, CAIP-10 (default eip155:4663:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432, Robinhood Chain; Base: eip155:8453:0x8004A169FB4a3325136EB29fA0ceB6D2e539a432) |
| rpc | object | – | The wallet request as the agent would send it: {method, params}. personal_sign [data, address], eth_sign [address, data], eth_signTypedData_v4 [address, typed data JSON], eth_sendTransaction [tx] |
| strict | boolean | – | Strict payee policy: an x402 payment whose payTo is not verified as the seller's (ERC-8478 verified-wallet or verified-delegation) is BLOCK instead of a warning; not read is BLOCK too |
| summary | boolean | – | Optional: a 1-2 sentence plain-words line (AI, rewritten from the action and warnings, opening with the action word; dropped if it names a number not in them). Default: added when ready within about… |
| ticket | – | – | Optional: ask for a single-use ALLOW ticket a contract can require: true, or {consumer? (the contract that checks it), scope? "call" | "v4swap", swap? {poolId, zeroForOne, amountSpecified, sqrtPriceL… |
| to | string | – | The transaction's to: the contract or wallet it is sent to (0x + 40 hex) |
| typedData | object | – | An EIP-712 signature request: {domain, types, primaryType, message}. Permit, Permit2, EIP-3009, Seaport, UniswapX, or any other (named field by field) |
| userOp | object | – | An ERC-4337 user operation (v0.6, v0.7 packed or unpacked, v0.8): sender, nonce, callData, gas fields, paymaster, signature. Its calls are opened and each checked |
| value | string | – | Wei sent with it, decimal or 0x hex (default 0) |
| x402 | object | – | An x402 payment: the PaymentRequired the 402 sent (with accepts), or one accepts entry; optional payment (the signed payload) and resource (the URL) |
No output schema declared.
No examples provided.
dev_record Deployer record ~111
Every coin one wallet launched on Robinhood Chain. On Robinhood Chain (Pons and Long launchpads): how many, how many graduated from the bonding curve, whether the dev sold, and the latest launches with how each ended. Reads Robinhood Chain.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Which chain: rh = Robinhood Chain (4663). Leave it out for Robinhood Chain. |
| wallet | string | yes | The deployer (dev) wallet address: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
find_job Find a job recipe ~194
Job recipes on Robinhood Chain: jobs an agent can do for a client with paid x402 tools. Each recipe names the tools in order (the URL, its price read from its own HTTP 402 right now, who it pays and whether that is the seller's registered agent wallet), what the tools cost for one run and a price to suggest to the client. Recipes are written by Toll or listed by registered ERC-8004 agents; a job with a tool that is not answering is marked not available and shows no price. Pass query to filter. Toll holds no money and matches nobody: no escrow, no bids. Facts, not a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many jobs, 1 to 20 (default 5) |
| query | string | – | What kind of job, in a few words (for example "coin", "hook" or "stock token"); empty lists every job |
No output schema declared.
No examples provided.
find_paid_api Find a paid API ~204
Paid APIs (x402) an agent can buy on Robinhood Chain, by what you need (for example "weather", "stock quotes", "BV-7X", or empty for all): each with its resource URL, price, payTo, whether that payTo is the agent wallet its ERC-8004 identity registered (verified, ERC-8478) and how many payments it settled through Toll's x402 facilitator; verified first, one row per operator unless the query names it. From the agent census's x402 endpoints and resources settled through Toll with the x402 bazaar extension. Facts, not a recommendation: verified does not say the seller delivers. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many rows, 1 to 20 (default 10) |
| query | string | – | What you want to buy, in a few words (for example "weather" or "stock quotes"); empty lists every operator's best endpoint |
No output schema declared.
No examples provided.
fresh_launches Newest coins ~91
The newest coins launched on Robinhood Chain, newest first, from Toll's live engine: launchpad, age, pair, and the engine's short notes on each (dev record, first buyers, buyers, curve), with a link to the full check. At most 20. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many coins, 1 to 20 (default 10) |
No output schema declared.
No examples provided.
fundamentals Company fundamentals ~276
The company numbers behind one Robinhood Stock Token on Robinhood Chain, from SEC EDGAR XBRL filings, by ticker (AAPL) or token contract: revenue, gross profit, operating income, net income, EPS (diluted and basic), operating cash flow, capital expenditure and free cash flow for TTM (four contiguous quarters, "TTM to <end>"), the last 4 fiscal years or the last 8 quarters (period: ttm, annual or quarterly); margins; year-on-year growth; the latest balance sheet; shares outstanding with its date; the last 8 quarters of revenue and diluted EPS with YoY; and market cap and P/E at the Chainlink reference only when one share count, the multiplier and a current reference allow it (otherwise the reason). Values a filing does not state are labelled derived; EPS is never added up across quarters. Funds and foreign filers say so. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A stock ticker as Robinhood lists it (AAPL, NVDA, BRK.B) or the Stock Token's contract on Robinhood Chain (0x + 40 hex) |
| period | string | – | ttm (default): the last four quarters; annual: the last 4 fiscal years; quarterly: the last 8 quarters |
No output schema declared.
No examples provided.
guidance Earnings release guidance and KPIs ~285
What the company behind one Robinhood Stock Token on Robinhood Chain said in its last 4 earnings releases (SEC 8-K Item 2.02, the press release exhibit), by ticker (NVDA) or token contract, AI-extracted from cited filings: forward guidance (a range low to high, a single figure, or words only), company KPIs, non-GAAP measures and the GAAP lines they are reconciled from, each with its period, its quote from the filing (at most 300 characters) and the filing link. A model picked each value's sentence or table cell; the number was read from that quote by code, never written by the model; figures the code could not read, and GAAP lines that disagree with the company's XBRL facts, were dropped. Read once per release (never per question). limit: values per release (1 to 60, default 25). Funds and foreign issuers (6-K) are not covered. Quotes are the company's words. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A stock ticker as Robinhood lists it (AAPL, NVDA, BRK.B) or the Stock Token's contract on Robinhood Chain (0x + 40 hex) |
| limit | integer | – | How many values to list per release, 1 to 60 (default 25) |
No output schema declared.
No examples provided.
insider_trades Insider trades ~226
Insider trades at the company behind one Robinhood Stock Token on Robinhood Chain, from SEC Form 4 filings of the last 90 days (the newest 40 at most; the window covered is stated): who (owner and relationship), the date, the transaction code in words, shares (signed by acquired or disposed), price (or "see footnote"), shares owned after, the Rule 10b5-1 flag and the filing link; a 4/A replaces its original; purchase and sale totals (codes P and S); plus the latest Schedule 13D/G filings naming the company. limit: rows to list (1 to 100, default 15). Foreign filers file no Form 4. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A stock ticker as Robinhood lists it (AAPL, NVDA, BRK.B) or the Stock Token's contract on Robinhood Chain (0x + 40 hex) |
| limit | integer | – | How many trade rows to list, 1 to 100 (default 15) |
No output schema declared.
No examples provided.
institutions Institutional holders (13F) ~261
Institutional holders of the company behind one Robinhood Stock Token on Robinhood Chain, from SEC's quarterly Form 13F data sets, by ticker (NVDA) or token contract: the top investment managers by shares for the latest quarter (limit: 1 to 20, default 10), each with its change vs the prior quarter (only managers that filed both quarters; one new this quarter says so), total institutional shares, the number of filers and the change over the managers present in both quarters. Puts and calls are left out; amendments are applied; a value that looks filed in thousands is flagged. Every answer starts with "13F for the quarter ended <date>, SEC data set published <date>". Funds and foreign issuers are not covered; a ticker without a reviewed CUSIP says 13F not mapped. 13F shares are the company's shares, not the Stock Token. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A stock ticker as Robinhood lists it (AAPL, NVDA, BRK.B) or the Stock Token's contract on Robinhood Chain (0x + 40 hex) |
| limit | integer | – | How many holders to list, 1 to 20 (default 10) |
No output schema declared.
No examples provided.
larp_check LARP check ~227
LARP check: is there a real product behind a coin on Robinhood Chain? Toll reads the coin's own site, launch post and code README, lists each thing it says it offers, and checks every claim against the chain and against its working parts that Toll tries itself (app page, API, MCP server, x402 payments, Chrome extension, Telegram bot, public code). Answers the label (product found / partly found / not found / not read: what we could check, never a verdict), each claim with found / partly / not found and the line that shows it, and the working parts that answered. A coin nobody asked about yet is queued and read within minutes: the answer says how many seconds to wait before calling again. Free: 25 new coins a day per caller, coins already read are always free.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Which chain: rh = Robinhood Chain. Leave it out for Robinhood Chain. |
| token | string | yes | The coin: its token contract on Robinhood Chain: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
launch_record Call at launch ~112
The call Toll made a few minutes after a Robinhood Chain coin launched, frozen and never edited: against / careful / clear (or launch facts only), the findings tallied, why, the dev's and funder's other coins of the week, and how it ended 24 hours later. Not the coin now: the current state is the coin's own check. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address on Robinhood Chain: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
macro US macro figures ~121
US macro figures for agents reading Robinhood Stock Tokens on Robinhood Chain, from public primary sources, each with its date: the Treasury daily par yield curve (1 month to 30 years), the New York Fed's effective federal funds rate with its target range, and from BLS the CPI-U change year on year, the unemployment rate and the monthly change in nonfarm payrolls (P = preliminary). No input. The EFFR is subject to the Terms of Use posted at newyorkfed.org; Toll is not affiliated with the New York Fed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_watches My watches ~59
The coins and the wallets your Toll key's wallet watches on Robinhood Chain: for each watch its id, token or address, url, paused (after 5 failed deliveries), fails, last read; never the secret. Needs a Toll key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pre_buy_check Gate before a buy ~300
For the moment before a buy ("should I buy this?", "should I ape this?"): Toll answers with facts, not advice. One call before buying a coin on Robinhood Chain: Toll reads the coin (its full coin check, counted in the same free coins) and answers Decision: BLOCK / WARN / ALLOW / WAIT with up to 3 reasons, most severe first, on Toll's calibrated pre-sign rules (BLOCK = a finding whose coins rugged at 40% or more within 24 h in Toll's calibration, a coin from one unnamed launcher contract with 50 or more of its last 7 days' coins scored and 80% or more of them rugged within 24 h (named launchpads never BLOCK on this), the coin's pool liquidity already pulled once, or sells that fail). WAIT means part of the coin is still being read: call again after the seconds given. Facts, not advice; ALLOW means nothing against was found in what was read, never a promise. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address you are about to buy on Robinhood Chain: 0x followed by 40 hex characters |
| budget_ms | integer | – | Optional: your time budget in ms (a trading bot's timeout, 300-25000). Not read in time = WAIT with the seconds to ask again; the read goes on, so the next call is fast. |
No output schema declared.
No examples provided.
presign_risk_report Pre-sign risk report ~404
Agent Pre-Sign Risk Report (ERC draft, ethereum/ERCs PR #2134): send a PresignRequest {version: "erc-presign/1", subject: {type: "calls", chainId: "eip155:4663", from: "eip155:4663:0x...", calls: [{to, value, data}], typedData?, authorizationList?}, context?: {payment?, texts?, tokens?}} and get a PresignReport: typed facts about the unsigned request on Robinhood Chain, each read or not read at one pinned block (approval amount, unlimited, share of supply, expiry, current allowance; address code; issuer listing of stock tokens; ERC-8470 launch observations; ERC-8478 payee binding; control characters, mixed scripts, addresses and injection classes (from our published pattern set) in text), bound to the request by digest and EIP-712 signed by Toll (ERC-8004 agent #20030). No verdict: apply your own policy, and treat not read as unknown, never as clean. Toll's ALLOW / WARN / BLOCK pre-sign answer carries this same report.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | Optional: {payment: {requirements (the x402 accepts entry chosen), resource?, payee?: {registry, agentId}}, texts: [{field, ref?, text}], tokens: [CAIP-10]} |
| kinds | array | – | Optional: only these finding kinds |
| subject | object | yes | {type: "calls", chainId: "eip155:4663", from: "eip155:4663:0x<signer>", calls: [{to, value (wei, decimal string), data}], typedData?, authorizationList? (EIP-7702: bound into the subject digest, list… |
| version | string | yes | Always "erc-presign/1" |
No output schema declared.
No examples provided.
stock_events Stock token events ~332
What changed on Robinhood's Stock Tokens on Robinhood Chain, oldest first: listed / delisted, multiplier_scheduled / multiplier_applied, corporate_action (status changes), feed_stale / feed_paused / feed_resumed (a Chainlink stock feed past its heartbeat while a session is open, or the token's oracle paused), and filing (SEC 8-K, 10-Q, 10-K, Form 4, Schedule 13D/G, by acceptance time). Each event has its id, source time (at, with what that time is) and when Toll found it. Pass since (the last answer's next) to get only newer events, kind to filter, limit (1 to 100). With a Toll key: Team (20M+ $TOLL) live, Pro (5M+) 15 minutes late; without one, the last 10 events found an hour ago or more, free. Funds and tickers with no SEC CIK get no filing events. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Only this kind: listed, delisted, multiplier_scheduled, multiplier_applied, corporate_action, feed_stale, feed_paused, feed_resumed, filing |
| limit | integer | – | How many events, 1 to 100 (default 25; the keyless preview is always the last 10) |
| since | integer | – | The next of the last answer (an event id): only newer events. Leave out for the newest. Applied with a Toll key (the keyless preview is always the last 10) |
No output schema declared.
No examples provided.
stock_token Stock token ~310
One Robinhood Stock Token (a tokenized security: debt issued by Robinhood Assets (Jersey) Ltd, not a share) on Robinhood Chain, by its ticker (NVDA, AAPL) or its token contract: Robinhood's listing (company, contract, shares per token and any announced change), Chainlink's reference price read on chain with its age and the US session (stale only past the feed's heartbeat while a session is open), the price in the token's deepest pool priced from the chain and its venue (Uniswap v3 or v4) with its liquidity, the difference vs the reference in percent (while the US market is closed: "market closed since <time>" and the pool vs the last close reference, past 5% named as not backed by a live market), the token's ERC-8056 multiplier read on chain ("1 token = N shares since <date>"), supply in shares, whether its oracle is paused, Robinhood's corporate actions (dividends, splits), and the company from SEC EDGAR (CIK, industry, exchange, latest 10-K / 10-Q / 8-K with links). Every number with its source and time; anything not read says so. Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A stock ticker as Robinhood lists it (NVDA, AAPL, BRK.B) or the Stock Token's contract on Robinhood Chain (0x + 40 hex) |
No output schema declared.
No examples provided.
stock_tokens Stock tokens ~144
The Stock Tokens Robinhood lists on Robinhood Chain (about 200): ticker, issuer's name, contract, Chainlink's reference price (or no feed) and its status, with how many have a feed, how many have SEC filings and how many corporate actions fall this month. Pass query (a ticker or part of a company name) to filter, limit for how many. Each row is one token; the full record of a token is its own lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many tokens, 1 to 250 (default 25) |
| query | string | – | Only tokens whose ticker or company contains this (NVDA, nvidia) |
No output schema declared.
No examples provided.
unwatch_coin Stop watching a coin ~42
Remove one of your coin watches on Robinhood Chain by its watch id. Needs a Toll key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The watch id (a uuid) |
No output schema declared.
No examples provided.
unwatch_wallet Stop watching a wallet ~43
Remove one of your wallet watches on Robinhood Chain by its watch id. Needs a Toll key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The wallet watch id (a uuid) |
No output schema declared.
No examples provided.
wallet_approvals Wallet approvals ~152
A wallet's live token approvals on Robinhood Chain: ERC-20 allowances, NFT approval-for-all and Permit2 allowances, newest first (at most 200, with how many more). Each one: the token, the spender (plain wallet or contract, and its name when Toll knows it), the amount (unlimited flagged), a risk (high / medium / low), and the revoke transaction (to, data, value 0) with Toll's pre-sign answer on it. Revoked, zero and expired allowances are left out. Facts read from the chain, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | The wallet address on Robinhood Chain: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
wallet_privacy Wallet privacy check ~111
What anyone can learn about a wallet from Robinhood Chain alone: a privacy grade (A to F), a score out of 100, and each leak found (who funded it, linked wallets, holdings, active hours, launches, trading record, linked accounts) with tips. The grade measures what anyone can see, not whether the wallet is good or bad. Robinhood Chain only.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | The wallet address on Robinhood Chain: 0x followed by 40 hex characters |
No output schema declared.
No examples provided.
watch_coin Watch a coin (webhook) ~226
Watch one Robinhood Chain coin for your agent: Toll re-reads it about every 10 minutes, and sooner after a trade or liquidity change (with more watched coins it takes longer), and POSTs a signed JSON event to your https url when its verdict word changes, a new finding against appears (liquidity pulled, wallets dumping together), or the dev's or a launch wallet group's sold share rises 5 points or more (dev_sold, cluster_sold). The first read sends nothing. Answers the watch id and, the first time, the secret that signs every event (x-toll-signature: sha256=<hex HMAC-SHA256(secret, raw body)>). Needs a Toll key; the cap is your tier's (3 / 20 / 50 / 100 by $TOLL held). Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The token contract address to watch on Robinhood Chain: 0x followed by 40 hex characters |
| url | string | yes | Your webhook: a public https URL on the default port |
No output schema declared.
No examples provided.
watch_wallet Watch a wallet (webhook) ~312
Watch one Robinhood Chain wallet for your agent (its own wallet, or one it trades with): Toll POSTs a signed JSON event to your https url when the wallet gives a new token approval (ERC-20, NFT approval-for-all or Permit2, with the spender and whether the amount is unlimited), signs a new EIP-7702 delegation, or receives a token whose Toll check is against; and, when the address is a smart account (a Safe, a Zodiac Roles or Delay module, an ERC-7579 account), when who can move its funds changes (event account_permission: a module enabled, a guard or fallback handler set, a signer or threshold change, a Zodiac role or permission, the Delay waiting period, an ERC-7579 module installed; each with a severity and plain words). Answers the watch id and, the first time, the secret that signs every event (x-toll-signature: sha256=<hex HMAC-SHA256(secret, raw body)>). Each approval alert names the spender and amount so it can be revoked. Needs a Toll key; wallet watches have their own cap, the same size as your tier's coin watches (3 / 20 / 50 / 100 by $TOLL held). Facts, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The wallet address to watch on Robinhood Chain: 0x followed by 40 hex characters |
| url | string | yes | Your webhook: a public https URL on the default port |
No output schema declared.
No examples provided.
How do I install the Toll MCP server?
Toll is a hosted endpoint at https://t0ll.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · t0ll.xyz
claude mcp add --transport http t0ll-xyz-toll 'https://t0ll.xyz/mcp'
What is the Toll MCP server?
Toll is an MCP server listed in the public MCP registry as io.github.t0ll-xyz/toll. Robinhood Chain checks for agents: coins, devs, ERC-8004 agents, pre-sign check, Stock Token data. This page covers its hosted endpoint (https://t0ll.xyz/mcp).
Is the Toll MCP server safe to use?
Toll scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Toll MCP server expose?
Toll exposes 33 tools: check_coin, pre_buy_check, check_coins, larp_check, dev_record, and 28 more. Their descriptions and schemas cost roughly 8,944 tokens of context every time the server is loaded.
Does the Toll MCP server require authentication?
No. We connected to Toll without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Toll MCP server still maintained?
Toll is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Toll MCP server?
VerifyMCP ran 13 checks on Toll, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.