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.TheBarmaEffect/glassbox-framework

NPM · @GLASSBOX-FRAMEWORK/MCP

Runtime constitutional verification for AI answers — claim reasoning, ECS, red team, audits.

+1 this week 75 Trust /100

Last scanned (21 hours ago)

Scores higher than 51% of npm 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 45 of 158 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 646 tokens (~107/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 16 Nov 26 0
    • Stability: 0.97 → pass security
  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 26 +1

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

  • 5 Nov 26 +1

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

  • 3 Nov 26 −6
    • Stability: pass → 0.57 functional
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 npm/@glassbox-framework/mcp@1.0.3

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 158 packages
Packages resolved 158
Deprecated 1
Stale 44
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~646 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
glassbox_export_audit_report ~85

Run the full Glass Box pipeline and return a full AuditRecord, including the per-call API trace and a deterministic SHA-256-based log_id. Two runs with identical inputs AND identical engine outputs produce the same log_id, enabling replay detection and cache lookups.

NameTypeReqDescription
answerstringyes–
intentsarray––
questionstringyes–

No output schema declared.

No examples provided.

glassbox_extract_claims ~101

Decompose an answer into atomic claims. Every claim carries a non-empty reasoning chain explaining why it is asserted, what evidence supports it, and how it could be falsified. Fallback claims (produced when the LLM call fails) are explicitly marked with a [fallback] prefix. The reasoning field is non-negotiable — it is the core product of the framework.

NameTypeReqDescription
answerstringyes–
questionstringyes–

No output schema declared.

No examples provided.

glassbox_generate_trust_card ~133

Assemble a Trust Card from prebuilt parts (claims, red_team, ecs, optional constitution). No new LLM calls are made by this tool — it derives the verdict from the supplied parts and produces a deterministic audit reference. Use this when you have already called glassbox_extract_claims / glassbox_red_team / glassbox_score_ecs separately and want to compose the final artifact.

NameTypeReqDescription
answerstringyes–
claimsarrayyes–
constitution–––
ecs–––
intentsarray––
questionstringyes–
red_team–––

No output schema declared.

No examples provided.

glassbox_red_team ~129

Glassbox Court runs all seven adversarial probes against an answer: fabrication, source manipulation, bias injection, context attack, overconfidence, underspecification, and constitutional violation. Returns one finding per probe, with verbatim evidence, even when the probe passes. If `intents` are supplied and `constitution` is not, the intents are compiled and evaluated inline so the constitutional_violation probe runs against the right rule set.

NameTypeReqDescription
answerstringyes–
claimsarray––
constitution–––
intentsarray––
questionstringyes–

No output schema declared.

No examples provided.

glassbox_score_ecs ~106

Compute the Epistemic Confidence Score over prebuilt claims, an optional red-team report, and an optional constitution. Returns all five dimension scores, the weights used, the exact formula evaluated, and the total — never just the total. Defaults to weighted arithmetic mean; pass mode="geometric" for the stricter variant.

NameTypeReqDescription
claimsarrayyes–
constitution–––
modestring––
red_team–––
weights–––

No output schema declared.

No examples provided.

glassbox_verify_answer ~92

Run a question/answer pair through the entire Glass Box Framework: claim extraction → constitution compile + evaluate → Glassbox Court (red-team) → ECS → verdict. Returns a Trust Card with verdict, ECS breakdown, per-claim reasoning, all 7 red-team probes, and the deterministic audit reference.

NameTypeReqDescription
answerstringyes–
intentsarray––
questionstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.TheBarmaEffect/glassbox-framework MCP server?

io.github.TheBarmaEffect/glassbox-framework runs locally as an npm package, launched with npx -y @glassbox-framework/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @glassbox-framework/mcp

# add to Claude Code
claude mcp add thebarmaeffect-glassbox-framework -- npx -y @glassbox-framework/mcp
Common questions

What is the io.github.TheBarmaEffect/glassbox-framework MCP server?

io.github.TheBarmaEffect/glassbox-framework is an MCP server listed in the public MCP registry as io.github.TheBarmaEffect/glassbox-framework. Runtime constitutional verification for AI answers, claim reasoning, ECS, red team, audits. This page covers its npm package (@glassbox-framework/mcp).

Is the io.github.TheBarmaEffect/glassbox-framework MCP server safe to use?

io.github.TheBarmaEffect/glassbox-framework scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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.TheBarmaEffect/glassbox-framework MCP server expose?

io.github.TheBarmaEffect/glassbox-framework exposes 6 tools: glassbox_verify_answer, glassbox_extract_claims, glassbox_score_ecs, glassbox_red_team, glassbox_generate_trust_card, glassbox_export_audit_report. Their descriptions and schemas cost roughly 646 tokens of context every time the server is loaded.

Is the io.github.TheBarmaEffect/glassbox-framework MCP server still maintained?

io.github.TheBarmaEffect/glassbox-framework 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.TheBarmaEffect/glassbox-framework MCP server under?

io.github.TheBarmaEffect/glassbox-framework declares the Apache-2.0 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.TheBarmaEffect/glassbox-framework MCP server?

VerifyMCP ran 16 checks on io.github.TheBarmaEffect/glassbox-framework, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.