Is the Imrane2019 Alphabotpro MCP server down?

mcp-registry/io.github.imrane2019/alphabotpro · v1.0.0

Also listed as github/imrane2019/mcp-x402-example

healthy
Last checked 2026-10-19 16:10 UTC · handshake 106ms

As of 2026-10-19 16:10 UTC, the Imrane2019 Alphabotpro MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,857
outages (90d)
0
tools
9

Live XAUUSD/BTCUSD trading signals, priced in USD, payable by AI agents via crypto (x402).

Install Imrane2019 Alphabotpro MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http imrane2019-alphabotpro-mcp-server https://mcp.alphabotpro.cloud/v1/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "imrane2019-alphabotpro-mcp-server": {
      "type": "http",
      "url": "https://mcp.alphabotpro.cloud/v1/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 9 tool(s); ~376 tokens of tool definitions.
Scores higher than 10% of 15,350 MCP servers Glimind has audited.
Its tool list costs an agent ~376 tokens per session — lighter than 95% of servers.
74 → 74 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability85
Stability100

What to fix (5)

9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_payment, get_catalog, get_ea_download, get_signal_performance, get_signals and 4 more

6 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_payment, get_ea_download, purchase_access

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Handshake + tools/list takes ~1,707 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 8 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.imrane2019%2Falphabotpro/fixes

check_payment 1 change 
{
  "name": "check_payment",
  "description": "Verify a payment and receive a key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "payment_reference_id"
    ],
    "properties": {
      "tx_hash": {
        "type": "string"
      },
      "payment_reference_id": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_catalog 1 change 
{
  "name": "get_catalog",
  "description": "Public offerings + sample payloads.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_ea_download 1 change 
{
  "name": "get_ea_download",
  "description": "Single-use EA download link.",
  "inputSchema": {
    "type": "object",
    "required": [
      "slug"
    ],
    "properties": {
      "slug": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.imrane2019/alphabotpro"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.imrane2019/alphabotpro"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imrane2019%2Falphabotpro.svg)](https://glimind.com/server/mcp-registry%2Fio.github.imrane2019%2Falphabotpro?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.imrane2019%2Falphabotpro?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imrane2019%2Falphabotpro.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.imrane2019%2Falphabotpro.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.imrane2019%2Falphabotpro?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1da503e34a11b52f…, first seen 2026-10-17, included at leaf 953 of 27,551. Version history · verify what your client received.

Tools (9)

Compare: most reliable payments servers · most reliable knowledge servers · most reliable data servers · most reliable finance servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Imrane2019 Alphabotpro MCP server down right now?

As of 2026-10-19 16:10 UTC, the Imrane2019 Alphabotpro MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Imrane2019 Alphabotpro MCP server provide?

Imrane2019 Alphabotpro MCP server advertises 9 tools, including check_payment, get_catalog, get_ea_download, get_signal_performance, get_signals.

How do I install Imrane2019 Alphabotpro MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.alphabotpro.cloud/v1/mcp

Is the Imrane2019 Alphabotpro MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Imrane2019 Alphabotpro MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve