MCP servers observed by Lowdown
app.2ools/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 81 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 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:app.2ools/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.2ools/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
81 tools on 2026-11-16:
act_on_project_os_taskactivate_projectadd_project_feedbackadd_project_pinadvance_project_agent_modeanswer_project_engineering_decisionapprove_artifact_versionapprove_versionattach_project_engine_workspacebuild_from_conversationcancel_agent_runcancel_buildcheckpoint_work_sessionclaim_work_assignmentcompare_versionsconfigure_project_agent_modecontinue_projectcreate_public_previewcreate_version_share_linkcreate_work_assignmentdecide_work_assignmentdispatch_project_workget_account_profileget_agentget_artifactget_buildget_engine_dispatchget_projectget_project_accessget_project_activityget_project_agent_modeget_project_contextget_project_disciplineget_project_engine_workspaceget_project_intelligenceget_project_missionget_project_work_dispatchget_task_quality_gateget_version_share_linkget_work_handoffheartbeat_work_sessioninvite_project_memberlist_approval_requestslist_artifact_approval_requestslist_artifactslist_build_systemslist_connected_engineslist_project_agentslist_project_engineering_decisionslist_project_feedbacklist_project_pinslist_projectslist_work_assignmentsmanage_project_disciplinemanage_work_watchdogprepare_artifact_downloadprepare_artifact_uploadprepare_version_exportprepare_work_handoffrefine_projectrefresh_project_cockpitregister_existing_projectreject_artifact_versionreject_versionremove_project_memberremove_project_pinrender_project_previewresolve_project_feedbackreview_project_missionrevoke_project_inviterevoke_version_share_linkrun_project_agentrun_task_quality_gatestart_project_on_enginesubmit_work_sessionupdate_account_profileupdate_living_planupdate_project_intelligenceupdate_project_member_roleupdate_project_missionwait_for_project_activity
MCP Registry declaration
- Registry name:
app.2ools/mcp - Declared version: 0.3.1
- Status: active
- Declared hosts:
2ools.app
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:app.2ools/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.2ools/mcp?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).