updated 2026-09-04 23:32 UTC

SageMath MCP

XBP-Europe/sagemath-mcp

Stateful SageMath MCP server: 37 tools for symbolic math, algebra, number theory, graphs and plotting. A persistent Sage

MCP Servers Python Grade B Listed MIT
76.8/100
Rank #133 of 1320
Compare SageMath MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-24 · 11d ago
Recent change
Rank +5

Is SageMath MCP safe? SageMath MCP scores 76.8/100 (Grade B), ranked #133 of 1320 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.5/10; 18% of recent commits are signed; last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#63 Fred MCP Server — 77.0 (B) → #64 build123d MCP — 76.9 (B) → #66 Notion MCP Server — 76.6 (B) → #67 Teamcity MCP — 76.4 (B) →

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 13 spots (#116 → #129)
2026-09-02
Scorecard Added
OSSF Scorecard: 5.5/10
2026-09-02
Rank Moved
Rank rose 154 spots (#270 → #116)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for SageMath MCP View MCP Servers Report missing data
55.6
Activity sub-score · out of 100
#65
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 B 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-09-04 23:32 UTC · Repo last pushed 11 days ago

Rank Trend

2026-08-16 2026-09-04

Activity & Reach

Stars
14
Forks
0
Last Push
2026-08-24
11 days ago
Commits (4 wk)
139
Downloads (7d)
39
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▼4
was #129

Analysis

HVTrust Dimensions vs MCP Servers

76.8 / 100 · 100.0% confidence

SageMath MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
15.3 / 25
5.7 above avg 9.6
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
1.4 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.3 / 20
7.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
5.0 / 20
1.3 below avg 6.3

Activity Inputs

55.6 / 100
StarsRepository reach
7.1 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
5.5 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
18%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 10

Is SageMath MCP safe?

Public supply-chain signals for SageMath MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but SageMath MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does SageMath MCP publish package provenance?
Yes. SageMath MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does SageMath MCP have an OpenSSF Scorecard?
SageMath MCP has an OpenSSF Scorecard score of 5.5/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 SageMath MCP actively maintained?
Maintained. Last push was 11 days ago.
What license does SageMath MCP use?
SageMath MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SageMath MCP's commits signed?
18% of the last 100 commits to SageMath 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
SageMath MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool 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

Maintain SageMath MCP?

For maintainers

HVTrust scores SageMath 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 11Listed 1HVTrust 1Scorecard 1
2026-09-03
Rank Moved
Rank dropped 13 spots (#116 → #129)
2026-09-02
Scorecard Added
OSSF Scorecard: 5.5/10
2026-09-02
Rank Moved
Rank rose 154 spots (#270 → #116)
2026-09-02
HVTrust Changed
HVTrust up 11.5pts (66.3 → 77.8)
2026-08-31
Rank Moved
Rank dropped 28 spots (#239 → #267)
2026-08-29
Rank Moved
Rank dropped 10 spots (#234 → #244)
2026-08-27
Rank Moved
Rank dropped 12 spots (#220 → #232)
2026-08-26
Rank Moved
Rank dropped 17 spots (#203 → #220)
2026-08-24
Rank Moved
Rank dropped 13 spots (#189 → #202)
2026-08-23
Rank Moved
Rank rose 11 spots (#200 → #189)
2026-08-22
Rank Moved
Rank rose 13 spots (#213 → #200)
2026-08-19
Rank Moved
Rank dropped 10 spots (#195 → #205)
2026-08-17
Rank Moved
Rank rose 13 spots (#202 → #189)
2026-08-16
Newly Listed
First tracked at rank #202
GitHub → PyPI: sagemath-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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