Unity API Documentation

Instant, accurate Unity API lookups instead of expensive source file reads, saving your agent tokens, context, and hallucinations

MCP Servers Python Listed MIT

Is Unity API Documentation safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.7 / 10
Provenance Attested
Signed commits 2%
Last push 16d ago
Advisories None known
Compare Unity API Documentation
Suggest a correction

In detail: Unity API Documentation scores 69.4/100 (Grade B), ranked #388 of 1387 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.7/10; 2% of recent commits are signed; no published advisory affects its latest release (unity-api-mcp); last pushed 2026-10-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How Unity API Documentation 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.

Chain of custody

Scanners check what the code says. This traces who ships Unity API Documentation 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/Codeturion/unity-api-mcp, MIT, last pushed 2026-10-26. 2% 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.7/10 (scanned Nov 4, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions8
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    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 -1
    Token-Permissions 8
    Vulnerabilities 10
  3. Published packages Linked and attested

    • PyPI unity-api-mcp Source link points back to this repo Build provenance attested
  4. What you install today No known advisories

    Latest release checked: unity-api-mcp 2.1.1. No published advisory affects it (OSV, checked 2026-11-11).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-28 OSSF Scorecard: 4.7/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 Unity API Documentation’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.

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 Unity API Documentation compares in MCP Servers

  1. #227 ProxmoxMCP-Plus 69.6 +0.2
  2. #228 JavaLens 69.5 +0.1
  3. #229 Unity API Documentation 69.4 this agent
  4. #230 Grafana MCP Server 68.8 −0.6
  5. #231 Ai Cli MCP 68.8 −0.6

Bars show each HVTrust score; the tick marks Unity API Documentation’s 69.4.

Where the 69.4 comes from

HVTrust dimensions vs the MCP Servers average

69.4 / 100 · 100.0% confidence

Unity API Documentation MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.5 / 25
2.7 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
12.5 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.8 / 20
0.5 above avg 12.3
AdoptionLog-scaled stars · package downloads
6.6 / 20
1.0 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-05
Rank Moved
Rank rose 30 spots (#394 → #364)
2026-11-04
Rank Moved
Rank rose 35 spots (#429 → #394)
2026-10-21
Rank Moved
Rank dropped 32 spots (#361 → #393)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/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
View MCP Servers Report missing data
43.8
Activity sub-score · out of 100
#229

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-11-11 00:08 UTC · Repo last pushed 16 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
66
Forks
6
Last Push
2026-10-26
16 days ago
Commits (4 wk)
2
Downloads (7d)
49
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▼9
was #379

Analysis

Activity Inputs

43.8 / 100
StarsRepository reach
11.0 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
3.9 / 20

Common questions about Unity API Documentation

Unity API Documentation 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 Unity API Documentation publish package provenance?
Yes. Unity API Documentation's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Unity API Documentation have an OpenSSF Scorecard?
Unity API Documentation has an OpenSSF Scorecard score of 4.7/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 Unity API Documentation actively maintained?
Maintained. Last push was 16 days ago.
What license does Unity API Documentation use?
Unity API Documentation ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Unity API Documentation's commits signed?
2% of the last 100 commits to Unity API Documentation 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
medium confidence
Implemented
Unity API Documentation 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 Unity API Documentation'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 Unity API Documentation?

For maintainers

HVTrust scores Unity API Documentation 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 23HVTrust 4Grade 4Score 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-05
Rank Moved
Rank rose 30 spots (#394 → #364)
2026-11-04
Rank Moved
Rank rose 35 spots (#429 → #394)
2026-10-21
Rank Moved
Rank dropped 32 spots (#361 → #393)
2026-10-13
Rank Moved
Rank rose 10 spots (#364 → #354)
2026-10-12
Grade Changed
Trust grade C → B
2026-10-12
Rank Moved
Rank rose 215 spots (#579 → #364)
2026-10-12
HVTrust Changed
HVTrust up 6.6pts (62.9 → 69.5)
2026-10-12
Activity Score Changed
Activity score up 18pts (28 → 46)
2026-10-02
Rank Moved
Rank dropped 18 spots (#522 → #540)
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 → C
2026-09-23
Rank Moved
Rank rose 606 spots (#1118 → #512)
2026-09-23
HVTrust Changed
HVTrust up 42.1pts (21.7 → 63.8)
2026-09-22
Newly Listed
First tracked at rank #1118
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 13 spots (#470 → #483)
2026-09-17
Rank Moved
Rank dropped 10 spots (#460 → #470)
2026-09-15
Grade Changed
Trust grade B → C
2026-09-11
Rank Moved
Rank dropped 19 spots (#429 → #448)
2026-09-07
Rank Moved
Rank dropped 25 spots (#386 → #411)
2026-09-05
Rank Moved
Rank dropped 70 spots (#309 → #379)
2026-09-04
Rank Moved
Rank dropped 17 spots (#292 → #309)
2026-09-03
Rank Moved
Rank dropped 16 spots (#276 → #292)
2026-08-31
Rank Moved
Rank dropped 30 spots (#240 → #270)
2026-08-28
Scorecard Added
OSSF Scorecard: 4.7/10
2026-08-28
Grade Changed
Trust grade C → B
2026-08-28
Rank Moved
Rank rose 209 spots (#447 → #238)
2026-08-28
HVTrust Changed
HVTrust up 9.8pts (56.6 → 66.4)
2026-08-27
Rank Moved
Rank dropped 12 spots (#435 → #447)
2026-08-26
Rank Moved
Rank dropped 41 spots (#394 → #435)
2026-08-24
Rank Moved
Rank dropped 20 spots (#372 → #392)
2026-08-22
Rank Moved
Rank rose 17 spots (#391 → #374)
2026-08-19
Rank Moved
Rank dropped 17 spots (#374 → #391)
2026-08-18
Rank Moved
Rank dropped 71 spots (#303 → #374)
2026-08-18
HVTrust Changed
HVTrust down 4.1pts (61.3 → 57.2)
2026-08-18
Activity Score Changed
Activity score down 13pts (48 → 36)
2026-08-17
Rank Moved
Rank rose 15 spots (#318 → #303)

Embed Badge Badge guide for maintainers →

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