com.clauxel.zerolangcompiler/zerolangcompiler-mcp

MCPcommunity
v1.0.0com.clauxel.zerolangcompilerUnknownUpdated 1mo agoGitHub

A paid remote MCP for ZeroLang, built to return verdicts, receipts, usage logs, and audit-ready JSON

ZeroLang Agent Compiler MCP remote MCP for ZeroLang. Paid remote MCP for ZeroLang, structured receipts, usage logs, and audit-ready JSON evidence. This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website. Unauthenticated browser visits to return a clear JSON error instead of internal details. 1. Open the website and choose a plan. 2. Create or…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorcom.clauxel.zerolangcompiler
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubclauxel/zerolang-agent-compiler-mcp-mcp
Trust Status
B
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 · not run+0/30
→ Not yet scanned — package must be on npm
✓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—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 19d 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

ZeroLang Agent Compiler MCP remote MCP for ZeroLang. Paid remote MCP for ZeroLang, structured receipts, usage logs, and audit-ready JSON evidence. This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website. Unauthenticated browser visits to return a clear JSON error instead of internal details. 1. Open the website and choose a plan. 2. Create or request an API token. 3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.…

Keywords
mcp