io.github.cruxible-ai/cruxible-core

MCPcommunity
v0.1.2io.github.cruxible-aiUnknownUpdated 5mo agoGitHub

Deterministic decision engine with receipts. Define rules in YAML, query a graph, get proof.

Deterministic decision engine with DAG-based receipts. Build entity graphs, query with MCP, get auditable proof. Define entity graphs, queries, and constraints in YAML. Run them locally from CLI or MCP, and get receipts proving exactly why each result was returned. 1. Define a domain in YAML: 2. Load data and run a deterministic query: "Suggest an alternative to simvastatin" 3. Get a receipt —…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.cruxible-ai
LicenseUnknown
Version0.1.2
Sourcemcp-registry
GitHubcruxible-ai/cruxible-core
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—
DependenciesNot audited
Tool surface—
Security scan✓ Cleanv0.1.5 · 2mo 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

Deterministic decision engine with DAG-based receipts. Build entity graphs, query with MCP, get auditable proof. Define entity graphs, queries, and constraints in YAML. Run them locally from CLI or MCP, and get receipts proving exactly why each result was returned. 1. Define a domain in YAML: 2. Load data and run a deterministic query: "Suggest an alternative to simvastatin" 3. Get a receipt — structured proof of every answer: Raw receipt DAG rendered for readability: Or use if you prefer uv.…

Keywords
mcp