GIA — Governed Intelligence Architecture
NPM · GIA-MCP-SERVER · 2 COMPONENTS · SCANNED AUG 4
Runtime AI governance: decision gates, human approval, hash-chained audit, compliance mapping.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (117 of 121), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (117 of 121), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (poor).Fail
- Context-footprint check failed: tool/resource definitions use about 8023 tokens (~123/item across 65 items; 57 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · gia-mcp-server
claude mcp add knowledgepa3-gia-mcp-server -- npx -y gia-mcp-server
codex mcp add knowledgepa3-gia-mcp-server -- npx -y gia-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"knowledgepa3-gia-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"gia-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add knowledgepa3-gia-mcp-server --command npx --arg -y --arg gia-mcp-server
mcp_servers:
knowledgepa3-gia-mcp-server:
command: "npx"
args: ["-y", "gia-mcp-server"] {
"mcpServers": {
"knowledgepa3-gia-mcp-server": {
"command": "npx",
"args": [
"-y",
"gia-mcp-server"
]
}
}
} 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.
- 2 Aug 26 +35
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → poor ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: SEE LICENSE IN LICENSE functional
- 1 Aug 26 −5
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- 31 Jul 26 +24
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −19
- Malware scan: pass → unverified ▼ security
- Security disclosure: fail → unverified ▼ functional
- Dependency health: partial → unverified ▼ functional
- Package version: 0.3.0 → 0.4.4 functional
- 29 Jul 26 +1
- Dependency health: unverified → partial ▲ functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- 27 Jul 26 24
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 117 packages
117 packages in the resolved dependency tree · 117 deprecated · 38 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
srt_diagnose ~87
Run the SRT Diagnostician on an incident. Matches finding to known playbooks, identifies root cause, and proposes a staged repair plan. Classification: ADVISORY — read-only analysis, no mutations.
| Name | Type | Req | Description |
|---|---|---|---|
| additional_observations | array | — | Additional diagnostic observations (e.g. from manual log reading) |
| incident_id | string | yes | Incident ID from watchdog finding |
No output schema declared.
No examples provided.
srt_generate_postmortem ~112
Generate a structured postmortem report for a completed SRT incident. Includes timeline, root cause, what worked/failed, prevention actions, real timing metrics (TTD/TTDiag/TTR), an ESTIMATED ROI (humanTimeSaved/costAvoided from a severity-bucket heuristic — not measured savings, flagged via roiEstimated/roiBasis), and optional playbook delta. Classification: ADVISORY.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | Incident ID to generate postmortem for |
No output schema declared.
No examples provided.
srt_run_watchdog ~86
Run real health check probes from the MCP container (API health, frontend, disk, memory, TLS cert, DB, DNS). Returns actual measured values — never uses AI-provided data. Classification: INFORMATIONAL — read-only, no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| check_results | array | — | IGNORED — real probes are always used. This parameter exists for backward compatibility only. |
No output schema declared.
No examples provided.
system_status ~296
Returns a comprehensive read-only snapshot of the GIA governance engine's current state. No parameters required. RETURNS (JSON object): - version: server version string (e.g. "0.3.5") - engine.health: "healthy" | "degraded" | "failed" - engine.uptimeMs: milliseconds since server start - governance.totalDecisions: lifetime decision count - governance.mandatoryCount: decisions classified MANDATORY - governance.pendingGates: gates awaiting human approval - storey_threshold.escalationRatePct: MANDATORY rate as percentage (healthy band: 10–18%) - storey_threshold.status: "HEALTHY" | "DEGRADED" | "CRITICAL" - ledger.totalEntries: forensic audit trail entry count - ledger.chainIntegrity: true if hash chain is unbroken - intelligence.phoenixSnapshots: context recovery snapshots - intelligence.memoryPacks: sealed memory packs count - runtimeAccountability.activeSessions: live MCP sessions - thresholdDetail.interpretation: plain-English health summary USE WHEN: - Verifying the governance engine is healthy before dispatching agents - Checking if mandatory gate backlog is blocking workflow progression - Auditing Storey Threshold compliance (MANDATORY gate rate ceiling) - Confirming ledger chain integrity before exporting audit evidence READ-ONLY: No side effects. Safe to call at any frequency.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
transfer_memory_pack ~123
Transfer a memory pack between agents via a governed knowledge corridor. Creates a derived pack with transfer provenance. ALWAYS requires MANDATORY gate — no silent transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| approved_by | string | yes | Human who approved the transfer (MANDATORY) |
| scope_filter | array | — | Optional: only transfer specific scope items |
| source_agent_id | string | yes | Agent transferring the pack |
| source_pack_id | string | yes | Source pack to transfer |
| target_agent_id | string | yes | Agent receiving the pack |
| target_role | string | yes | Role of the target agent |
No output schema declared.
No examples provided.
verify_ledger ~68
Check the internal self-consistency of the hash-chained forensic audit ledger. Walks the in-memory chain reconstruction (not persisted DB rows) and reports whether it is internally consistent and linkage-intact. Not third-party content-verification. Classification: INFORMATIONAL — read-only, no side effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_ledger_v2 ~101
Verify the PERSISTED forensic ledger rows in PostgreSQL (not an in-memory reconstruction). Epoch-aware: epoch-2 rows are content-verified against persisted columns with Ledger Canonical v2; legacy epoch-1 rows are linkage-verified only and labeled honestly. Findings append a MANDATORY LEDGER_INTEGRITY_VIOLATION entry (never repaired, never UPDATEd). Classification: INFORMATIONAL read; MANDATORY escalation on findings.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.