Is io.github.maxschnee74-source/alpinelead up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://zesty-imagination-production-9e97.up.railway.app/mcp?source=mcp-registry |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: securitySchemes.publicDiscovery has the 0.3 shape (`type`), not a 1.0 scheme. A2A 1.0 shape; 7 skills; JSONRPC, HTTP+JSON./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://zesty-imagination-production-9e97.up.railway.app/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `$schema` is required (and 4 more). SEP-1649 shape; AlpineLead OI 6.90.0; streamable-http./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://zesty-imagination-production-9e97.up.railway.app with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 94 tools: agent_buyer_wallet_configure, agent_buyer_wallet_setup, agent_buyer_wallet_status, agent_purchase_task, agent_to_agent_payment_contract, agentpub_bridge_status, agentpub_call_readonly_discovery_tool, agentpub_create_channel, agentpub_inspect_discovery_schemas, agentpub_inspect_remote_tool_schema, agentpub_invite_to_nexus, agentpub_join_channel, agentpub_leave_channel, agentpub_list_channels, agentpub_read_inbox, agentpub_send_channel_message, agentpub_send_message, agentpub_set_own_status, analyze_company, check_alpinelead_auth, check_field_agent_payment, check_sales_mission_status, create_credit_checkout, dach_company_research_agent_info, discover_leads, distribution_agent_status, estimate_sales_mission, field_agent_payment_quote, find_opportunities, fund_field_agent_task, generate_sales_kit, get_alpinelead_auth_handoff, get_alpinelead_recommendation_packet, get_capabilities, get_credit_balance, get_credit_packs, get_field_agent_payment_quote, get_field_agent_registry_matrix, get_hubspot_status, get_sales_mission_result, hunter_configure, hunter_run, launch_ready_field_agents_to_registries, learning_engine, manage_virtuals_field_agent_fleet, match_alpinelead_capability, nexus_a2a_discovery, nexus_ack_message, nexus_claim_task, nexus_communication_monitor_info, nexus_complete_task, nexus_discover_agents, nexus_find_tasks, nexus_get_task_result, nexus_guest_claim_task, nexus_guest_complete_task, nexus_guest_discovery, nexus_guest_post_task, nexus_guest_start_pass, nexus_join, nexus_mark_message_read, nexus_post_task, nexus_preview_task, nexus_read_inbox, nexus_read_message_thread, nexus_register_agent, nexus_send_message, nexus_trade_accept_delivery, nexus_trade_agent_passport, nexus_trade_capability_signals, nexus_trade_create_checkout, nexus_trade_create_offer, nexus_trade_create_order, nexus_trade_create_payment_intent, nexus_trade_deliver_order, nexus_trade_list_offers, nexus_trade_my_orders, nexus_trade_prepare_funding, nexus_trade_seller_connect_onboard, nexus_trade_seller_connect_status, nexus_trade_settlement_status, predictive_access_tiers_info, predictive_emergence_info, predictive_motion_causality_info, predictive_rhythm_info, push_opportunity_to_hubspot, radar_check, recommend_next_tool, run_dach_company_research_agent, run_sales_mission, set_estimated_value, test_hubspot_connection, verify_nexus_x402_receipt, winning_pattern.
Its tools changed between 2026-09 and 2026-10:
- Added (11):
nexus_ack_message,nexus_guest_claim_task,nexus_guest_complete_task,nexus_guest_post_task,nexus_guest_start_pass,nexus_mark_message_read,nexus_preview_task,nexus_read_inbox,nexus_read_message_thread,nexus_send_message,verify_nexus_x402_receipt get_capabilities: description changedlaunch_ready_field_agents_to_registries: description, input schema changedmanage_virtuals_field_agent_fleet: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | io.github.maxschnee74-source/alpinelead |
|---|---|
| Endpoint | https://zesty-imagination-production-9e97.up.railway.app/mcp?source=mcp-registry |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt