Skip to content

Crypto prices and ZEC ETF flows

pro.megahard/coinsmegahard.prostreamable-httpv1.0.0Scanned

Live USD prices for the top 100 cryptocurrencies, plus a daily BUY/HOLD/SELL signal for Zcash.

3 tools: 3 only read.

Tools: 0 delete, 0 irreversible, 0 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

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_crypto_pricesLive USD prices for the top 100 cryptocurrencies by market cap: rank, name, symbol, price, 1h / 24h / 7d percent change, market cap and 24h volume.No findings

    Why it is in this group

    • The name "get_crypto_prices" says "get": a word for reading.
    Description, as the server wrote it
    Live USD prices for the top 100 cryptocurrencies by market cap: rank, name, symbol, price, 1h / 24h / 7d percent change, market cap and 24h volume. Data from CoinGecko, at most about 60 s old. Pass symbols (tickers like "btc", or CoinGecko ids / names like "ethereum") for specific coins, or omit them for the top N by market cap. Coins outside the top 100 are not available.

    Annotations the server declares

    • title: Crypto prices (top 100)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • 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

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.

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 coins https://coins.megahard.pro/mcp
claude mcp add --transport http coins https://coins.megahard.pro/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__coins__get_crypto_prices",
      "mcp__coins__get_zec_etf_signal",
      "mcp__coins__get_zec_etf_history"
    ],
    "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 coins. 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://anlyon.dev/api/v1/servers/pro.megahard/coins/verify?hash=275c06e7690d0b9d3e6aa8fbdcc1b1910aa7f15e382806cdae20cb1305c0b282" | jq -e '.changed == false'

Pinned hash 275c06e7690d, from Oct 29, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/pro.megahard/coins/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

anlyon.dev badge for pro.megahard/coins
[![anlyon.dev](https://anlyon.dev/badge/pro.megahard/coins.svg)](https://anlyon.dev/servers/pro.megahard/coins)

Source: MCP Registry. Synced Oct 29, 2026, 12:18 UTC.