MCP servers observed by Lowdown
io.github.molt2meet-org/molt2meet MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 54 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.molt2meet-org/molt2meet
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.molt2meet-org/molt2meet?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
54 tools on 2026-11-18:
acknowledge_direct_settlement_taskadd_contact_methodadd_service_interestadd_task_reviewapprove_physical_task_completionapprove_rescheduleapprove_task_reviewcancel_physical_taskcancel_task_with_settlementcheck_task_fundingcheckout_wallet_depositcreate_api_keydispatch_physical_taskdispute_direct_settlement_taskfund_taskfund_walletget_agent_profileget_bank_transfer_detailsget_decision_requestsget_legal_documentsget_pending_actionsget_physical_task_detailsget_support_requestsget_task_eventsget_task_historyget_task_proofsget_waitlist_statusget_wallet_balanceget_wallet_transactionsjoin_country_waitlistlist_countrieslist_currencieslist_localeslist_physical_taskslist_reschedule_requestslist_service_capabilitieslist_service_categorieslist_service_interestslist_walletsopen_task_disputepublish_taskregister_agentreject_reschedulereject_task_reviewreply_to_support_requestrequest_reschedulerequest_task_quoteresolve_decision_requestrevoke_api_keysubmit_support_requesttest_task_webhookupdate_agent_profileupdate_task_locationupdate_task_webhook
MCP Registry declaration
- Registry name:
io.github.molt2meet-org/molt2meet - Declared version: 1.3.0
- Status: active
- Declared hosts:
molt.molt2meet.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.molt2meet-org/molt2meet", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.molt2meet-org/molt2meet?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).