updated 2026-10-16 20:06 UTC

SpaceFrontiers MCP

Repository Website

Machine Library by Space Frontiers: citable research retrieval for AI agents across papers, books, patents, Wikipedia, and public discussions.

MCP Servers Python Listed MIT

Is SpaceFrontiers MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.6 / 10
Provenance None
Signed commits 8%
Last push yesterday
Compare SpaceFrontiers MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: SpaceFrontiers MCP scores 46.6/100 (Grade D), ranked #1087 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.6/10; 8% of recent commits are signed; last pushed 2026-10-15. Every point is earned from checkable signals — never paid placement. How scoring works →

How SpaceFrontiers 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 SpaceFrontiers MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/SpaceFrontiers/mcp, MIT, last pushed 2026-10-15. 8% 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.6/10 (scanned Oct 13, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions10
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 9
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 10
    Vulnerabilities 10

  3. Published packages None

    No registry package. SpaceFrontiers MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-03 OSSF Scorecard: 3.1/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues SpaceFrontiers 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 SpaceFrontiers MCP compares in MCP Servers

  1. #619 Kronan MCP 46.8 +0.2
  2. #620 MTG MCP Server 46.7 +0.1
  3. #621 SpaceFrontiers MCP 46.6 this agent
  4. #622 Infobip MCP 46.6 ±0
  5. #623 Danishashko Yahoo Finance 46.6 ±0

Bars show each HVTrust score; the tick marks SpaceFrontiers MCP’s 46.6.

Where the 46.6 comes from

HVTrust dimensions vs the MCP Servers average

46.6 / 100 · 100.0% confidence

SpaceFrontiers MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
6.1 / 25
4.4 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.4 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.7 / 20
1.4 above avg 12.3
AdoptionLog-scaled stars · package downloads
2.6 / 20
4.8 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-13
Rank Moved
Rank dropped 35 spots (#1043 → #1078)
2026-10-12
Rank Moved
Rank dropped 24 spots (#1019 → #1043)
2026-10-08
Rank Moved
Rank rose 60 spots (#1058 → #998)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.6/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.
Compare with another agent Get email alerts for SpaceFrontiers MCP View MCP Servers Report missing data
46.6
Activity sub-score · out of 100
#621
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
11
Forks
6
Last Push
2026-10-15
yesterday
Commits (4 wk)
7?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼4
was #1083

Analysis

Activity Inputs

46.6 / 100
StarsRepository reach
6.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
3.9 / 20

Common questions about SpaceFrontiers MCP

Public trust evidence for SpaceFrontiers MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does SpaceFrontiers MCP publish package provenance?
No published build provenance is currently detected for SpaceFrontiers 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 SpaceFrontiers MCP have an OpenSSF Scorecard?
SpaceFrontiers MCP has an OpenSSF Scorecard score of 4.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 SpaceFrontiers MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does SpaceFrontiers MCP use?
SpaceFrontiers MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are SpaceFrontiers MCP's commits signed?
7% of the last 100 commits to SpaceFrontiers 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
SpaceFrontiers MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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
N/A
No package source configured
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 SpaceFrontiers 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

Maintain SpaceFrontiers MCP?

For maintainers

HVTrust scores SpaceFrontiers 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 24HVTrust 3Listed 2Scorecard 1Score 1Delisted 1MCP 1
2026-10-13
Rank Moved
Rank dropped 35 spots (#1043 → #1078)
2026-10-12
Rank Moved
Rank dropped 24 spots (#1019 → #1043)
2026-10-08
Rank Moved
Rank rose 60 spots (#1058 → #998)
2026-10-06
Rank Moved
Rank rose 12 spots (#1069 → #1057)
2026-10-04
Rank Moved
Rank rose 44 spots (#1107 → #1063)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 491 spots (#585 → #1076)
2026-09-23
HVTrust Changed
HVTrust up 9.7pts (34.6 → 44.3)
2026-09-22
Newly Listed
First tracked at rank #585
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank rose 19 spots (#1105 → #1086)
2026-09-12
Rank Moved
Rank rose 64 spots (#1169 → #1105)
2026-09-12
HVTrust Changed
HVTrust up 4.3pts (38.7 → 43.0)
2026-09-12
Activity Score Changed
Activity score up 15pts (29 → 44)
2026-09-09
Rank Moved
Rank dropped 16 spots (#1152 → #1168)
2026-09-07
Rank Moved
Rank dropped 18 spots (#1127 → #1145)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1112 → #1127)
2026-09-05
Rank Moved
Rank dropped 38 spots (#1074 → #1112)
2026-09-04
Rank Moved
Rank dropped 27 spots (#1047 → #1074)
2026-09-03
Scorecard Added
OSSF Scorecard: 3.1/10
2026-09-03
Rank Moved
Rank rose 256 spots (#1303 → #1047)
2026-09-03
HVTrust Changed
HVTrust up 22.3pts (16.9 → 39.2)
2026-09-02
Rank Moved
Rank dropped 12 spots (#1291 → #1303)
2026-08-30
Rank Moved
Rank dropped 12 spots (#1264 → #1276)
2026-08-29
Rank Moved
Rank dropped 11 spots (#1253 → #1264)
2026-08-28
Rank Moved
Rank dropped 24 spots (#1229 → #1253)
2026-08-27
Rank Moved
Rank dropped 10 spots (#1219 → #1229)
2026-08-26
Rank Moved
Rank dropped 40 spots (#1179 → #1219)
2026-08-19
Rank Moved
Rank dropped 10 spots (#1174 → #1184)
2026-08-16
Rank Moved
Rank dropped 24 spots (#1151 → #1175)
2026-08-13
Rank Moved
Rank dropped 10 spots (#1145 → #1155)
2026-08-10
Rank Moved
Rank dropped 71 spots (#1079 → #1150)
2026-08-08
Newly Listed
First tracked at rank #1078
GitHub → Website →

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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