MCP servers observed by Lowdown
io.github.ppcvote/mindthread MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 43 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; 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:io.github.ppcvote/mindthread
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ppcvote/mindthread?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: 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?
43 tools on 2026-11-17:
add_libraryanalytics_insightsapply_account_settingsapprove_library_itemapprove_pending_replybuild_materialbulk_archive_librarybulk_delete_librarybulk_queue_librarycancel_schedulecloud_patrol_logcloud_patrol_statsconnect_account_linkdelete_library_itemdisable_this_keygenerate_postsget_account_settingsget_account_settings_batchget_approvalget_brand_docget_cloud_patrolget_materialget_meget_my_usageget_playbookget_top_postslist_account_settingslist_accountslist_eventslist_formulaslist_guardrail_changeslist_librarylist_pending_replieslist_schedulespreview_account_settingspublishreject_pending_replyrevert_account_settings_batchsave_brand_docschedule_textset_cloud_patrolupdate_account_settingsupdate_library_item
MCP Registry declaration
- Registry name:
io.github.ppcvote/mindthread - Declared version: 0.2.0
- Status: active
- Declared hosts:
mindthread.tw
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.ppcvote/mindthread", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.ppcvote/mindthread?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:io.github.ppcvote/mindthread -- npx -y mindthread-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).