Gia MCP Server

gia-mcp-server npm v0.4.4

Published by knowledgepa3 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Runtime governance layer for generative AI agents. Works with any MCP-compatible client — Claude, GPT, Gemini, Cursor, or custom frameworks. MAI classification, forensic audit trails, human-in-the-loop gates, EU AI Act compliance, NIST/SOC 2/CMMC mapping.

Trust grade
B
89/100
Last scanned get badge →
Trust
B · 89/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 96 − adoption risk = 89/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 3.6 = 96. What the published surface and source actually contain:

PointsWhat was foundCategory
−3.6 Near-miss of exa-mcp-server MTC-SUP-005 supply-chain

2. Client adoption risk — 96 − 7 = 89. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/mcp/tools/srt.js)MTC-SRC-002

In the server's implementation (`dist/mcp/tools/srt.js:21`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: exec as cpExec } from 'child_process'; import { existsSync } from 'fs'; import { promisify } from 'util'; import { MaiC

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/mcp/tools/srt.js

medium Near-miss of exa-mcp-server (edit distance 2)MTC-SUP-005

"gia-mcp-server" is edit-distance 2 from the package "exa-mcp-server". Verify this is the intended package.

Fix: Confirm you meant "exa-mcp-server". Install packages only from their documented, official name.

Location: package gia-mcp-server

Tools 57

Each tool and what it can reach — statically extracted from the published source.

  • gia_scan_environmentreads sensitive data
  • agent_citizenship_statusno sensitive capability
  • agent_rightsno sensitive capability
  • approve_gateno sensitive capability
  • assess_risk_tierno sensitive capability
  • audit_pipelineno sensitive capability
  • board_approve_gateno sensitive capability
  • board_convene_sessionno sensitive capability
  • board_get_sessionno sensitive capability
  • board_install_kitno sensitive capability
Show 47 more tools ↓
  • board_list_chartersno sensitive capability
  • board_list_institutionsno sensitive capability
  • board_search_precedentno sensitive capability
  • branch_authority_statusno sensitive capability
  • chain_of_reasoningno sensitive capability
  • classify_decisionno sensitive capability
  • colony_convene_requestno sensitive capability
  • colony_healthno sensitive capability
  • colony_suggestionno sensitive capability
  • compose_memory_packsno sensitive capability
  • context_reviveno sensitive capability
  • distill_memory_packno sensitive capability
  • evaluate_routing_thresholdno sensitive capability
  • evaluate_thresholdno sensitive capability
  • export_ledgerno sensitive capability
  • generate_impact_reportno sensitive capability
  • generate_reportno sensitive capability
  • generate_value_reportno sensitive capability
  • get_gate_statusno sensitive capability
  • gia_apply_packno sensitive capability
  • gia_dry_run_packno sensitive capability
  • gia_ingest_documentno sensitive capability
  • gia_list_packsno sensitive capability
  • gia_retrieveno sensitive capability
  • gia_run_patrolno sensitive capability
  • governed_sampleno sensitive capability
  • list_available_toolsno sensitive capability
  • load_memory_packno sensitive capability
  • map_complianceno sensitive capability
  • monitor_agentsno sensitive capability
  • phoenix_recovery_healthno sensitive capability
  • phoenix_snapshotno sensitive capability
  • phoenix_verify_integrityno sensitive capability
  • promote_memory_packno sensitive capability
  • record_governance_eventno sensitive capability
  • record_value_metricno sensitive capability
  • request_contextno sensitive capability
  • score_governanceno sensitive capability
  • seal_memory_packno sensitive capability
  • srt_approve_repairno sensitive capability
  • srt_diagnoseno sensitive capability
  • srt_generate_postmortemno sensitive capability
  • srt_run_watchdogno sensitive capability
  • system_statusno sensitive capability
  • transfer_memory_packno sensitive capability
  • verify_ledgerno sensitive capability
  • verify_ledger_v2no sensitive capability

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.4.4 latest B 89/100 2 1.13.0 2026-09-07
v0.4.2 B 89/100 2 1.12.1 2026-07-29
v0.4.1 B 89/100 2 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 89/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/gia-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/gia-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/gia-mcp-server"><img src="https://mcptrustchecker.com/registry/gia-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/gia-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan gia-mcp-server --online

Use the free API → How scoring works

More in AI & Agents