Cesium MCP

Protocol-agnostic CesiumJS AI control runtime for MCP, WebMCP, function calling, and browser agents.

MCP Servers JavaScript Grade C Listed MIT
60.1/100
Rank #583 of 1328
Compare Cesium MCP

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-09-08 · 0d ago
Recent change
Grade Changed +10

Is Cesium MCP safe? Cesium MCP scores 60.1/100 (Grade C), ranked #583 of 1328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.1/10; 37% of recent commits are signed; last pushed 2026-09-08. 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
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 514 spots (#1101 → #587)
2026-09-07
HVTrust Changed
HVTrust up 19.5pts (40.4 → 59.9)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.1/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
61.2
Activity sub-score · out of 100
#315

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-09-08 15:03 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
136
Forks
26
Last Push
2026-09-08
today
Commits (4 wk)
21
Downloads (7d)
35
npm
HN mentions (30d)
Open Issues
1
Rank Change
▲4
was #587

Analysis

HVTrust Dimensions vs MCP Servers

60.1 / 100 · 100.0% confidence

Cesium MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.0 / 25
2.9 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.0 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
17.4 / 20
5.2 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.2 / 20
in line with avg 6.9

Activity Inputs

61.2 / 100
StarsRepository reach
12.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
16.7 / 25
CommunityFork signal
6.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.1 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
37%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 8
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 6
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Cesium MCP safe?

Cesium 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 Cesium MCP publish package provenance?
No published build provenance is currently detected for Cesium MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Cesium MCP have an OpenSSF Scorecard?
Cesium MCP has an OpenSSF Scorecard score of 4.1/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 Cesium MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Cesium MCP use?
Cesium MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Cesium MCP's commits signed?
37% of the last 100 commits to Cesium 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
Cesium MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 Cesium MCP?

For maintainers

HVTrust scores Cesium 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.

Reputation Timeline

Signal history
Rank 18HVTrust 2Listed 1Scorecard 1Grade 1
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 514 spots (#1101 → #587)
2026-09-07
HVTrust Changed
HVTrust up 19.5pts (40.4 → 59.9)
2026-09-06
Rank Moved
Rank dropped 14 spots (#1087 → #1101)
2026-09-05
Rank Moved
Rank dropped 40 spots (#1047 → #1087)
2026-09-04
Rank Moved
Rank dropped 34 spots (#1013 → #1047)
2026-09-03
Rank Moved
Rank dropped 57 spots (#956 → #1013)
2026-09-02
Rank Moved
Rank dropped 37 spots (#919 → #956)
2026-09-01
Scorecard Added
OSSF Scorecard: 4.1/10
2026-09-01
Rank Moved
Rank rose 256 spots (#1175 → #919)
2026-09-01
HVTrust Changed
HVTrust up 17.3pts (23.0 → 40.3)
2026-08-31
Rank Moved
Rank dropped 29 spots (#1146 → #1175)
2026-08-30
Rank Moved
Rank dropped 38 spots (#1108 → #1146)
2026-08-29
Rank Moved
Rank dropped 37 spots (#1071 → #1108)
2026-08-28
Rank Moved
Rank dropped 38 spots (#1033 → #1071)
2026-08-27
Rank Moved
Rank dropped 23 spots (#1010 → #1033)
2026-08-26
Rank Moved
Rank dropped 93 spots (#917 → #1010)
2026-08-24
Rank Moved
Rank dropped 10 spots (#910 → #920)
2026-08-17
Rank Moved
Rank rose 11 spots (#943 → #932)
2026-08-16
Rank Moved
Rank dropped 29 spots (#914 → #943)
2026-08-13
Rank Moved
Rank dropped 11 spots (#900 → #911)
2026-08-10
Rank Moved
Rank dropped 47 spots (#855 → #902)
2026-08-08
Newly Listed
First tracked at rank #851

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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