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/rubricscore

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

Grade essays and resumes, and judge texts with typed yes/no, choice and score questions.

+3 this week 43 Trust /100

Last scanned (14 hours ago)

Scores higher than 42% of OCI servers

Category Education and Research

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 Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 759 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 54% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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.

What we tested

Checks we ran (12)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)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.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 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.

  • 10 Nov 26 38

    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 21 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/rubricscore@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 · 7 exposed · ~759 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
check_resume ~96

Score a resume, optionally against a job posting: a 0-100 match score, the posting's keywords found and missing (matched literally, as an ATS search would), ATS format checks, the level fit, and the probability a recruiter would move it to interview.

NameTypeReqDescription
job_descriptionstring–The job posting to match against. Omit for a general resume check.
resumestringyesThe resume as plain text.

No output schema declared.

No examples provided.

compare_versions ~108

Which of two versions is stronger for a stated purpose. Asked twice with the order swapped and averaged, because the model favors the second option on close calls; if the two orders disagree the result is a tie.

NameTypeReqDescription
contextstring–The surrounding text, such as the whole essay or the job posting.
questionstringyese.g. 'Which opening line would an admissions reader find more compelling?'
version_astringyes–
version_bstringyes–

No output schema declared.

No examples provided.

grade_essay ~179

Grade one essay against a built-in rubric. kind "essay": six criteria and a letter grade, for class essays at middle school, high school or college level. kind "common-app": a Common App personal statement (pass the prompt number, 1-7). kind "sat": an SAT School Day essay, Reading/Analysis/Writing each 1-4 (pass the source passage to check quotations).

NameTypeReqDescription
assignmentstring–kind "essay": the assignment prompt.
essaystringyesThe essay text.
kindstring––
levelstring–kind "essay" only. Default high school.
passagestring–kind "sat": the source passage.
promptinteger–kind "common-app": which of the seven prompts. Default 7, topic of your choice.

No output schema declared.

No examples provided.

grade_with_rubric ~121

Grade one or more submissions (up to 30, in parallel) against a rubric you supply: each criterion scored on a 3- to 6-point scale, summed per submission. Each submission is graded in its own call, so its score never depends on the others.

NameTypeReqDescription
assignmentstring––
criteriaarrayyesRubric rows, e.g. { "name": "Evidence", "description": "Supports the claim with specific evidence" }.
pointsinteger––
submissionsarrayyes–

No output schema declared.

No examples provided.

judge_choice ~83

Pick the option that best fits a text, with a probability for every option and a confidence. Options map an id to a description of when it applies.

NameTypeReqDescription
optionsobjectyese.g. { "billing": "Payments, refunds, invoices", "technical": "Bugs and errors" }
questionstringyes–
textstringyes–

No output schema declared.

No examples provided.

judge_score ~78

Place a text on an ordered scale you define (lowest level first) and get the nearest level, the exact position and a probability for each level.

NameTypeReqDescription
levelsarrayyesLowest first, e.g. ["Off-topic", "Partly relevant", "Fully relevant"].
questionstringyes–
textstringyes–

No output schema declared.

No examples provided.

judge_yes_no ~94

Ask any yes/no question about a text and get the probability that the answer is yes. Use for checks and gates, e.g. 'Does this reply answer the customer's question?'.

NameTypeReqDescription
no_meansstring––
questionstringyes–
textstringyesThe text to judge.
yes_meansstring–What a yes looks like, if it helps to spell out.

No output schema declared.

No examples provided.

Install

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

io.github.CloudCorpRecords/rubricscore runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/rubricscore:0.1.0 mcp. 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/rubricscore

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

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

io.github.CloudCorpRecords/rubricscore is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/rubricscore. Grade essays and resumes, and judge texts with typed yes/no, choice and score questions. This page covers its container image (ghcr.io/cloudcorprecords/rubricscore).

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

io.github.CloudCorpRecords/rubricscore scores 43 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/rubricscore MCP server expose?

io.github.CloudCorpRecords/rubricscore exposes 7 tools: check_resume, grade_essay, grade_with_rubric, judge_yes_no, judge_choice, and 2 more. Their descriptions and schemas cost roughly 759 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/rubricscore is still listed as active in the MCP registry. We last reached this channel on 21 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/rubricscore MCP server under?

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

What did VerifyMCP test on the io.github.CloudCorpRecords/rubricscore MCP server?

VerifyMCP ran 12 checks on io.github.CloudCorpRecords/rubricscore, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/rubricscore: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.