updated 2026-10-16 16:07 UTC

Loomle

Repository Website

Agent-native Unreal Engine tooling through MCP

MCP Servers C++ Listed MIT

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

OSSF Scorecard 3.1 / 10
Provenance None
Signed commits 0%
Last push 4d ago
Compare Loomle

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Loomle scores 42.6/100 (Grade D), ranked #1166 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 3.1/10; recent commits are unsigned; last pushed 2026-10-12. 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Loomle 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 Unsigned

    github.com/loomle/loomle, MIT, last pushed 2026-10-12. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.1/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies4
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    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 4
    SAST 0
    Security-Policy 0
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. Loomle 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-08-26 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 Loomle’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 Loomle compares in MCP Servers

  1. #670 Ux MCP Server 42.9 +0.3
  2. #671 Deployhq MCP Server 42.9 +0.3
  3. #672 Loomle 42.6 this agent
  4. #673 spreadsheet-kit MCP 42.5 −0.1
  5. #674 Kolada MCP Server 42.4 −0.2

Bars show each HVTrust score; the tick marks Loomle’s 42.6.

Where the 42.6 comes from

HVTrust dimensions vs the MCP Servers average

42.6 / 100 · 100.0% confidence

Loomle MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.9 / 25
6.6 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
11.1 / 17
1.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
12.3 / 20
in line with avg 12.3
AdoptionLog-scaled stars · package downloads
2.8 / 20
4.6 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-12
Rank Moved
Rank rose 62 spots (#1210 → #1148)
2026-10-12
HVTrust Changed
HVTrust up 3.7pts (39.2 → 42.9)
2026-10-12
Activity Score Changed
Activity score up 10pts (28 → 38)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.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.
Compare with another agent Get email alerts for Loomle View MCP Servers Report missing data
37.9
Activity sub-score · out of 100
#672
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 16:07 UTC · Repo last pushed 4 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
13
Forks
3
Last Push
2026-10-12
4 days ago
Commits (4 wk)
1?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
21
Rank Change
▼3
was #1163

Analysis

Activity Inputs

37.9 / 100
StarsRepository reach
6.9 / 30
FreshnessLast push recency
24.4 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
2.8 / 20

Common questions about Loomle

Public trust evidence for Loomle 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 Loomle publish package provenance?
No published build provenance is currently detected for Loomle. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Loomle have an OpenSSF Scorecard?
Loomle has an OpenSSF Scorecard score of 3.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 Loomle actively maintained?
Actively maintained. The repository was pushed to within the last 4 day(s).
What license does Loomle use?
Loomle ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Loomle's commits signed?
0% of the last 100 commits to Loomle 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
Loomle 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
high confidence
Declared
Declared plugin/integration 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 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.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 24HVTrust 4Score 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-12
Rank Moved
Rank rose 62 spots (#1210 → #1148)
2026-10-12
HVTrust Changed
HVTrust up 3.7pts (39.2 → 42.9)
2026-10-12
Activity Score Changed
Activity score up 10pts (28 → 38)
2026-10-09
Rank Moved
Rank dropped 10 spots (#1191 → #1201)
2026-09-25
Rank Moved
Rank dropped 65 spots (#1095 → #1160)
2026-09-25
Activity Score Changed
Activity score down 9pts (39 → 30)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 475 spots (#620 → #1095)
2026-09-23
HVTrust Changed
HVTrust up 10.1pts (33.1 → 43.2)
2026-09-22
Newly Listed
First tracked at rank #620
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-17
Rank Moved
Rank dropped 115 spots (#960 → #1075)
2026-09-17
HVTrust Changed
HVTrust down 4.9pts (48.8 → 43.9)
2026-09-17
Activity Score Changed
Activity score down 15pts (56 → 41)
2026-09-12
Rank Moved
Rank dropped 13 spots (#942 → #955)
2026-09-11
Rank Moved
Rank dropped 12 spots (#930 → #942)
2026-09-09
Rank Moved
Rank dropped 12 spots (#918 → #930)
2026-09-08
Rank Moved
Rank dropped 16 spots (#902 → #918)
2026-09-07
Rank Moved
Rank dropped 39 spots (#863 → #902)
2026-09-06
Rank Moved
Rank dropped 14 spots (#849 → #863)
2026-09-05
Rank Moved
Rank dropped 60 spots (#789 → #849)
2026-09-04
Rank Moved
Rank dropped 31 spots (#758 → #789)
2026-09-03
Rank Moved
Rank dropped 46 spots (#712 → #758)
2026-09-02
Rank Moved
Rank dropped 37 spots (#675 → #712)
2026-09-01
Grade Changed
Trust grade C → D
2026-09-01
Rank Moved
Rank dropped 25 spots (#650 → #675)
2026-08-31
Rank Moved
Rank dropped 35 spots (#615 → #650)
2026-08-30
Rank Moved
Rank dropped 13 spots (#602 → #615)
2026-08-29
Rank Moved
Rank dropped 40 spots (#562 → #602)
2026-08-28
Rank Moved
Rank dropped 14 spots (#548 → #562)
2026-08-27
Rank Moved
Rank dropped 14 spots (#534 → #548)
2026-08-26
Scorecard Added
OSSF Scorecard: 3.1/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 410 spots (#944 → #534)
2026-08-26
HVTrust Changed
HVTrust up 27.6pts (22.6 → 50.2)
2026-08-22
Rank Moved
Rank rose 11 spots (#946 → #935)
2026-08-17
Rank Moved
Rank rose 22 spots (#964 → #942)
2026-08-16
Newly Listed
First tracked at rank #964
GitHub → Website →

Embed Badge Badge guide for maintainers →

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