io.github.TheBarmaEffect/glassbox-framework
NPM · @GLASSBOX-FRAMEWORK/MCP · SCANNED SEP 24
Runtime constitutional verification for AI answers — claim reasoning, ECS, red team, audits.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 46 of 140 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 121 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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
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
claude mcp add thebarmaeffect-glassbox-framework -- npx -y @glassbox-framework/mcp
{
"mcpServers": {
"thebarmaeffect-glassbox-framework": {
"command": "npx",
"args": [
"-y",
"@glassbox-framework/mcp"
]
}
}
} {
"servers": {
"thebarmaeffect-glassbox-framework": {
"command": "npx",
"args": [
"-y",
"@glassbox-framework/mcp"
]
}
}
} codex mcp add thebarmaeffect-glassbox-framework -- npx -y @glassbox-framework/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"thebarmaeffect-glassbox-framework": {
"type": "local",
"command": [
"npx",
"-y",
"@glassbox-framework/mcp"
],
"enabled": true
}
}
} openclaw mcp add thebarmaeffect-glassbox-framework --command npx --arg -y --arg @glassbox-framework/mcp
mcp_servers:
thebarmaeffect-glassbox-framework:
command: "npx"
args: ["-y", "@glassbox-framework/mcp"] {
"McpServers": {
"thebarmaeffect-glassbox-framework": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@glassbox-framework/mcp"
]
}
}
} assistant mcp add thebarmaeffect-glassbox-framework -t stdio -c npx -a -y @glassbox-framework/mcp
{
"mcpServers": {
"thebarmaeffect-glassbox-framework": {
"command": "npx",
"args": [
"-y",
"@glassbox-framework/mcp"
]
}
}
} 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.
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 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.
- 21 Sept 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.
- 19 Sept 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.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 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.
- 14 Sept 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.
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 24 Sept 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 →
Dependencies 140 packages
| Packages resolved | 140 |
|---|---|
| Deprecated | 1 |
| Stale | 45 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
glassbox_export_audit_report 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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| intents | array | – | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
glassbox_extract_claims 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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
glassbox_generate_trust_card 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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| claims | array | yes | – |
| constitution | – | – | – |
| ecs | – | – | – |
| intents | array | – | – |
| question | string | yes | – |
| red_team | – | – | – |
No output schema declared.
No examples provided.
glassbox_red_team Glassbox · Court (7-Angle 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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| claims | array | – | – |
| constitution | – | – | – |
| intents | array | – | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
glassbox_score_ecs 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.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | – |
| constitution | – | – | – |
| mode | string | – | – |
| red_team | – | – | – |
| weights | – | – | – |
No output schema declared.
No examples provided.
glassbox_verify_answer 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.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| intents | array | – | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 24 September 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.