io.github.bdentech/chieflab

Name: io.github.bdentech/chieflab
Rating: 60 (1 reviews)
Author: io.github.bdentech

MCPcommunity

v0.3.0io.github.bdentechUnknownUpdated 1mo agonpm GitHub

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.…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.bdentech

LicenseUnknown

Version0.3.0

Sourcemcp-registry

npm@chieflab/mcp-server

GitHubbdentech/chiefmo-agent

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ 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>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

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 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp