Is io.github.molt2meet-org/molt2meet 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.

Endpointhttps://molt.molt2meet.com/mcp
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 cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 200 with JSON that is not a server card).
https://molt.molt2meet.com/mcp/server-card
MCP server card (SEP-1649 location)Published, does not validate: `$schema` is required (and 2 more). SEP-2127 shape; com.molt2meet/physical-execution 1.3.0.
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://molt.molt2meet.com 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 54 tools: acknowledge_direct_settlement_task, add_contact_method, add_service_interest, add_task_review, approve_physical_task_completion, approve_reschedule, approve_task_review, cancel_physical_task, cancel_task_with_settlement, check_task_funding, checkout_wallet_deposit, create_api_key, dispatch_physical_task, dispute_direct_settlement_task, fund_task, fund_wallet, get_agent_profile, get_bank_transfer_details, get_decision_requests, get_legal_documents, get_pending_actions, get_physical_task_details, get_support_requests, get_task_events, get_task_history, get_task_proofs, get_waitlist_status, get_wallet_balance, get_wallet_transactions, join_country_waitlist, list_countries, list_currencies, list_locales, list_physical_tasks, list_reschedule_requests, list_service_capabilities, list_service_categories, list_service_interests, list_wallets, open_task_dispute, publish_task, register_agent, reject_reschedule, reject_task_review, reply_to_support_request, request_reschedule, request_task_quote, resolve_decision_request, revoke_api_key, submit_support_request, test_task_webhook, update_agent_profile, update_task_location, update_task_webhook.

No change to its tools between 2026-09 and 2026-10.

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 nameio.github.molt2meet-org/molt2meet
Endpointhttps://molt.molt2meet.com/mcp
Publisher repositorynot 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

Free, no key, no signup. Terms · Privacy