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

ALGOMetrics

https://api.algometrics.org

Registry code: 1c4093ccc13dff56

api record

ALGO-USD adverse-selection risk from Coinbase trade data: VPIN, its 0.5 threshold status, and interpretation guidance

from a public catalogue that lists it, not from the operator

endpoint
https://api.algometrics.org/mcp
protocol
streamable-http ·2025-06-18
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 ALGOMetrics live?
Yes — it answered the hub's last check (checked 3h ago). It answered 98% of checks over the last 30 days.
Is ALGOMetrics free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does ALGOMetrics have?
8 tools: project_algorand_supply, get_algorand_staking, get_algometrics_methodology, get_algorand_issuance, get_algorand_fees, get_algorand_microstructure_interpretation, get_algorand_microstructure, get_algorand_summary.
Is ALGOMetrics 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%

90 days 98.6%· all time 98.6%

latency
266ms

last good check

priced tools
5

of 8 tools

_ answered our checks, 90 days 281 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
crypto & onchain onchain analytics
used for
  • get algorand fee and burn metrics
  • get algorand staking metrics
  • get algo market microstructure
  • project algorand supply
takes → gives
data → data, text
tools
8 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 8 tools
5 paid2 open 1 never probed 7 of 8 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_algorand_issuance reads 0.01 31566704 paid 45d ago

    Get Algorand issuance, reward-rate, and net supply change metrics.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_algorand_fees reads 0.01 31566704 paid 46d ago

    Get Algorand protocol fee and burn metrics.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_algorand_microstructure_interpretation reads 0.05 31566704 paid 46d ago

    Get a Claude-generated interpretation of current ALGO-USD market conditions (regime, adverse selection, volatility, liquidity, execution implications) with the metrics snapshot it was based on. Generates a fresh reading when the cached one has expired, so this tool is charged at the premium rate rather than the base rate that the other tools use.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_algorand_microstructure reads 0.01 31566704 paid 46d ago

    Get ALGO-USD market microstructure metrics from Coinbase trade data: VPIN (adverse selection risk), order-flow imbalance, flow autocorrelation, Kyle lambda, realized and Parkinson volatility, VWAP, Amihud illiquidity, and Roll spread. Updated once per minute.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_algorand_summary reads 0.01 31566704 paid 46d ago

    Get summary Algorand protocol economics metrics.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_algorand_staking reads open 46d ago

    Get Algorand online-stake and decentralization metrics.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_algometrics_methodology reads open 46d ago

    Get published methodology notes for ALGOMetrics metrics.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • project_algorand_supply reads unknown never probed

    Project supply-change scenarios from current issuance and fee burn estimates.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 3650,
      "minimum": 1
    },
    "daily_fee_burn_algos": {
      "type": "number",
      "minimum": 0
    },
    "annual_issuance_decay": {
      "type": "number",
      "maximum": 1,
      "minimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 20 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 1c4093ccc13dff56.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1c4093ccc13dff56/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/1c4093ccc13dff56/badge.svg)](https://brick.blue/agent/1c4093ccc13dff56?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.