GIA — Governed Intelligence Architecture
NPM · GIA-MCP-SERVER · 2 COMPONENTS · SCANNED SEP 25
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 → 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
- 40 of 118 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 56 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety92
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "gia_run_patrol" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 58 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 GIA — Governed Intelligence Architecture MCP server?
GIA — Governed Intelligence Architecture runs locally as an npm package, launched with npx -y gia-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gia-mcp-server
claude mcp add knowledgepa3-gia-mcp-server -- npx -y gia-mcp-server
{
"mcpServers": {
"knowledgepa3-gia-mcp-server": {
"command": "npx",
"args": [
"-y",
"gia-mcp-server"
]
}
}
} {
"servers": {
"knowledgepa3-gia-mcp-server": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"gia-mcp-server"
]
}
}
} assistant mcp add knowledgepa3-gia-mcp-server -t stdio -c npx -a -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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 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.
- 22 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.
- 21 Sept 26 −3
- Stability: pass → 0.80 functional
- 20 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 −4
- Source repository: pass → fail ▼ security
- 17 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.
- 15 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.
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 25 Sept 2026 · Analysed npm/gia-mcp-server@0.4.4
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 118 packages
| Packages resolved | 118 |
|---|---|
| Stale | 40 |
| 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 →
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.
What is the GIA — Governed Intelligence Architecture MCP server?
GIA — Governed Intelligence Architecture is an MCP server listed in the public MCP registry as io.github.knowledgepa3/gia-mcp-server. Runtime AI governance: decision gates, human approval, hash-chained audit, compliance mapping. This page covers its npm package (gia-mcp-server).
Is the GIA — Governed Intelligence Architecture MCP server safe to use?
GIA — Governed Intelligence Architecture scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 GIA — Governed Intelligence Architecture MCP server expose?
GIA — Governed Intelligence Architecture exposes 57 tools: classify_decision, get_gate_status, evaluate_threshold, score_governance, assess_risk_tier, and 52 more. Their descriptions and schemas cost roughly 7,853 tokens of context every time the server is loaded.
Is the GIA — Governed Intelligence Architecture MCP server still maintained?
GIA — Governed Intelligence Architecture is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.