ZEC ETF flows indicator MCP server
pro.megahard/zecmegahard.prostreamable-httpv1.0.0Scanned
Daily BUY/HOLD/SELL signal for Zcash from US spot ETF creations and redemptions, with history.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ZEC ETF flows indicator MCP server can do
The ZEC ETF flows indicator MCP server is published by megahard.pro, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
get_zec_etf_historyDaily history of the ZEC ETF flows indicator, oldest day first: the signal and score, the BUY / SELL thresholds in force, and per day the net ETF flow in ZEC and USD, 5-day flow, f…No findings
Why it is in this group
- The name "get_zec_etf_history" says "get": a word for reading.
Description, as the server wrote it Daily history of the ZEC ETF flows indicator, oldest day first: the signal and score, the BUY / SELL thresholds in force, and per day the net ETF flow in ZEC and USD, 5-day flow, flow streak, ETF holdings and AUM, premium to NAV and the ZEC price. History starts on 2026-09-07. Optionally adds each day's component scores and rationale. Informational only, not investment advice.
Annotations the server declares
- title: ZEC ETF flows signal history
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_zec_etf_signalThe current ZEC ETF flows indicator: a daily BUY / HOLD / SELL signal for Zcash built from creations and redemptions in US spot Zcash ETFs (Grayscale ZCSH), scored together with pr…No findings
Why it is in this group
- The name "get_zec_etf_signal" says "get": a word for reading.
Description, as the server wrote it The current ZEC ETF flows indicator: a daily BUY / HOLD / SELL signal for Zcash built from creations and redemptions in US spot Zcash ETFs (Grayscale ZCSH), scored together with premium to NAV, derivatives leverage and funding, spot taker imbalance, open interest trend, shielded pool growth, volume share, SEC EDGAR filings and the price regime. Returns the signal, total score, each component's score and reason, the raw inputs, an LLM-written rationale (it may only downgrade the computed signal), the tracked funds and recent classified filings. Recomputed once a day after the US close; "stale" is true when the ETF data is more than two business days old. Informational only, not investment advice.
Annotations the server declares
- title: ZEC ETF flows signal (today)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_zec_quoteCurrent Zcash (ZEC) price in USD with 1h / 24h / 7d percent change, market cap rank, market cap and 24h volume.No findings
Why it is in this group
- The name "get_zec_quote" says "get": a word for reading.
Description, as the server wrote it Current Zcash (ZEC) price in USD with 1h / 24h / 7d percent change, market cap rank, market cap and 24h volume. CoinGecko data, at most about 60 s old.
Annotations the server declares
- title: Zcash (ZEC) price
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:24 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http zec https://zec.megahard.pro/mcpclaude mcp add --transport http zec https://zec.megahard.pro/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__zec__get_zec_etf_signal",
"mcp__zec__get_zec_etf_history",
"mcp__zec__get_zec_quote"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as zec. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/pro.megahard/zec/verify?hash=f5fb90b69b2af416f37cccc5b29b14d7293bc899e727e5e96e61a78f9774fe4e" | jq -e '.changed == false'Pinned hash f5fb90b69b2a, from Nov 10, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/pro.megahard/zec/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/pro.megahard/zec)Source: MCP Registry. Synced Oct 29, 2026, 13:19 UTC.
ZEC ETF flows indicator MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ZEC ETF flows indicator MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the ZEC ETF flows indicator MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ZEC ETF flows indicator MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ZEC ETF flows indicator MCP server have?
- 3 tools: 3 read. get_zec_etf_signal, get_zec_etf_history and get_zec_quote.
Does the ZEC ETF flows indicator MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ZEC ETF flows indicator MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ZEC ETF flows indicator MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.