Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

FairMind

PYPI · FAIRMIND-MCP

Release gate for AI systems from FairMind: evaluations, framework evidence and ledger snapshots.

Available components

+3 this week 82 Trust /100

Last scanned (13 hours ago)

Scores higher than 82% of PyPI servers

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to adhit-r/fairmind). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1591 tokens (~83/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 0
    • Malware scan: pass → unverified ▼ security
    • Schema quality: 97 → 83 ▲ functional
    • Package version: 0.3.1a0 → 0.4.2a0 functional
    • Package version: 0.3.1a0 → 0.4.1a0 functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 11 Nov 26 +2
    • Stability: unverified → 0.10 ▲ functional
  • 8 Nov 26 61

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed pypi/fairmind-mcp@0.4.2a0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo adhit-r/fairmind
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/adhit-r/fairmind/.github/workflows/release.yml@refs/tags/v0.4.2-alpha
Rekor log index 3935304571
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:820dbd065ddb110c9c149f2614473cac24a5e9e4a638f5843e3f32a168c075ac

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~1,406 tokens

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 →

Tool Tokens
attest_check ~95

Record that a person states a gate check is satisfied (manual evidence: it attests, it never proves). Only call this with a statement the user has given or confirmed; never invent one. `statement` is at least 12 characters; `reference` optionally points at a document or ticket.

NameTypeReqDescription
checkstringyes–
reference–––
statementstringyes–
system_idstringyes–

No output schema declared.

No examples provided.

clause_map ~65

Read the release gate per regulatory clause (EU AI Act, ISO 42001, NIST AI RMF, ...). `frameworks` optionally limits it to catalogue keys such as EUAIA or ISO42001.

NameTypeReqDescription
frameworks–––
system_idstringyes–

No output schema declared.

No examples provided.

create_evidence_pack ~105

Build a hashed inspection pack of the chosen systems' evidence and clause maps. `frameworks` are catalogue keys such as EUAIA or ISO42001. `share=true` also mints a read-only auditor token (shown once; the link is /verify/<pack id>?t=<token> on the FairMind site).

NameTypeReqDescription
frameworksarrayyes–
shareboolean––
system_idsarrayyes–
titlestringyes–

No output schema declared.

No examples provided.

create_remediation_task ~73

Open a remediation task for a system, optionally tied to a finding id from record_finding or list_findings.

NameTypeReqDescription
descriptionstringyes–
finding_id–––
owner–––
prioritystring––
system_idstringyes–
titlestringyes–

No output schema declared.

No examples provided.

describe_evaluation ~43

The files and params an evaluation takes before run_evaluation, and whether it can run as a behaviour test against the live system.

NameTypeReqDescription
evaluation_idstringyes–

No output schema declared.

No examples provided.

generate_report ~54

Generate and store an audit report snapshot (risks, evidence, approvals) for a system, and list the earlier ones.

NameTypeReqDescription
report_typestringyes–
system_idstringyes–
title–––

No output schema declared.

No examples provided.

get_system ~32

One AI system: name, owner, risk tier, lifecycle stage and metadata.

NameTypeReqDescription
system_idstringyes–

No output schema declared.

No examples provided.

list_evaluations ~60

Search FairMind's evaluation catalogue (for example "drift", "injection", "leakage", "counterfactual"). Each entry says what it measures, its pass threshold and whether FairMind can run it.

NameTypeReqDescription
query–––

No output schema declared.

No examples provided.

list_findings ~42

Recorded findings (risks) with counts by severity, and, when `system_id` is given, that system's remediation tasks.

NameTypeReqDescription
system_id–––

No output schema declared.

No examples provided.

list_systems ~30

List the AI systems the configured FairMind key can see, with id, risk tier and lifecycle stage.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

record_finding ~68

Record a risk finding against a system (for example risk_type "bias" or "privacy"). Use what was actually observed; never invent one.

NameTypeReqDescription
descriptionstringyes–
risk_typestringyes–
severitystringyes–
system_idstringyes–

No output schema declared.

No examples provided.

record_monitoring_snapshot ~104

Compare recent production decisions in a CSV on this machine against the system's latest fairness run (selection-rate drift, impact ratio, score PSI) and store the snapshot as measured evidence. Needs `prediction` (0/1) or `score` (0 to 1).

NameTypeReqDescription
attributesarrayyes–
csv_pathstringyes–
favorable_label–––
prediction–––
score–––
system_idstringyes–

No output schema declared.

No examples provided.

register_system ~86

Register an AI system. Without `workspace_id` it goes into the organisation's first workspace, or a new one named Default when there is none. Use the risk tier the user states; do not guess one.

NameTypeReqDescription
lifecycle_stagestring––
namestringyes–
owner–––
risk_tierstring––
workspace_id–––

No output schema declared.

No examples provided.

release_gate ~80

May this AI system ship? Returns the verdict (go, conditional_go, no_go), confidence, the five checks (each proven, attested or open), the reasons and the release decision status (not_requested, pending, approved, rejected). A release that needs sign-off may ship only when that status is approved.

NameTypeReqDescription
system_idstringyes–

No output schema declared.

No examples provided.

request_release_approval ~49

Ask for a release decision on a system, or read where the latest request stands. A person approves or rejects it in FairMind; this server cannot.

NameTypeReqDescription
system_idstringyes–

No output schema declared.

No examples provided.

run_evaluation ~132

Run a catalogue evaluation and store the result as measured evidence. `files` maps the file names from describe_evaluation to paths on this machine. `live=true` runs its behaviour test against the system's connected endpoint, judged by the organisation's model (this can take minutes). `use_connection=true` reads the organisation's connected agent platform instead of files. Returns passed, failed or insufficient with the metrics.

NameTypeReqDescription
evaluation_idstringyes–
files–––
liveboolean––
params–––
system_idstringyes–
use_connectionboolean––

No output schema declared.

No examples provided.

run_fairness_test ~151

Run a fairness test on a CSV on this machine (one row per decision) and store it as measured evidence. `outcome` is the column with what happened, `attributes` the protected attribute columns, and `prediction` (0/1) or `score` (0 to 1) the model's output column. `favorable_label` names the favourable value when a column is not 0/1. Returns the metrics and the updated gate.

NameTypeReqDescription
attributesarrayyes–
csv_pathstringyes–
favorable_label–––
outcomestringyes–
prediction–––
score–––
system_idstringyes–

No output schema declared.

No examples provided.

update_remediation_task ~41

Move a remediation task to a new status and/or add notes.

NameTypeReqDescription
notes–––
status–––
task_idstringyes–

No output schema declared.

No examples provided.

verify_evidence_pack ~96

Check an inspection pack: recompute its manifest hash and each system's evidence chain head and say whether it is intact. Give one of `path` (a downloaded pack.json on this machine, checked offline), `link` (an auditor share link, fetched then checked locally) or `pack_id` (a pack of the signed-in organisation).

NameTypeReqDescription
link–––
pack_id–––
path–––

No output schema declared.

No examples provided.

Install

How do I install the FairMind MCP server?

FairMind runs locally as a PyPI package, launched with uvx fairmind-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · fairmind-mcp

# add to Claude Code
claude mcp add adhit-r-fairmind -- uvx fairmind-mcp
Common questions

What is the FairMind MCP server?

FairMind is an MCP server listed in the public MCP registry as io.github.adhit-r/fairmind. Release gate for AI systems from FairMind: evaluations, framework evidence and ledger snapshots. This page covers its PyPI package (fairmind-mcp).

Is the FairMind MCP server safe to use?

FairMind scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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 FairMind MCP server expose?

FairMind exposes 19 tools: list_systems, get_system, register_system, release_gate, clause_map, and 14 more. Their descriptions and schemas cost roughly 1,406 tokens of context every time the server is loaded.

Is the FairMind MCP server still maintained?

FairMind is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the FairMind MCP server under?

FairMind declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the FairMind MCP server?

VerifyMCP ran 16 checks on FairMind, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.