Koskamo

Elliott Wave Atlas MCP

An official MCP server providing daily Elliott Wave technical analysis counts for 100 financial markets including indices, stocks, crypto, FX, and commodities. It offers tools to list markets, retrieve detailed wave counts with targets and invalidation levels, search by symbol or group, and track recent changes in market calls.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Elliott Wave Atlas MCP logo, by Elliott Wave AtlasVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-08Operated by Elliott Wave Atlas
MCP endpoint (Streamable HTTP)
https://elliottwaveatlas.com/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 0 of 4 declare behavior hints · 3 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to elliottwaveatlas.com ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Retrieve daily Elliott Wave counts and invalidation levels for specific assets
  • List all tracked markets with their current wave bias
  • Search for markets by symbol, name, or sector group
  • Identify markets with recently revised or invalidated wave calls

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
elliott-wave-atlas 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

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

Tools

4 advertised

list_markets
Advertised by the server during the last successful anonymous check.

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.

list_markets input schema
{
  "type": "object",
  "properties": {
    "group": {
      "type": "string",
      "description": "e.g. Crypto, US stocks, US indices, Commodities, Rates & FX, India"
    }
  }
}
get_market
Advertised by the server during the last successful anonymous check.

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, invalidation and time window. Returns Markdown.

get_market input schema
{
  "type": "object",
  "required": [
    "symbol"
  ],
  "properties": {
    "symbol": {
      "type": "string",
      "description": "Symbol or name, e.g. BTC-USD, bitcoin, SPX, NVDA, gold, EURUSD"
    }
  }
}
get_changes
Advertised by the server during the last successful anonymous check.

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

get_changes input schema
{
  "type": "object",
  "properties": {
    "days": {
      "type": "number",
      "description": "How many recent closes to include (default 3)"
    }
  }
}
search_markets
Advertised by the server during the last successful anonymous check.

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

search_markets input schema
{
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (4 of 4 answered).

  1. 2026-11-09: 2 of 2 checks answered
  2. 2026-11-10: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
504 ms
95th percentile latency
504 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 504 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http elliott-wave-atlas-mcp https://elliottwaveatlas.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add elliott-wave-atlas-mcp --url https://elliottwaveatlas.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable elliott-wave-atlas-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "elliott-wave-atlas-mcp": {
      "url": "https://elliottwaveatlas.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "elliott-wave-atlas-mcp": {
      "type": "streamableHttp",
      "url": "https://elliottwaveatlas.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start elliott-wave-atlas-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "elliott-wave-atlas-mcp": {
      "type": "http",
      "url": "https://elliottwaveatlas.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http elliott-wave-atlas-mcp https://elliottwaveatlas.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://elliottwaveatlas.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "elliott-wave-atlas-mcp": {
      "serverUrl": "https://elliottwaveatlas.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Elliott Wave Atlas MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Elliott Wave Atlas MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing