Fulcrum

io.github.Dewars30Published by GitHub account Dewars30v1.1.0Updated Oct 24, 2026

AI governance MCP server for policy enforcement, cost control, and observability.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

An AI governance MCP server that enforces policies, controls costs, and provides observability for AI usage.

What you can do
Fulcrum is an AI governance server that connects an assistant to a governance backend for policy enforcement, cost control, and observability. It runs locally over stdio and communicates with a Fulcrum gRPC API endpoint. The manifest does not list individual tools, so the exact operations are not documented here.
When to use it
Consider it when an organization needs to apply governance rules, track spending, or monitor AI usage through a centralized Fulcrum service. It is intended for teams already using or evaluating Fulcrum governance rather than for general-purpose tasks.
Requirements
Runs as a local process via npm package @fulcrum-governance/sdk or PyPI package fulcrum-governance over stdio. Requires a Fulcrum gRPC API endpoint (FULCRUM_API_ENDPOINT) and a tenant identifier (FULCRUM_TENANT_ID); an API key (FULCRUM_API_KEY) is optional for local development. Desktop only.
Before you install
The server asks for an API key (FULCRUM_API_KEY) and tenant identifier (FULCRUM_TENANT_ID), which are credentials that should be handled carefully. It connects to a Fulcrum API endpoint, so usage data may be sent to that service. No tools are listed, so review what actions it can take before installing.

Installation

In SourceWeft

  1. Open Fulcrum in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.