io.github.bdentech/chieflab

MCPcommunitylive
v0.3.0io.github.bdentechUnknownUpdated 4mo agonpmGitHub

Open execution contract for agents doing business work. 6 operators, one MIT-licensed spec.

Stdio MCP server for ChiefLab. Drop into Cursor / Claude Desktop / Claude Code / Codex / Windsurf / Cline / any stdio MCP host. Package status: this bridge is packaged in the repo but not published to npm yet. Use the hosted MCP endpoint directly today: . Current status: packaged in repo, not published to npm yet. Do not tell users to run until resolves. Use the hosted MCP URL directly today.…

Endpoint healthlive
checked 8 days ago · 180ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.bdentech
LicenseUnknown
Version0.3.0
Sourcemcp-registry
npm@chieflab/mcp-server
GitHubbdentech/chiefmo-agent
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 0 resolved · none vulnerable
Tool surface—
Security scan✓ Cleanv0.1.0 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 1 source file from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Stdio MCP server for ChiefLab. Drop into Cursor / Claude Desktop / Claude Code / Codex / Windsurf / Cline / any stdio MCP host. Package status: this bridge is packaged in the repo but not published to npm yet. Use the hosted MCP endpoint directly today: . Current status: packaged in repo, not published to npm yet. Do not tell users to run until resolves. Use the hosted MCP URL directly today. Then in your MCP host config: Restart the host. ChiefLab's launch tool set is now available — the…

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.