updated 2026-11-10 04:07 UTC

Mistral MCP

Repository

Mistral MCP server for document extraction: invoices, contracts and typed JSON from text, Markdown or OCR. Six-tool core, chat, vision, audio, stdio and Streamable HTTP.

MCP Servers TypeScript Listed MIT

Is Mistral MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.0 / 10
Provenance None
Signed commits 12%
Last push 42d ago
Advisories None known
Compare Mistral MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Mistral MCP scores 47.7/100 (Grade D), ranked #1072 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.0/10; 12% of recent commits are signed; no published advisory affects its latest release (mistral-mcp); last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mistral MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Mistral MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/Swih/mistral-mcp, MIT, last pushed 2026-09-29. 12% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.0/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm mistral-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: mistral-mcp 1.0.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-02 OSSF Scorecard: 4.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Mistral MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Mistral MCP compares in MCP Servers

  1. #604 Zscaler Zero Trust Exchange 47.8 +0.1
  2. #605 Cortex Gateway 47.7 ±0
  3. #606 Mistral MCP 47.7 this agent
  4. #607 Notebooklm MCP Secure 47.7 ±0
  5. #608 Glovebox MCP 47.7 ±0

Bars show each HVTrust score; the tick marks Mistral MCP’s 47.7.

Where the 47.7 comes from

HVTrust dimensions vs the MCP Servers average

47.7 / 100 · 100.0% confidence

Mistral MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.6 / 25
5.2 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
9.2 / 20
3.0 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.0 / 20
1.6 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-29
Grade Changed
Trust grade C → D
2026-10-29
Rank Moved
Rank dropped 62 spots (#999 → #1061)
2026-10-29
Activity Score Changed
Activity score down 8pts (38 → 30)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 42 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
28.7
Activity sub-score · out of 100
#606
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 42 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
15
Forks
2
Last Push
2026-09-29
42 days ago
Commits (4 wk)
0
Downloads (7d)
201
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▲1
was #1073

Analysis

Activity Inputs

28.7 / 100
StarsRepository reach
7.2 / 30
FreshnessLast push recency
19.2 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Common questions about Mistral MCP

Public trust evidence for Mistral MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Mistral MCP publish package provenance?
No published build provenance is currently detected for Mistral MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Mistral MCP have an OpenSSF Scorecard?
Mistral MCP has an OpenSSF Scorecard score of 4.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Mistral MCP actively maintained?
Slowing down. Last push was 42 days ago — keep an eye on whether activity resumes.
What license does Mistral MCP use?
Mistral MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mistral MCP's commits signed?
12% of the last 100 commits to Mistral MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Mistral MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Mistral MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Mistral AI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Mistral MCP?

For maintainers

HVTrust scores Mistral MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 35Score 5HVTrust 4Grade 3Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-10-29
Grade Changed
Trust grade C → D
2026-10-29
Rank Moved
Rank dropped 62 spots (#999 → #1061)
2026-10-29
Activity Score Changed
Activity score down 8pts (38 → 30)
2026-10-28
Rank Moved
Rank dropped 67 spots (#932 → #999)
2026-10-28
Activity Score Changed
Activity score down 6pts (44 → 38)
2026-10-22
Rank Moved
Rank dropped 11 spots (#913 → #924)
2026-10-20
Rank Moved
Rank dropped 10 spots (#898 → #908)
2026-10-17
Rank Moved
Rank dropped 10 spots (#878 → #888)
2026-10-15
Rank Moved
Rank dropped 14 spots (#858 → #872)
2026-10-10
Rank Moved
Rank dropped 29 spots (#808 → #837)
2026-10-09
Rank Moved
Rank dropped 15 spots (#793 → #808)
2026-10-04
Rank Moved
Rank rose 41 spots (#823 → #782)
2026-09-28
Rank Moved
Rank rose 35 spots (#909 → #874)
2026-09-28
Activity Score Changed
Activity score up 6pts (41 → 47)
2026-09-27
Rank Moved
Rank dropped 106 spots (#803 → #909)
2026-09-27
HVTrust Changed
HVTrust down 3.4pts (54.5 → 51.1)
2026-09-27
Activity Score Changed
Activity score down 7pts (48 → 41)
2026-09-24
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-24
Provider Added
Runtime surface grew — new detected provider dependencies: Anthropic, Mistral AI
2026-09-24
Rank Moved
Rank dropped 68 spots (#722 → #790)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 211 spots (#933 → #722)
2026-09-23
HVTrust Changed
HVTrust up 30.4pts (26.2 → 56.6)
2026-09-22
Newly Listed
First tracked at rank #933
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 13 spots (#776 → #789)
2026-09-15
Rank Moved
Rank rose 15 spots (#784 → #769)
2026-09-11
Rank Moved
Rank dropped 11 spots (#765 → #776)
2026-09-10
Rank Moved
Rank dropped 10 spots (#755 → #765)
2026-09-09
Rank Moved
Rank rose 11 spots (#766 → #755)
2026-09-07
Rank Moved
Rank dropped 65 spots (#697 → #762)
2026-09-06
Rank Moved
Rank dropped 11 spots (#686 → #697)
2026-09-05
Rank Moved
Rank dropped 77 spots (#609 → #686)
2026-09-04
Rank Moved
Rank dropped 19 spots (#590 → #609)
2026-09-03
Rank Moved
Rank dropped 32 spots (#558 → #590)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.3/10
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 538 spots (#1096 → #558)
2026-09-02
HVTrust Changed
HVTrust up 23.0pts (32.1 → 55.1)
2026-09-01
Rank Moved
Rank dropped 42 spots (#1054 → #1096)
2026-08-31
Rank Moved
Rank dropped 33 spots (#1021 → #1054)
2026-08-30
Rank Moved
Rank dropped 56 spots (#965 → #1021)
2026-08-29
Rank Moved
Rank dropped 45 spots (#920 → #965)
2026-08-28
Rank Moved
Rank rose 36 spots (#956 → #920)
2026-08-28
HVTrust Changed
HVTrust up 5.4pts (26.8 → 32.2)
2026-08-28
Activity Score Changed
Activity score up 21pts (26 → 48)
2026-08-27
Rank Moved
Rank dropped 28 spots (#928 → #956)
2026-08-26
Rank Moved
Rank dropped 113 spots (#815 → #928)
2026-08-24
Rank Moved
Rank dropped 12 spots (#804 → #816)
2026-08-19
Rank Moved
Rank dropped 10 spots (#805 → #815)
2026-08-16
Rank Moved
Rank dropped 15 spots (#797 → #812)
2026-08-13
Rank Moved
Rank dropped 11 spots (#782 → #793)
GitHub → npm: mistral-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 47.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mistral-mcp.svg)](https://hvtracker.net/agents/mistral-mcp)
HTML:
<a href="https://hvtracker.net/agents/mistral-mcp"><img src="https://hvtracker.net/badge/mistral-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON