MCP servers observed by Lowdown
io.github.bdentech/chieflab 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); 45 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 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.bdentech/chieflab
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bdentech/chieflab?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?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
45 tools on 2026-11-18:
chieflab_approve_actionchieflab_bootchieflab_brain_summarychieflab_check_measurement_duechieflab_connect_providerchieflab_connector_statuschieflab_continue_launch_loopchieflab_create_next_move_actionchieflab_create_work_requestchieflab_execute_approved_actionchieflab_force_measurement_duechieflab_get_capabilitychieflab_get_company_profilechieflab_get_publishing_targetschieflab_get_users_after_buildchieflab_helpchieflab_inboxchieflab_launch_productchieflab_list_specialistschieflab_mark_action_donechieflab_measure_hacker_newschieflab_measure_redditchieflab_persistence_healthchieflab_post_launch_reviewchieflab_prepare_next_movechieflab_publish_approved_postchieflab_query_proof_ledgerchieflab_record_manual_metricschieflab_record_manual_publishchieflab_redraftchieflab_regenerate_visual_assetchieflab_request_specialistchieflab_retry_blocked_actionchieflab_review_visual_assetchieflab_search_capabilitieschieflab_send_approved_emailchieflab_set_company_profilechieflab_set_provider_keychieflab_set_publishing_targetschieflab_signup_workspacechieflab_skip_next_movechieflab_statuschieflab_suggest_next_movechieflab_use_manual_fallbackchieflab_verify_install
MCP Registry declaration
- Registry name:
io.github.bdentech/chieflab - Declared version: 0.3.0
- Status: active
- Declared hosts:
api.chieflab.io
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.bdentech/chieflab", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.bdentech/chieflab?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.bdentech/chieflab -- npx -y @chieflab/mcp-server
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).