Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/ruleverdict

OCI · GHCR.IO/CLOUDCORPRECORDS/RULEVERDICT · 2 COMPONENTS

Deterministic rule-engine decisions with document-grounded explanations, rules and usage tools.

40 Trust /100

Last scanned (6 hours ago)

Scores higher than 41% of OCI servers

Category AI and Machine Learning

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 493 tokens (~54/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 39

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/ruleverdict@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 9 exposed · ~493 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
decide ~127

Make a decision in a domain from structured facts and/or free text; the verdict comes from the rule engine, with a document-grounded explanation.

NameTypeReqDescription
as_ofstring–Evaluate as of this date (optional).
domainstringyesDomain this call applies to.
fact_sourcesobject–Sources for the facts (optional).
factsobject–Facts payload for this call.
pattern_01boolean–First pattern to evaluate.
pattern_02boolean–Second pattern to evaluate.
textstring–Text content for this call.

No output schema declared.

No examples provided.

get_parameters ~39

The facts a domain's rules decide on, most decisive first — what to collect before decide.

NameTypeReqDescription
domainstringyesDomain this call applies to.

No output schema declared.

No examples provided.

get_rule_source ~31

Fetch a domain's rule set as editable YAML.

NameTypeReqDescription
domainstringyesDomain this call applies to.

No output schema declared.

No examples provided.

get_usage ~17

Check your plan and remaining monthly decision quota.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

import_policy_rules ~54

Turn a written policy document into draft rules, each citing the sentence it encodes. Nothing is saved.

NameTypeReqDescription
domainstringyesDomain this call applies to.
textstringyesText content for this call.

No output schema declared.

No examples provided.

ingest_text ~94

Add policy text to a domain's knowledge base, optionally dated or replacing an earlier version.

NameTypeReqDescription
domainstringyesDomain this call applies to.
effective_fromstring–Effective-from date (optional).
effective_untilstring–Effective-until date (optional).
supersedesstring–Identifier of the record this supersedes (optional).
textstringyesText content for this call.

No output schema declared.

No examples provided.

list_documents ~28

Browse a domain's ingested documents.

NameTypeReqDescription
domainstringyesDomain this call applies to.

No output schema declared.

No examples provided.

list_rules ~36

Inspect a domain's rules — conditions, verdicts, salience, overlaps.

NameTypeReqDescription
domainstringyesDomain this call applies to.

No output schema declared.

No examples provided.

put_rules ~67

Create or replace a domain's rule set from YAML (dry_run to validate).

NameTypeReqDescription
domainstringyesDomain this call applies to.
dry_runboolean–When true, preview the change without applying it (optional).
rulesstringyesRules payload for this call.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/ruleverdict MCP server?

io.github.CloudCorpRecords/ruleverdict runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/ruleverdict:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/cloudcorprecords/ruleverdict

# add to Claude Code
claude mcp add cloudcorprecords-ruleverdict -- docker run --rm -i ghcr.io/cloudcorprecords/ruleverdict:0.1.0
Common questions

What is the io.github.CloudCorpRecords/ruleverdict MCP server?

io.github.CloudCorpRecords/ruleverdict is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/ruleverdict. Deterministic rule-engine decisions with document-grounded explanations, rules and usage tools. This page covers its container image (ghcr.io/cloudcorprecords/ruleverdict).

Is the io.github.CloudCorpRecords/ruleverdict MCP server safe to use?

io.github.CloudCorpRecords/ruleverdict scores 40 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CloudCorpRecords/ruleverdict MCP server expose?

io.github.CloudCorpRecords/ruleverdict exposes 9 tools: decide, get_parameters, list_rules, get_rule_source, import_policy_rules, and 4 more. Their descriptions and schemas cost roughly 493 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/ruleverdict MCP server still maintained?

io.github.CloudCorpRecords/ruleverdict is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/ruleverdict MCP server under?

io.github.CloudCorpRecords/ruleverdict declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.