GIA — Governed Intelligence Architecture

io.github.knowledgepa3Published by GitHub account knowledgepa3v0.4.4Updated Oct 24, 2026

Runtime AI governance: decision gates, human approval, hash-chained audit, compliance mapping.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

GIA (Governed Intelligence Architecture) is a remote or local MCP server that adds runtime AI governance: decision gates, human approval, hash-chained audit…

What you can do
  • The manifest lists no individual tools, so capabilities come from the registry description only.
  • Apply decision gates that check AI actions against governance rules at runtime.
  • Route actions to human approval before they proceed.
  • Record activity in a hash-chained audit trail.
  • Map activity to compliance requirements.
When to use it
Worth adding when an assistant's actions need oversight: gated decisions, human sign-off, tamper-evident audit records, or mapping activity to compliance frameworks.
Requirements
A GIA account and API key, sent as an Authorization bearer token (the endpoint also accepts a GIA_API_KEY query parameter; it does not accept x-api-key). Can be used as the remote endpoint or as the npm package gia-mcp-server over stdio, which needs Node.js.
Before you install
The API key is a credential; keep it out of shared logs and prefer the Authorization header over a query parameter, which can leak in URLs. The server governs and audits actions, so expect it to record what the assistant does. No tool list is published, so review the actual tools before relying on it.

Installation

In SourceWeft

  1. Open GIA — Governed Intelligence Architecture in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.knowledgepa3%2Fgia-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "gia-governed-intelligence-architecture": {
      "type": "http",
      "url": "https://gia.aceadvising.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.4.4LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.