A3E Ecosystem MCP server

Which servers in the official MCP registry are A3E Ecosystem's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to A3E Ecosystem

Whose server it is

Registry namecom.a3eecosystem.neurotrade/signalverified in the MCP registry

The registry name sits under a3eecosystem.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools2
Server calls itselfneurotrade-signal-api
Server version1.0.0
Protocol version2024-11-05

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 328 ms.

Measured dailydaily checks: 2, the first on 2026-10-19

Answeredmeasuring2 of the 7 daily checks it takes to print a share
Median first answer396 ms
Space in an agent's context≈ 486 tokensthe definitions of all its tools (2), which an agent carries on every turn
Tool definitionsB · 83 of 100

Not saying whether it only reads or can destroy: 2 of 2

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-19

generate_signal
Generate an AI-powered crypto trading signal for a given pair and timeframe. Returns: action (OPEN_LONG | OPEN_SHORT | CLOSE), confidence (0.0–1.0), entry_price, take_profit (array of price levels), stop_loss, risk_reward ratio…
get_account
Return the current NeuroTrade B2B API quota status: plan tier, calls used, calls remaining, and quota reset date. Requires a valid NeuroTrade B2B API key.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "signal": {
      "type": "http",
      "url": "https://neurotrade.a3eecosystem.com/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.