Rubrkit MCP Server

https://www.rubrkit.com/api/v1/mcp Remote v0.1.0

Published by rubrkit.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP-native AI evaluation: rubric audits, eval suites, and proof reports for AI/LLM output.

Trust grade
A
90/100
Last scanned get badge →
Trust
A · 90/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 90/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 10 = 90. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: rubrkit_read_proof_report → rubrkit_list_artifact_files → rubrkit_read_eval. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow rubrkit_read_proof_report → rubrkit_list_artifact_files → rubrkit_read_eval

high Tool "rubrkit_read_eval" exposes command/code executionMTC-CAP-001

Tool "rubrkit_read_eval" appears to run shell commands or evaluate code (keyword "eval" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool rubrkit_read_eval

low Mutating tool "rubrkit_read_eval" declares no destructiveHintMTC-CAP-005

Tool "rubrkit_read_eval" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool rubrkit_read_eval

Tools 41

Each tool and what it can reach — enumerated from the running server.

  • rubrkit_list_artifact_filesreads sensitive data
  • rubrkit_read_evalruns code / shell
  • rubrkit_read_proof_reportingests untrusted input
  • rubrkit_add_golden_caseno sensitive capability
  • rubrkit_apply_audit_rewriteno sensitive capability
  • rubrkit_convert_to_rubr_flowno sensitive capability
  • rubrkit_create_artifact_bundleno sensitive capability
  • rubrkit_create_drift_monitorno sensitive capability
  • rubrkit_delete_artifact_bundleno sensitive capability
  • rubrkit_export_proof_reportno sensitive capability
Show 31 more tools ↓
  • rubrkit_hard_delete_artifact_bundleno sensitive capability
  • rubrkit_list_artifact_bundle_versionsno sensitive capability
  • rubrkit_list_artifact_bundlesno sensitive capability
  • rubrkit_list_auditsno sensitive capability
  • rubrkit_list_drift_monitorsno sensitive capability
  • rubrkit_list_evalsno sensitive capability
  • rubrkit_list_file_versionsno sensitive capability
  • rubrkit_list_golden_casesno sensitive capability
  • rubrkit_list_job_eventsno sensitive capability
  • rubrkit_list_rubr_flow_conversionsno sensitive capability
  • rubrkit_poll_jobno sensitive capability
  • rubrkit_read_api_docno sensitive capability
  • rubrkit_read_artifact_bundleno sensitive capability
  • rubrkit_read_artifact_fileno sensitive capability
  • rubrkit_read_auditno sensitive capability
  • rubrkit_read_drift_observationsno sensitive capability
  • rubrkit_read_input_driftno sensitive capability
  • rubrkit_read_openapi_contractno sensitive capability
  • rubrkit_read_rubr_flow_conversionno sensitive capability
  • rubrkit_read_validity_driftno sensitive capability
  • rubrkit_record_outcomeno sensitive capability
  • rubrkit_restore_artifact_bundle_versionno sensitive capability
  • rubrkit_restore_file_versionno sensitive capability
  • rubrkit_retire_golden_caseno sensitive capability
  • rubrkit_run_drift_checkno sensitive capability
  • rubrkit_run_evalsno sensitive capability
  • rubrkit_search_api_docsno sensitive capability
  • rubrkit_set_drift_monitor_statusno sensitive capability
  • rubrkit_start_auditno sensitive capability
  • rubrkit_update_artifact_fileno sensitive capability
  • rubrkit_upload_artifact_filesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.0 latest A 90/100 3 1.10.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 90/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/rubrkit-com-api-v1/badge.svg)](https://mcptrustchecker.com/registry/rubrkit-com-api-v1)
HTML
<a href="https://mcptrustchecker.com/registry/rubrkit-com-api-v1"><img src="https://mcptrustchecker.com/registry/rubrkit-com-api-v1/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/rubrkit-com-api-v1/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://www.rubrkit.com/api/v1/mcp --online

Use the free API → How scoring works

More in AI & Agents