MCP Audit vs Gia MCP Server

get_gate_status

Check resolution of a MANDATORY gate. Call this after classify_decision returns gateStatus: PENDING. Polls for up to 60 seconds — re-call if still PENDING. Do not proceed with the classified action until this returns APPROVED.

evaluate_threshold

Compute the Storey Threshold — escalation rate (gates required / total operations). Returns current rate, status, and recommendations. Healthy band 10-18% is a design heuristic, not empirically validated.

score_governance

Compute weighted governance score from caller-provided Integrity, Accuracy, and Compliance values (0-1). Returns weighted composite and pass/fail against configured thresholds. Scores are caller-assessed — this tool applies weights and thresholds, not independent evaluation.

assess_risk_tier

Assess the risk tier of an AI system using rule-based mapping to EU AI Act categories (Unacceptable, High, Limited, Minimal). Returns tier and MAI governance recommendations. Classification is heuristic, not a legal determination.

map_compliance

Map GIA governance components to regulatory compliance frameworks (NIST AI RMF, EU AI Act, ISO 42001, NIST 800-53, FedRAMP, LINDDUN, MITRE ATLAS, OMB M-25-22, HIPAA, VHA Trustworthy AI). Returns a DESIGN MAPPING (which GIA component is mapped to each control) across 10 frameworks and 72 controls — NOT third-party certification and NOT measured runtime enforcement. Rows whose control text implies enforcement that is config-gated off by default carry status PARTIAL. Runtime-evidenced coverage requires a ControlBinding (0 controls evidence-bound today).

verify_ledger

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.

verify_ledger_v2

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.

audit_pipeline

Query the audit ledger for governance entries. Search by operation name or retrieve recent entries. Returns hash-chained audit trail with MAI classification context.

monitor_agents

Monitor the status and health of all governed AI agents. Returns supervisor state, repair history, and failure counts.

evaluate_routing_threshold

Assess model routing health over a time window: safeguard fallback rate, prompt cache hit rate, batch utilization, and premium spend leakage. Returns banded status per metric (HEALTHY / WARNING / CRITICAL / INSUFFICIENT_DATA / UNVERIFIED) plus overall status. CRITICAL overall status opens a Mandatory gate and halts premium-tier routing until a human approves with rationale. Defaults to the last 24 hours.

system_status

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.