updated 2026-11-10 04:07 UTC

Maya MCP

Repository Website

Local, typed MCP server for controlling Autodesk Maya via commandPort

MCP Servers Python Listed MIT

Is Maya MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.0 / 10
Provenance Attested
Signed commits 28%
Last push 88d ago
Advisories None known
Compare Maya MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Maya MCP scores 62.9/100 (Grade C), ranked #610 of 1374 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 4.0/10; 28% of recent commits are signed; no published advisory affects its latest release (maya-mcp); last pushed 2026-08-14. Every point is earned from checkable signals — never paid placement. How scoring works →

How Maya 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 Maya 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/GimbalGoats/GG_MayaMCP, MIT, last pushed 2026-08-14. 28% 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 4, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked and attested

    • PyPI maya-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: maya-mcp 0.6.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-11 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 Maya 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 Maya MCP compares in MCP Servers

  1. #335 Sub Agents MCP 62.9 ±0
  2. #336 MCP Devkit Server 62.9 ±0
  3. #337 Maya MCP 62.9 this agent
  4. #338 IvanMurzak Unity MCP 62.9 ±0
  5. #339 Codex Control Plane MCP 62.8 −0.1

Bars show each HVTrust score; the tick marks Maya MCP’s 62.9.

Where the 62.9 comes from

HVTrust dimensions vs the MCP Servers average

62.9 / 100 · 100.0% confidence

Maya MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.9 / 25
3.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above 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
6.1 / 20
6.1 below avg 12.2
AdoptionLog-scaled stars · package downloads
7.0 / 20
0.6 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-03
Rank Moved
Rank dropped 12 spots (#574 → #586)
2026-10-24
Rank Moved
Rank rose 12 spots (#569 → #557)
2026-10-15
Rank Moved
Rank dropped 29 spots (#518 → #547)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/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.
Refresh maintenance signals The repo was last pushed 88 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
26.6
Activity sub-score · out of 100
#337
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 C 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 88 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
34
Forks
8
Last Push
2026-08-14
88 days ago
Commits (4 wk)
0
Downloads (7d)
280
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▼4
was #606

Analysis

Activity Inputs

26.6 / 100
StarsRepository reach
9.3 / 30
FreshnessLast push recency
12.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
4.4 / 20

Common questions about Maya MCP

Maya 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 Maya MCP publish package provenance?
Yes. Maya MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Maya MCP have an OpenSSF Scorecard?
Maya 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 Maya MCP actively maintained?
Slowing down. Last push was 88 days ago — keep an eye on whether activity resumes.
What license does Maya MCP use?
Maya MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Maya MCP's commits signed?
28% of the last 100 commits to Maya 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
Maya 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
How this surface has changed

Detected changes to Maya 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-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Maya MCP?

For maintainers

HVTrust scores Maya 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 20Grade 4HVTrust 3Score 1Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-03
Rank Moved
Rank dropped 12 spots (#574 → #586)
2026-10-24
Rank Moved
Rank rose 12 spots (#569 → #557)
2026-10-15
Rank Moved
Rank dropped 29 spots (#518 → #547)
2026-10-13
Grade Changed
Trust grade B → C
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 680 spots (#1119 → #439)
2026-09-23
HVTrust Changed
HVTrust up 44.2pts (21.7 → 65.9)
2026-09-22
Newly Listed
First tracked at rank #1119
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Scorecard Added
OSSF Scorecard: 4.3/10
2026-09-11
Grade Changed
Trust grade C → B
2026-09-11
Rank Moved
Rank rose 268 spots (#666 → #398)
2026-09-11
HVTrust Changed
HVTrust up 9.0pts (57.8 → 66.8)
2026-09-07
Rank Moved
Rank dropped 49 spots (#609 → #658)
2026-09-05
Rank Moved
Rank dropped 76 spots (#525 → #601)
2026-09-04
Rank Moved
Rank dropped 25 spots (#500 → #525)
2026-09-03
Rank Moved
Rank dropped 20 spots (#480 → #500)
2026-09-02
Rank Moved
Rank dropped 14 spots (#466 → #480)
2026-09-01
Rank Moved
Rank dropped 18 spots (#448 → #466)
2026-08-31
Rank Moved
Rank dropped 31 spots (#417 → #448)
2026-08-30
Rank Moved
Rank rose 13 spots (#430 → #417)
2026-08-29
Rank Moved
Rank dropped 14 spots (#416 → #430)
2026-08-27
Rank Moved
Rank dropped 10 spots (#401 → #411)
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 255 spots (#656 → #401)
2026-08-26
HVTrust Changed
HVTrust up 19.3pts (39.1 → 58.4)
2026-08-19
Rank Moved
Rank dropped 22 spots (#634 → #656)
2026-08-16
Rank Moved
Rank dropped 11 spots (#617 → #628)
2026-08-15
Rank Moved
Rank dropped 17 spots (#600 → #617)
2026-08-15
Activity Score Changed
Activity score down 5pts (43 → 38)
2026-08-14
Rank Moved
Rank rose 20 spots (#620 → #600)
GitHub → Website → PyPI: maya-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/maya-mcp.svg)](https://hvtracker.net/agents/maya-mcp)
HTML:
<a href="https://hvtracker.net/agents/maya-mcp"><img src="https://hvtracker.net/badge/maya-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.4 · Raw JSON