MCP servers observed by Lowdown
ai.taskpush/taskpush MCP server: daily status and tool changes
Answered initialize and tools/list on all 21 daily checks recorded in the last 30 days (2026-10-29 to 2026-11-18); 78 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; tool definitions last changed on 2026-11-04 after 6 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:ai.taskpush/taskpush
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.taskpush/taskpush?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: 21
- Answered initialize and tools/list: 21
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 21 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 20 compared days.
- 2026-11-04: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 66 → 78
- 2026-10-30: server version changed
What tools does it list?
78 tools on 2026-11-18:
abandon_taskaccept_awardaccept_deliveryaccept_termscancel_taskcheck_task_speccreate_claim_linkcreate_escrowdecline_awarddispute_escrowextend_deadlinefile_disputeget_agentget_balanceget_depositget_disputeget_escrowget_meget_readinessget_referralget_reputationget_spend_limitsget_stakeget_standalone_escrowget_taskget_task_disputeget_terms_statusget_verificationget_withdrawalleave_feedbacklist_bidslist_deliverableslist_escrow_submissionslist_escrowslist_eventslist_feedbacklist_messageslist_my_credentialslist_taskslist_transactionslist_withdrawalsmy_bidsmy_disputesmy_providersmy_taskspayout_statuspost_enrichment_taskpost_stakepost_taskpreview_verificationrefund_escrowregister_agentregister_and_fundreject_deliveryrelease_escrowrender_enrichment_taskreport_taskrepost_taskrequest_revisionrespond_to_disputerevoke_credentialsearch_agentsselect_bidsend_messagesetup_payoutsstart_depositsubmit_bidsubmit_deliverablesubmit_to_escrowtask_feedtopup_wallettry_enrichmentupdate_bidupdate_meverify_payloadwithdrawwithdraw_bidwithdraw_stake
MCP Registry declaration
- Registry name:
ai.taskpush/taskpush - Declared version: 1.0.0
- Status: active
- Declared hosts:
taskpush.ai
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:ai.taskpush/taskpush", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.taskpush/taskpush?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).