MCP servers observed by Lowdown
net.tasklite/mcp 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); 102 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-12 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:net.tasklite/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.tasklite/mcp?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?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-12: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 91 → 102
What tools does it list?
102 tools on 2026-11-18:
add_app_useradd_commentbuild_backendcheck_invite_codeconfigure_app_settingsconfigure_external_accessconfigure_telephony_mappingcreate_appcreate_app_api_keycreate_app_endpointcreate_app_invitecreate_automationcreate_boardcreate_columncreate_itemcreate_projectcreate_signature_requestdefine_app_roledelete_app_endpointdelete_app_roledelete_boarddelete_board_policydelete_columndelete_commentdelete_itemdelete_projectdeploy_frontenddisconnect_telephonyexplain_accessexport_projectfetchget_app_specget_board_policyget_board_schemaget_cellsget_deployment_filesget_email_usageget_frontend_promptget_item_historyget_permission_historyget_policy_identityget_signature_requestget_telephony_connectiongoogle_calendar_busygoogle_calendar_connectgoogle_calendar_create_eventgoogle_calendar_delete_eventgoogle_calendar_disconnectgoogle_calendar_ensure_calendargoogle_calendar_list_eventsgoogle_calendar_set_return_pathgoogle_calendar_statusgoogle_calendar_update_eventgrant_app_rolelink_app_userlist_app_endpointslist_app_inviteslist_app_role_grantslist_app_roleslist_app_user_linkslist_app_userslist_appslist_automationslist_boardslist_commentslist_deploymentslist_organizationslist_projectslist_signature_requestslist_telephony_providerslist_uploaded_filespreview_telephony_syncpublish_apppush_statusquery_itemsremove_app_userreorder_columnsrequest_file_uploadrevoke_app_inviterevoke_app_rolerevoke_upload_linkrollback_deploymentrun_telephony_syncsearchsend_test_pushset_app_user_roleset_board_policyset_cellset_cells_if_unchangedset_policy_identitysignature_linksimulate_requeststart_telephony_connectiontest_telephony_connectionunlink_app_userupdate_app_endpointupdate_automationupdate_boardupdate_columnupdate_commentupdate_itemvoid_signature_request
MCP Registry declaration
- Registry name:
net.tasklite/mcp - Declared version: 0.14.4
- Status: active
- Declared hosts:
mcp.tasklite.net
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:net.tasklite/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.tasklite/mcp?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:net.tasklite/mcp -- npx -y @tasklite/mcp
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).