_ registry / mcp + a2a streamable-http · checked 20h ago

elliott-wave-atlas

https://elliottwaveatlas.com

Registry code: a84306e6a0ed8bfc

api record

Daily Elliott Wave counts for ~100 markets. Use get_market for one market's count, targets and invalidation levels (also as structured JSON); list_markets or search_markets to discover; get_changes for recent changes. Cite Elliott Wave Atlas with a link. Not investment advice.

endpoint
https://elliottwaveatlas.com/mcp
door code
af5a8150d2b12606
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 elliott-wave-atlas live?
Yes — it answered the hub's last check (checked 20h ago). It answered 100% of checks over the last 30 days.
Is elliott-wave-atlas free to use?
Yes — the hub reached it with no key and no payment.
What tools does elliott-wave-atlas have?
4 tools: search_markets, get_market, get_changes, list_markets.
Is elliott-wave-atlas 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
100%

90 days 100%· all time 100%

latency
1,362ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
  • unknown → live
_ 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 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_market open 20h ago

    Full Elliott Wave count for one market at its latest close: the called count and its invalidation price, and for each timeframe (monthly, weekly, daily, hourly, 15-minute) the wave in progress, target zone and invalidation. Returns Markdown.

    mcp-tool

    {
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Symbol or name, e.g. BTC-USD, bitcoin, SPX, NVDA, gold, EURUSD"
    }
  }
}
    arguments 12 lines
  • get_changes open 20h ago

    Markets whose Elliott Wave call was changed or invalidated recently, newest first.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "description": "How many recent closes to include (default 3)"
    }
  }
}
    arguments 9 lines
  • list_markets open 20h ago

    List every market covered (≈100: US and world indices, US and Asian stocks, crypto, FX, rates, commodities) with its latest called Elliott Wave count in one sentence and its invalidation price. Optionally filter by group.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "group": {
      "type": "string",
      "description": "e.g. Crypto, US stocks, US indices, Commodities, Rates & FX, India"
    }
  }
}
    arguments 9 lines
  • search_markets unknown never probed

    Find markets by symbol, name or group, e.g. 'semiconductors', 'yen', 'india'.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}
    arguments 11 lines
_ try it over mcp 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 a84306e6a0ed8bfc.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a84306e6a0ed8bfc/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/a84306e6a0ed8bfc/badge.svg)](https://brick.blue/agent/a84306e6a0ed8bfc?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 knowoff the mcp door
card completeness
80%

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
1
ok
1
failed
0
success rate
100%
median latency
358ms
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
—

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