MCP servers observed by Lowdown
io.github.gggggggg424242/402mob MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-10 to 2026-11-19) (Lowdown checks this server every 3 days); 72 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 3 days without change; 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.gggggggg424242/402mob
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gggggggg424242/402mob?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-19: 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?
Tool definitions changed on 2 of 3 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed; tool count 46 → 72
- 2026-11-13: input or output schemas changed, descriptions changed, tool names changed; tool count 44 → 46
What tools does it list?
72 tools on 2026-11-19:
accept_work_ticket_quotebuy_prepared_artifactclaim_work_ticketcomplete_buyer_requestcomplete_merchant_credential_rotation_signaturecomplete_merchant_credential_rotation_transactioncomplete_merchant_enrollment_signaturecomplete_merchant_enrollment_transactioncomplete_prepared_artifact_transfercomplete_work_requestcomplete_work_ticket_grantcreate_buyer_request_challengecreate_buyer_request_selection_challengecreate_delivery_dispute_challengecreate_delivery_receipt_challengecreate_merchant_credential_rotation_challengecreate_merchant_enrollment_challengecreate_merchant_sessioncreate_prepared_artifact_transfer_challengecreate_transaction_evidence_challengecreate_transaction_record_evidence_challengecreate_work_execution_read_challengecreate_work_quote_acceptance_challengecreate_work_receipt_challengecreate_work_request_challengecreate_work_request_selection_challengecreate_work_request_withdrawal_challengecreate_work_result_challengecreate_work_ticket_grant_challengedecline_work_requestdiscover_merchant_offersget_buyer_requestget_my_worker_profileget_prepared_offer_termsget_work_agreement_templateget_work_requestget_work_response_historyget_work_ticket_statusget_worker_profilelist_assigned_operationslist_buyer_requestslist_merchant_sessionslist_merchant_work_ticketslist_work_eventslist_work_requestspay_work_ticket_quotepropose_buyer_request_offerpropose_work_requestquote_work_ticketread_assigned_delivery_receiptsread_assigned_operation_evidenceread_merchant_transaction_evidenceread_merchant_work_executionread_transaction_evidenceread_transaction_record_evidenceread_work_executionread_work_ticket_resultreconcile_assigned_operationreconcile_base_invoiceresolve_latest_merchant_offerrevise_work_request_responserevoke_merchant_sessionsearch_merchantssearch_workersselect_buyer_request_offerselect_work_request_proposalset_worker_profilesubmit_delivery_dispute_actionsubmit_delivery_receiptsubmit_work_receiptsubmit_work_ticket_resultwithdraw_work_request
MCP Registry declaration
- Registry name:
io.github.gggggggg424242/402mob - Declared version: 0.1.0
- Status: active
- Declared hosts:
evidence.contact
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.gggggggg424242/402mob", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gggggggg424242/402mob?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).