_ registry / mcp streamable-http · checked 2h ago

cryptoiz-mcp

https://mcp.cryptoiz.org

Registry code: e600958b1da03a75

api record

Crypto signals: Solana whale accumulation and distribution phases, BTC macro regime and futures signals, and Solana token address lookup.

endpoint
https://mcp.cryptoiz.org/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is cryptoiz-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is cryptoiz-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does cryptoiz-mcp have?
9 tools: get_token_ca, get_status, get_btc_regime, get_whale_alpha, get_btc_futures_signal, get_whale_distribution, get_whale_divergence, get_whale_neutral, ….
Is cryptoiz-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.8%

90 days 98.9%· all time 98.9%

latency
294ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 449 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find whale accumulation on solana
  • get bitcoin regime and fear greed
  • get btc futures signals
  • look up a solana token address
takes → gives
text → data
tools
9 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
7 auth-required 2 never probed 7 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_btc_regime reads auth-required 4h ago

    BTC macro regime + Fear/Greed + technicals. Cost: $0.01 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_whale_alpha reads auth-required 21h ago

    Get top 20 whale/dolphin accumulation signals on Solana DEX. Cost: $0.05 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_btc_futures_signal reads auth-required never probed

    BTC MTF futures scalp signal (35x leverage). Cost: $0.03 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_whale_distribution reads auth-required 21h ago

    Tokens in distribution phase (smart money exit). Cost: $0.02 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_whale_divergence reads auth-required 21h ago

    Whale divergence signals (Hidden Accumulation, Breakout, Classic). Cost: $0.02 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "tf": {
          "type": "string",
          "default": "4h"
        }
      }
    }
    arguments 10 lines
  • get_whale_neutral reads auth-required 4h ago

    Tokens in neutral phase. Cost: $0.02 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_whale_accumulation reads auth-required 4h ago

    Tokens in accumulation phase. Cost: $0.02 USDC. Requires x-api-key or x-payment.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
  • get_token_ca reads unknown 13h ago

    FREE. Lookup Solana token contract address by name.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • get_status reads unknown 13h ago

    FREE. Check CryptoIZ MCP server status.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e600958b1da03a75.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e600958b1da03a75/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e600958b1da03a75/badge.svg)](https://brick.blue/agent/e600958b1da03a75?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on cryptoiz.org 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.