dev.fly.obol-x402/obol
REMOTE · OBOL-MCP.FLY.DEV · SCANNED AUG 20
Pre-trade safety verdicts for agents: token rug/honeypot, calldata guard, wallet risk — signed x402.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the dev.fly.obol-x402/obol MCP server?
dev.fly.obol-x402/obol is a hosted endpoint at https://obol-mcp.fly.dev/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 · obol-mcp.fly.dev
claude mcp add --transport http dev-fly-obol-x402-obol 'https://obol-mcp.fly.dev/mcp'
{
"mcpServers": {
"dev-fly-obol-x402-obol": {
"url": "https://obol-mcp.fly.dev/mcp"
}
}
} {
"servers": {
"dev-fly-obol-x402-obol": {
"type": "http",
"url": "https://obol-mcp.fly.dev/mcp"
}
}
} [mcp_servers.dev-fly-obol-x402-obol] url = "https://obol-mcp.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-fly-obol-x402-obol": {
"type": "remote",
"url": "https://obol-mcp.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-fly-obol-x402-obol --url 'https://obol-mcp.fly.dev/mcp' --transport streamable-http
mcp_servers:
dev-fly-obol-x402-obol:
url: "https://obol-mcp.fly.dev/mcp" {
"McpServers": {
"dev-fly-obol-x402-obol": {
"Transport": "http",
"Url": "https://obol-mcp.fly.dev/mcp"
}
}
} assistant mcp add dev-fly-obol-x402-obol -t streamable-http -u 'https://obol-mcp.fly.dev/mcp'
{
"mcpServers": {
"dev-fly-obol-x402-obol": {
"type": "http",
"url": "https://obol-mcp.fly.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 20 Aug 2026 · Probed https://obol-mcp.fly.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of obol-mcp.fly.dev. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| obol-mcp.fly.dev. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://obol-mcp.fly.dev/mcp | Unreachable | ||
| http (plaintext) | http://obol-mcp.fly.dev/mcp | HTTPS enforced |
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 →
agent_counterparty_trust ~107
Is this x402 seller/agent REAL or a wash shell? Listing presence across Bazaar/PayAI/402index + recent Base USDC inflow forensics (distinct payers, concentration) → signed ESTABLISHED|ACTIVE_UNPROVEN|CONCENTRATED|GHOST verdict. ~50% of x402 volume is self-dealing — check before you pay. $0.10 USDC on Base via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| payTo | string | yes | – |
No output schema declared.
No examples provided.
bitcoin_address_intelligence ~62
Bitcoin address behavioral fingerprint (PLEXUS): vault, exchange, consolidator, distributor, whale, or ordinary — with balance/throughput. Counterparty screening before sending BTC. $0.10 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
bitcoin_market_intelligence ~58
Bitcoin market-intelligence digest: current BTC market REGIME (calm/active-stress/mixed) from cross-exchange spot integrity, fee/congestion regime, and block-anomaly state. $0.10 USDC on Base.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bitcoin_patoshi_provenance ~53
Bitcoin Patoshi-era provenance: is this early block from the Patoshi-dominant fingerprint period? TIMECHAIN forensic IP. $0.10 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | – |
No output schema declared.
No examples provided.
bitcoin_tx_intelligence ~63
Bitcoin tx structural intelligence (PLEXUS): classify money-movement role (consolidation/fan-out/payment), whale-tier, value-homophily. Not raw RPC. $0.10 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| txid | string | yes | – |
No output schema declared.
No examples provided.
check_evm_address ~91
Address risk profile for any EVM address on base, ethereum, arbitrum, optimism, polygon, bnb, or robinhood chain: EOA vs contract, activity, dormancy, proxy, risk score. Screen before send/approve. Args: address, chain (default base). $0.10 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
check_evm_token ~102
Token safety / rug-risk report for any EVM token on base, ethereum, arbitrum, optimism, polygon, bnb, or robinhood chain: ownership, proxy, mint, ERC-20 conformance, composite risk verdict. Call before buy/approve. Args: address, chain (default base). Payment is always $0.10 USDC on Base regardless of chain analyzed.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
evm_trade_verdict ~129
ONE call, one decision: should this exact EVM trade go through? Composes token risk report + honeypot sell-sim (+ calldata guard with to/data, + wallet risk) → signed PROCEED|PROCEED_WITH_CAPS|ABORT, 90s TTL. The only bundle with a pre-sign calldata leg. $0.25 USDC on Base via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| data | – | – | – |
| notional_usd | – | – | – |
| to | – | – | – |
| token | string | yes | – |
| wallet | – | – | – |
No output schema declared.
No examples provided.
get_bitcoin_mempool_fees ~62
Bitcoin broadcast-timing pulse: next-block fee sat/vB, trend, broadcast verdict, mempool congestion, fee-spike, tip, spot. Should I broadcast BTC now? $0.05 USDC on Base via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_bitcoin_signal ~60
Validation-gated Bitcoin block anomaly detector for a height: fee-exceeds-subsidy, empty block, retarget, timestamp inversion, long gap, coinbase message. $0.01 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | – |
No output schema declared.
No examples provided.
get_crypto_prices ~47
USD spot prices for BTC ETH SOL USDC USDT in ONE call — Coinbase+Kraken cross-exchange with divergence flag. $0.01 USDC on Base via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_obol_intel_pack ~56
OBOL flagship intelligence pack: Bitcoin market REGIME + broadcast-timing pulse + tip anomaly scan + multi-asset spots in ONE payment. Maximum decision density. $0.25 USDC on Base via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
obol_calldata_guard ~124
PRE-SIGN calldata guard: decode what a transaction ACTUALLY does before signing — detects unlimited approve(), setApprovalForAll, EIP-2612/Permit2 grants, and drains hidden inside multicall batches. Returns decoded intent + flags + policy ALLOW|CONFIRM|BLOCK. Args: to, data, frm, value. $0.05 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| data | string | yes | – |
| frm | string | – | – |
| to | string | yes | – |
| value | string | – | – |
No output schema declared.
No examples provided.
obol_catalog ~51
FREE. What OBOL sells and how to pay for it: every tool, its price in USDC, and the exact x402 payment shape. Call this first if a paid tool returned 'Payment Required'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
obol_evm_sell_sim ~152
EVM honeypot / sell-simulation — if you BUY this token, can you SELL it back? The dynamic two-way tradability gate the static rug check cannot answer: KyberSwap two-way round-trip FUSED with a sellability simulation on every chain (honeypot.is fork sim on base/ethereum/bnb, GoPlus on arbitrum/optimism/polygon). Buyable-but-not-sellable = honeypot BLOCK; verdict ALLOW|CAUTION|BLOCK, never ALLOW from a partial result. Args: address, chain (default base). $0.15 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| chain | string | – | – |
No output schema declared.
No examples provided.
obol_launch_feed ~125
Fresh token launches with a SAFETY VERDICT overlaid — the habit feed for trading/sniper agents: dexscreener launch attention (boosts + new profiles) enriched with best-pair liquidity/fdv and OBOL's GoPlus-fused token verdict per token. Covers base, ROBINHOOD CHAIN (no rival feed has a safety overlay there), ethereum, arbitrum, optimism, polygon, bnb. Empty list is never charged. Args: chain (default base). $0.05 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
No output schema declared.
No examples provided.
obol_risk_ritual ~161
OBOL risk ritual — pre-action JUDGE pack, MULTI-CHAIN (base, ethereum, arbitrum, optimism, polygon, bnb, robinhood): token safety and/or address risk and/or tx preflight + calldata drain decode. Args: token, address, to, data, frm, value, chain (provide ≥1 of token/address/to). Returns policy allow/caution/deny. $0.30 USDC on Base. Call before buy, send, or sign.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| chain | string | – | – |
| data | string | – | – |
| frm | string | – | – |
| to | string | – | – |
| token | string | – | – |
| value | string | – | – |
No output schema declared.
No examples provided.
obol_trading_tick ~63
OBOL trading tick — poll EVERY agent cycle: Bitcoin market REGIME + broadcast-timing pulse + multi-asset spots + machine action policy (ok_to_act / hold / wait / recheck). One settle per loop. $0.20 USDC.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
obol_whale_watch ~57
OBOL whale watch: Bitcoin market REGIME + PLEXUS address behavioral fingerprint for a BTC address. Who is this counterparty under current market stress? $0.20 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| btc_address | string | yes | – |
No output schema declared.
No examples provided.
simulate_evm_tx ~106
Simulate an EVM tx BEFORE signing on base, ethereum, arbitrum, optimism, polygon, bnb, or robinhood chain: succeed/revert, reason, gas estimate. Args: to, data, frm, value, chain (default base). $0.10 USDC on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| data | string | – | – |
| frm | string | – | – |
| to | string | yes | – |
| value | string | – | – |
No output schema declared.
No examples provided.
validate_agent_output ~112
ERC-8004 Validator seat: submit a counterparty agent's output (+ Ed25519 attestation) → independent signed pass|fail (signature, coherence, integrity flags, freshness, self-claims) + ERC-8004 Validation-Registry-ready sha256 digests. Fail-closed: nothing checkable = withheld, no charge. $0.25 USDC on Base via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| attestation_json | – | – | – |
| payload_json | string | yes | – |
| pubkey_b64 | – | – | – |
No output schema declared.
No examples provided.
What is the dev.fly.obol-x402/obol MCP server?
dev.fly.obol-x402/obol is an MCP server listed in the public MCP registry as dev.fly.obol-x402/obol. Pre-trade safety verdicts for agents: token rug/honeypot, calldata guard, wallet risk, signed x402. This page covers its hosted endpoint (https://obol-mcp.fly.dev/mcp).
Is the dev.fly.obol-x402/obol MCP server safe to use?
dev.fly.obol-x402/obol scores 0 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 dev.fly.obol-x402/obol MCP server expose?
dev.fly.obol-x402/obol exposes 21 tools: obol_catalog, agent_counterparty_trust, validate_agent_output, evm_trade_verdict, obol_trading_tick, and 16 more. Their descriptions and schemas cost roughly 1,841 tokens of context every time the server is loaded.
Does the dev.fly.obol-x402/obol MCP server require authentication?
Its publisher declares no required credentials for dev.fly.obol-x402/obol. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the dev.fly.obol-x402/obol MCP server still maintained?
dev.fly.obol-x402/obol has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 26 July 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.