ITASCA MCP Server

MCP server connecting AI agents to ITASCA engines (PFC, FLAC, 3DEC, MPoint, MassFlow) — run geotechnical & geomechanics

MCP Servers Python Grade B Listed MIT
74.5/100
Rank #157 of 1320
Compare ITASCA MCP Server

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-28 · 7d ago
Recent change
Rank +4

Is ITASCA MCP Server safe? ITASCA MCP Server scores 74.5/100 (Grade B), ranked #157 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 3.6/10; 57% of recent commits are signed; last pushed 2026-08-28. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-09-03
Rank Moved
Rank dropped 11 spots (#141 → #152)
2026-08-31
Rank Moved
Rank dropped 17 spots (#117 → #134)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.6/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/10. Tighten the weakest checks to improve public safety evidence.
67.3
Activity sub-score · out of 100
#78

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 7 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
172
Forks
13
Last Push
2026-08-28
7 days ago
Commits (4 wk)
92
Downloads (7d)
333
pypi
HN mentions (30d)
Open Issues
0
Rank Change
▼5
was #152

Analysis

HVTrust Dimensions vs MCP Servers

74.5 / 100 · 100.0% confidence

ITASCA MCP Server MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.8 / 25
5.2 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
11.6 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.4 / 20
7.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
8.7 / 20
2.4 above avg 6.3

Activity Inputs

67.3 / 100
StarsRepository reach
13.4 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
24.6 / 25
CommunityFork signal
5.3 / 20

Supply Chain Trust

Package Provenance
Verified
pypi attestation
OSSF Scorecard
3.6 / 10
OpenSSF Scorecard · scanned Aug 31, 2026
Signed Commits
57%
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 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is ITASCA MCP Server safe?

ITASCA MCP Server 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 ITASCA MCP Server publish package provenance?
Yes. ITASCA MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does ITASCA MCP Server have an OpenSSF Scorecard?
ITASCA MCP Server has an OpenSSF Scorecard score of 3.6/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 ITASCA MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does ITASCA MCP Server use?
ITASCA MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are ITASCA MCP Server's commits signed?
56% of the last 100 commits to ITASCA MCP Server 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
ITASCA MCP Server 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
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain ITASCA MCP Server?

For maintainers

HVTrust scores ITASCA MCP Server 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.

Reputation Timeline

Signal history
Rank 12Listed 1HVTrust 1Scorecard 1
2026-09-03
Rank Moved
Rank dropped 11 spots (#141 → #152)
2026-08-31
Rank Moved
Rank dropped 17 spots (#117 → #134)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.6/10
2026-08-29
Rank Moved
Rank rose 82 spots (#206 → #124)
2026-08-29
HVTrust Changed
HVTrust up 7.4pts (67.9 → 75.3)
2026-08-26
Rank Moved
Rank dropped 16 spots (#188 → #204)
2026-08-24
Rank Moved
Rank dropped 10 spots (#177 → #187)
2026-08-22
Rank Moved
Rank rose 11 spots (#186 → #175)
2026-08-19
Rank Moved
Rank dropped 10 spots (#172 → #182)
2026-08-17
Rank Moved
Rank rose 11 spots (#188 → #177)
2026-08-15
Rank Moved
Rank rose 13 spots (#195 → #182)
2026-08-13
Rank Moved
Rank rose 11 spots (#203 → #192)
2026-08-12
Rank Moved
Rank rose 12 spots (#215 → #203)
2026-08-10
Rank Moved
Rank dropped 18 spots (#190 → #208)
2026-08-08
Newly Listed
First tracked at rank #198

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 74.5 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/itasca-mcp-server.svg)](https://hvtracker.net/agents/itasca-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/itasca-mcp-server"><img src="https://hvtracker.net/badge/itasca-mcp-server.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