SpaceFrontiers MCP
Machine Library by Space Frontiers: citable research retrieval for AI agents across papers, books, patents, Wikipedia, and public discussions.
Is SpaceFrontiers MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare SpaceFrontiers MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: SpaceFrontiers MCP scores 44.1/100 (Grade D), ranked #1082 of 1325 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 3.4/10; 3% of recent commits are signed; last pushed 2026-09-12. Every point is earned from checkable signals — never paid placement. How scoring works →
How SpaceFrontiers MCP compares in MCP Servers
- #632 Ocm MCP Server 44.3 +0.2
- #633 Revolut MCP 44.2 +0.1
- #634 SpaceFrontiers MCP 44.1 this agent
- #635 JavaLens 44.1 ±0
- #636 Word MCP Live 44.1 ±0
Bars show each HVTrust score; the tick marks SpaceFrontiers MCP’s 44.1.
Where the 44.1 comes from
HVTrust dimensions vs the MCP Servers average
44.1 / 100 · 100.0% confidenceSpaceFrontiers MCP MCP Servers average (775 agents)
Quick Trust Read
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 →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
42.3 / 100Supply Chain Trust
Common questions about SpaceFrontiers MCP
Does SpaceFrontiers MCP publish package provenance?
Does SpaceFrontiers MCP have an OpenSSF Scorecard?
Is SpaceFrontiers MCP actively maintained?
What license does SpaceFrontiers MCP use?
Are SpaceFrontiers MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/spacefrontiers-mcp)
<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
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON