Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DeFi Capital Flow-Price Gap

REMOTE · DEFI-FLOW.ONCHAINPROOF.WORKERS.DEV

Daily on-chain DeFi capital inflow vs token price, Bitcoin-timestamped. Free and x402-paid tools.

64 Trust /100

Last scanned (21 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability43
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1317 tokens (~101/item across 13 items; 10 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 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
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_holder_value” rewrote its description, which is the text the model reads security
    • Tool “get_inflow_assets” rewrote its description, which is the text the model reads security
    • Tool “get_signal” rewrote its description, which is the text the model reads security
    • Tool “get_token_signal” rewrote its description, which is the text the model reads security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 61

    First indexed and scored.

Diagnostics

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://defi-flow.onchainproof.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onchainproof.workers.dev CN=YE2,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA384 6342c9e7df9c754aaea12765712611f1b51
SANs: *.onchainproof.workers.dev, onchainproof.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 defi-flow.onchainproof.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://defi-flow.onchainproof.workers.dev/mcp Verified 200
http (plaintext) http://defi-flow.onchainproof.workers.dev/mcp Inconclusive 405
MCP tools · 10 exposed · ~1,103 tokens

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 →

Tool Tokens
get_coverage ~39

Free. What is measured today: chains, protocols, tokens and data sets, generated from the data itself. Same JSON as GET /coverage.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_free_signal ~106

Free. The full daily signal (all tokens: protocol capital inflow vs price gap, tier and reason, holder value fields, risk flag) of a data day older than 7 days, CC BY 4.0, with its proof fields. Argument date: YYYY-MM-DD (see list_free_days). Same JSON as GET /free/{date}/signal.json. Informational, not investment advice.

NameTypeReqDescription
datestringyesdata day, YYYY-MM-DD (UTC)

No output schema declared.

No examples provided.

get_holder_value ~143

Holder value for 11 DeFi tokens on Ethereum: revenue, burn, buyback, payouts, dilution and net, first-party on-chain. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Paid: $0.02 USDC on Base with x402 inside the MCP call (_meta["x402/payment"]); without payment the tool returns the x402 PaymentRequired result and nothing is charged. Same JSON as GET /v1/holder-value.

NameTypeReqDescription
receiptstring–optional: refetch.receipt from an earlier paid answer of the same tool - the same data again without payment (terms 2b)

No output schema declared.

No examples provided.

get_inflow_assets ~144

Asset-level protocol TVL inflow/outflow for 11 DeFi tokens on Ethereum: first-party on-chain reads at a fixed daily block. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Paid: $0.02 USDC on Base with x402 inside the MCP call (_meta["x402/payment"]); without payment the tool returns the x402 PaymentRequired result and nothing is charged. Same JSON as GET /v1/inflow/assets.

NameTypeReqDescription
receiptstring–optional: refetch.receipt from an earlier paid answer of the same tool - the same data again without payment (terms 2b)

No output schema declared.

No examples provided.

get_proof ~79

Free. The SHA-256 fingerprint file and the OpenTimestamps Bitcoin proof of a data day, its Bitcoin status and block, and how to verify it yourself (ready-made code: /examples/). Argument date: YYYY-MM-DD. From GET /verify/index.json.

NameTypeReqDescription
datestringyesdata day, YYYY-MM-DD (UTC)

No output schema declared.

No examples provided.

get_signal ~177

All 11 DeFi tokens on Ethereum, daily: first-party on-chain protocol TVL inflow/outflow (not resold) vs price gap; tiers + reasons. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Track record per tier (A/B/C, rules fixed in advance and Bitcoin-timestamped) in every response; predictive power not yet proven live. Paid: $0.01 USDC on Base with x402 inside the MCP call (_meta["x402/payment"]); without payment the tool returns the x402 PaymentRequired result and nothing is charged. Same JSON as GET /v1/signal.

NameTypeReqDescription
receiptstring–optional: refetch.receipt from an earlier paid answer of the same tool - the same data again without payment (terms 2b)

No output schema declared.

No examples provided.

get_status ~70

Free. Today's data day and its age, the quality gate, whether paid tools are open (paid_routes_open), the Bitcoin proof status of today's fingerprint, the token list (token_symbols) and each tier's track-record verdict. Same JSON as GET /v1/status. Informational, not investment advice.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_token_signal ~205

One DeFi token (argument token): first-party on-chain TVL inflow/outflow vs price gap, tier + reason. All 11 tokens: /v1/signal $0.01. Bitcoin-timestamped; free proof: /verify/index.json. Informational, not investment advice. Track record per tier (A/B/C, rules fixed in advance and Bitcoin-timestamped) in every response; predictive power not yet proven live. Paid: $0.005 USDC on Base with x402 inside the MCP call (_meta["x402/payment"]); without payment the tool returns the x402 PaymentRequired result and nothing is charged. Same JSON as GET /v1/signal/{token}.

NameTypeReqDescription
receiptstring–optional: refetch.receipt from an earlier paid answer of the same tool - the same data again without payment (terms 2b)
tokenstringyestoken symbol (the list: get_status, field token_symbols)

No output schema declared.

No examples provided.

get_track_record ~78

Free. Track record per signal tier: backtest verdicts (A works / B partial / C not distinguishable from luck) per methodology version, observation counts, the thresholds, Bitcoin proofs, the live record and the price policy. A tier name describes the measured state, not how well it is proven. Same JSON as GET /performance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_free_days ~62

Free. Every data day older than 7 days, free under CC BY 4.0 and byte-identical to the Bitcoin-timestamped originals: date, link to the full signal, fingerprint and Bitcoin status. Compact view of GET /free/index.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the DeFi Capital Flow-Price Gap MCP server?

DeFi Capital Flow-Price Gap is a hosted endpoint at https://defi-flow.onchainproof.workers.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 · defi-flow.onchainproof.workers.dev

# add to Claude Code
claude mcp add --transport http zsraduly77-defi-flow-price-gap 'https://defi-flow.onchainproof.workers.dev/mcp'
Common questions

What is the DeFi Capital Flow-Price Gap MCP server?

DeFi Capital Flow-Price Gap is an MCP server listed in the public MCP registry as io.github.zsraduly77/defi-flow-price-gap. Daily on-chain DeFi capital inflow vs token price, Bitcoin-timestamped. Free and x402-paid tools. This page covers its hosted endpoint (https://defi-flow.onchainproof.workers.dev/mcp).

Is the DeFi Capital Flow-Price Gap MCP server safe to use?

DeFi Capital Flow-Price Gap scores 64 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 DeFi Capital Flow-Price Gap MCP server expose?

DeFi Capital Flow-Price Gap exposes 10 tools: get_status, get_track_record, get_coverage, list_free_days, get_free_signal, and 5 more. Their descriptions and schemas cost roughly 1,103 tokens of context every time the server is loaded.

Does the DeFi Capital Flow-Price Gap MCP server require authentication?

No. We connected to DeFi Capital Flow-Price Gap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DeFi Capital Flow-Price Gap MCP server still maintained?

DeFi Capital Flow-Price Gap 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 DeFi Capital Flow-Price Gap MCP server?

VerifyMCP ran 12 checks on DeFi Capital Flow-Price Gap, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about DeFi Capital Flow-Price Gap: HTTPS. 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.