Is SageMath MCP safe to use?

SageMath MCP has an HVTrust score of 66.6/100 (Grade B), ranked #203 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for SageMath MCP?

SageMath MCP scores 66.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 12 GitHub stars and is categorized under MCP Servers.

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

66.6/100

Rank #203 of 1308

Compare SageMath MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-16 · 1d ago

Recent change

New

Is SageMath MCP safe? SageMath MCP scores 66.6/100 (Grade B), ranked #203 of 1308 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; no OSSF Scorecard result yet; 15% of recent commits are signed; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#59 Laravel Boost — 66.6 (B) → #60 Linux MCP Server — 66.6 (B) → #62 Reversecore MCP — 66.5 (B) → #63 Awkoy Notion MCP Server — 66.4 (B) →

Quick Trust Read

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-08-16

Newly Listed

First tracked at rank #202

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

56.7

Activity sub-score · out of 100

#61

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 →

Activity & Reach

Stars

Forks

Last Push

2026-08-16

yesterday

Commits (4 wk)

125

Downloads (7d)

288

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #202

Analysis

HVTrust Dimensions vs MCP Servers

66.6 / 100 · 100.0% confidence

SageMath MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

8.2 / 25

3.2 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

in line with avg 8.8

Maintenance60% last-push freshness · 40% commit activity

19.9 / 20

7.5 above avg 12.4

AdoptionLog-scaled stars · package downloads

6.0 / 20

in line with avg 5.8

Activity Inputs

56.7 / 100

StarsRepository reach

6.7 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

0.0 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

15%

of last 100 commits verified

Is SageMath MCP safe?

SageMath MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

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?

No OpenSSF Scorecard data is currently published for SageMath MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.

Is SageMath MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

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?

15% 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

2026-08-16

Newly Listed

First tracked at rank #202

GitHub → PyPI: sagemath-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON