Loomle
Website
Agent-native Unreal Engine tooling through MCP
Is Loomle safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Loomle
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Loomle scores 39.9/100 (Grade D), ranked #1176 of 1343 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.1/10; recent commits are unsigned; last pushed 2026-08-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Loomle 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.
- Raise the OSSF Scorecard from 3.1 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.3 → 52.2 C · #498 of 778
- Sign every commit0% signed today +5.0 → 44.9 D · #633 of 778
How Loomle compares in MCP Servers
- #695 Astravue MCP 40.1 +0.2
- #696 Gopls MCP 39.9 ±0
- #697 Loomle 39.9 this agent
- #698 MCP Server Code Runner 39.7 −0.2
- #699 Pagecast 39.5 −0.4
Bars show each HVTrust score; the tick marks Loomle’s 39.9.
Where the 39.9 comes from
HVTrust dimensions vs the MCP Servers average
39.9 / 100 · 100.0% confidenceLoomle MCP Servers average (778 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
29.8 / 100Supply Chain Trust
Common questions about Loomle
Does Loomle publish package provenance?
Does Loomle have an OpenSSF Scorecard?
Is Loomle actively maintained?
What license does Loomle use?
Are Loomle'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 Loomle'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 Loomle?
For maintainers
HVTrust scores Loomle 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/loomle)
<a href="https://hvtracker.net/agents/loomle"><img src="https://hvtracker.net/badge/loomle.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.4 · Raw JSON