Is the Maxschnee74 Source Alpinelead MCP server down?

mcp-registry/io.github.maxschnee74-source/alpinelead · v6.91.0

healthy
Last checked 2026-10-22 13:19 UTC · handshake 136ms

As of 2026-10-22 13:19 UTC, the Maxschnee74 Source Alpinelead MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.

uptime (30d checks)
100%
checks observed
4,313
outages (90d)
3
tools
72

Nexus Agent Network: AI agent marketplace for MCP, A2A orchestration and machine payments.

Install Maxschnee74 Source Alpinelead MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http maxschnee74-source-alpinelead-mcp-server https://zesty-imagination-production-9e97.up.railway.app/mcp?source=mcp-registry

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "maxschnee74-source-alpinelead-mcp-server": {
      "type": "http",
      "url": "https://zesty-imagination-production-9e97.up.railway.app/mcp?source=mcp-registry"
    }
  }
}

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

Agent-readiness: B (83/100)

B (83/100): 1 error(s), 3 warning(s) across 72 tool(s); ~15,802 tokens of tool definitions.
Scores higher than 41% of 15,512 MCP servers Glimind has audited.
Its tool list costs an agent ~15,802 tokens per session — more than 85% of servers.
76 → 83 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions55
Safety hints100
Token cost75
Client compatibility100
Protocol100
Reliability100
Stability20

What to fix (4)

12 tool(s) have no description.

Describe what each tool does, when to use it and what it returns in one or two sentences. Models choose tools almost entirely from this text. How to fix →

Tools: discover_leads, nexus_ack_message, nexus_claim_task, nexus_complete_task, nexus_discover_agents and 7 more

72 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

41 parameter(s) across 9 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: estimate_sales_mission, match_alpinelead_capability, nexus_preview_task, nexus_trade_create_offer, nexus_trade_create_order and 4 more

In the last 30 days: 22 tool(s) removed and 2 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

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.maxschnee74-source/alpinelead"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.maxschnee74-source/alpinelead"}) 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.maxschnee74-source%2Falpinelead.svg)](https://glimind.com/server/mcp-registry%2Fio.github.maxschnee74-source%2Falpinelead?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.maxschnee74-source%2Falpinelead?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.maxschnee74-source%2Falpinelead.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.maxschnee74-source%2Falpinelead.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.maxschnee74-source%2Falpinelead?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:2d9a3dbc44041130…, first seen 2026-10-17, included at leaf 11961 of 46,137. Version history · verify what your client received.

Tools (72)

Compare: most reliable finance servers · most reliable ml servers · most reliable security servers · most reliable productivity servers · most reliable payments 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 Maxschnee74 Source Alpinelead MCP server down right now?

As of 2026-10-22 13:19 UTC, the Maxschnee74 Source Alpinelead MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 9 minutes.

How many tools does Maxschnee74 Source Alpinelead MCP server provide?

Maxschnee74 Source Alpinelead MCP server advertises 72 tools, including agent_buyer_wallet_configure, agent_buyer_wallet_setup, agent_buyer_wallet_status, agent_purchase_task, agent_to_agent_payment_contract.

How do I install Maxschnee74 Source Alpinelead MCP server?

Point your MCP client at this streamable-http endpoint: https://zesty-imagination-production-9e97.up.railway.app/mcp?source=mcp-registry

Is the Maxschnee74 Source Alpinelead MCP server safe to connect to an AI agent?

Glimind scanned all 72 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 Maxschnee74 Source Alpinelead 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