Other · Remote MCP server
ChiefLab
Open execution contract for agents doing business work. 6 operators, one MIT-licensed spec.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.bdentech/chieflab- Version
- 0.3.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-05-12
- Updated
- 2026-05-12
- Publisher
- bdentech (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/bdentech) · how
- Website
- chieflab.io
- Repository
- github.com/bdentech/chiefmo-agent (folder packages/mcp-server)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.chieflab.io/api/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- chieflab 0.3.0 · protocol 2025-03-26
- Tools discovered
45 - show names
chieflab_help,chieflab_get_users_after_build,chieflab_connect_provider,chieflab_retry_blocked_action,chieflab_use_manual_fallback,chieflab_set_company_profile,chieflab_get_company_profile,chieflab_list_specialists,chieflab_request_specialist,chieflab_force_measurement_due,chieflab_persistence_health,chieflab_query_proof_ledger,chieflab_set_publishing_targets,chieflab_get_publishing_targets,chieflab_suggest_next_move,chieflab_create_next_move_action,chieflab_regenerate_visual_asset,chieflab_record_manual_metrics,chieflab_measure_reddit,chieflab_measure_hacker_news,chieflab_review_visual_asset,chieflab_execute_approved_action,chieflab_check_measurement_due,chieflab_skip_next_move,chieflab_mark_action_done,chieflab_record_manual_publish,chieflab_connector_status,chieflab_signup_workspace,chieflab_launch_product,chieflab_redraft,chieflab_set_provider_key,chieflab_inbox,chieflab_status,chieflab_boot,chieflab_verify_install,chieflab_brain_summary,chieflab_search_capabilities,chieflab_get_capability,chieflab_create_work_request,chieflab_approve_action,chieflab_continue_launch_loop,chieflab_post_launch_review,chieflab_prepare_next_move,chieflab_publish_approved_post,chieflab_send_approved_email- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: node | @chieflab/mcp-server | 0.1.0 | stdio |
How to connect ChiefLab
ChiefLab is a remote MCP server: there is nothing to install. Its endpoint is https://api.chieflab.io/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
It can also run locally from a Node.js package published to the npm registry: @chieflab/mcp-server version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @chieflab/mcp-server@0.1.0; the entry names node as the runtime. It reads the environment variable CHIEFLAB_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"chieflab": {
"command": "npx",
"args": [
"-y",
"@chieflab/mcp-server@0.1.0"
],
"env": {
"CHIEFLAB_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ChessigmaChess opening guides and names, FEN and PGN checks, the daily chess puzzle and Elo estimates. | Remote · HTTPLive check: ✓ handshake |
| ChesswithclawPlay chess live against your own personal AI agent - OpenClaw, Hermes, and similar. | Remote · HTTPLive check: ✓ handshake |
| Chestnyznak MCPMCP server for Chestniy ZNAK (Честный ЗНАК) API - product marking verification. No auth needed for. | Local · stdio |
| Chicago Demolition Leads | Salvage SignalChicago demolition and reclaimed-brick leads, pricing, and a human-confirmed Daily Drop handoff. | Remote · HTTPLive check: ✓ handshake |
| China DisclosuresChina Disclosures MCP - non-SEC Chinese biotech deals and HK/STAR IPO. | Remote · HTTPLive check: ✓ handshake |
| China Market Access & StandardsFind CCC product categories by product name. | Remote · HTTPLive check: ✓ handshake |
| Chinese Almanac MCPChinese almanac (黄历) MCP: date selection, daily almanac, solar terms, zodiac horoscopes. | Local · stdio |
| Chinese History MCPTraceable Chinese-history MCP: 4 cited tools over 9 classical texts (pre-Qin to Wei-Jin). | Local · stdio |