updated 2026-10-17 20:06 UTC

InsForge InsForge

Repository by InsForge
MCP Servers TypeScript Listed Apache-2.0

Is InsForge InsForge safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10
Provenance None
Signed commits 30%
Last push 9d ago
Advisories None known
Compare InsForge InsForge

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: InsForge InsForge scores 60.7/100 (Grade C), ranked #660 of 1378 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 5.5/10; 30% of recent commits are signed; no published advisory affects its latest release (@insforge/mcp); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

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

  1. Source Partly signed

    github.com/InsForge/insforge-mcp, Apache-2.0, last pushed 2026-10-08. 30% 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 5.5/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 7

  3. Published packages Linked, not attested

    • npm @insforge/mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @insforge/mcp 1.2.11. No published advisory affects it (OSV, checked 2026-10-17).

Changes to this chain

  • 2026-08-28 OSSF Scorecard: 5.7/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

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

  1. #358 Porkbun DNS 🐷 60.9 +0.2
  2. #359 Nse Bse Indian Stock Market Data MCP 60.9 +0.2
  3. #360 InsForge InsForge 60.7 this agent
  4. #361 Laravel MCP Companion 60.6 −0.1
  5. #362 MCP Sqlite Tools 60.6 −0.1

Bars show each HVTrust score; the tick marks InsForge InsForge’s 60.7.

Where the 60.7 comes from

HVTrust dimensions vs the MCP Servers average

60.7 / 100 · 100.0% confidence

InsForge InsForge MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.4 / 25
2.1 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
13.2 / 17
0.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
15.2 / 20
2.9 above avg 12.3
AdoptionLog-scaled stars · package downloads
7.1 / 20
in line with 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-16
Rank Moved
Rank rose 45 spots (#703 → #658)
2026-10-11
Rank Moved
Rank dropped 50 spots (#632 → #682)
2026-10-10
Rank Moved
Rank dropped 21 spots (#611 → #632)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/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 InsForge InsForge View MCP Servers Report missing data
50.7
Activity sub-score · out of 100
#360
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 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-10-17 20:06 UTC · Repo last pushed 9 days ago

Rank Trend

2026-09-29 2026-10-17

Activity & Reach

Stars
37
Forks
14
Last Push
2026-10-08
9 days ago
Commits (4 wk)
8
Downloads (7d)
286
npm
HN mentions (30d)
—
Open Issues
18
Rank Change
▼2
was #658

Analysis

Activity Inputs

50.7 / 100
StarsRepository reach
9.5 / 30
FreshnessLast push recency
23.8 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
5.5 / 20

Common questions about InsForge InsForge

InsForge InsForge 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 InsForge InsForge publish package provenance?
No published build provenance is currently detected for InsForge InsForge. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does InsForge InsForge have an OpenSSF Scorecard?
InsForge InsForge has an OpenSSF Scorecard score of 5.5/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 InsForge InsForge actively maintained?
Maintained. Last push was 9 days ago.
What license does InsForge InsForge use?
InsForge InsForge ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are InsForge InsForge's commits signed?
30% of the last 100 commits to InsForge InsForge 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
InsForge InsForge 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
None detected
No clear plugin system or broad tool 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
How this surface has changed

Detected changes to InsForge InsForge'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 InsForge InsForge?

For maintainers

HVTrust scores InsForge InsForge 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 32HVTrust 3Score 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-16
Rank Moved
Rank rose 45 spots (#703 → #658)
2026-10-11
Rank Moved
Rank dropped 50 spots (#632 → #682)
2026-10-10
Rank Moved
Rank dropped 21 spots (#611 → #632)
2026-10-09
Rank Moved
Rank dropped 13 spots (#598 → #611)
2026-10-08
Rank Moved
Rank rose 65 spots (#663 → #598)
2026-10-06
Rank Moved
Rank rose 19 spots (#685 → #666)
2026-10-06
Activity Score Changed
Activity score up 5pts (46 → 51)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 265 spots (#924 → #659)
2026-09-23
HVTrust Changed
HVTrust up 32.5pts (26.3 → 58.8)
2026-09-22
Newly Listed
First tracked at rank #924
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-13
Rank Moved
Rank rose 41 spots (#667 → #626)
2026-09-11
Rank Moved
Rank dropped 18 spots (#644 → #662)
2026-09-10
Rank Moved
Rank rose 24 spots (#668 → #644)
2026-09-09
Rank Moved
Rank dropped 19 spots (#649 → #668)
2026-09-08
Rank Moved
Rank dropped 12 spots (#637 → #649)
2026-09-07
Rank Moved
Rank dropped 38 spots (#599 → #637)
2026-09-06
Rank Moved
Rank dropped 14 spots (#585 → #599)
2026-09-05
Rank Moved
Rank dropped 71 spots (#514 → #585)
2026-09-04
Rank Moved
Rank dropped 21 spots (#493 → #514)
2026-09-03
Rank Moved
Rank dropped 65 spots (#428 → #493)
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 511 spots (#939 → #428)
2026-09-02
HVTrust Changed
HVTrust up 20.5pts (39.5 → 60.0)
2026-09-01
Rank Moved
Rank dropped 40 spots (#899 → #939)
2026-08-31
Rank Moved
Rank dropped 69 spots (#830 → #899)
2026-08-31
Activity Score Changed
Activity score down 9pts (56 → 47)
2026-08-30
Rank Moved
Rank dropped 68 spots (#762 → #830)
2026-08-30
Activity Score Changed
Activity score down 8pts (63 → 56)
2026-08-29
Rank Moved
Rank dropped 50 spots (#712 → #762)
2026-08-28
Scorecard Added
OSSF Scorecard: 5.7/10
2026-08-28
Rank Moved
Rank rose 299 spots (#1011 → #712)
2026-08-28
HVTrust Changed
HVTrust up 19.6pts (23.6 → 43.2)
2026-08-27
Rank Moved
Rank dropped 21 spots (#990 → #1011)
2026-08-26
Rank Moved
Rank dropped 95 spots (#895 → #990)
2026-08-22
Rank Moved
Rank rose 10 spots (#892 → #882)
2026-08-19
Rank Moved
Rank rose 24 spots (#911 → #887)
2026-08-17
Rank Moved
Rank rose 11 spots (#921 → #910)
2026-08-16
Rank Moved
Rank dropped 27 spots (#894 → #921)
2026-08-13
Rank Moved
Rank dropped 16 spots (#882 → #898)
2026-08-12
Rank Moved
Rank rose 10 spots (#892 → #882)
2026-08-10
Rank Moved
Rank dropped 50 spots (#837 → #887)
2026-08-08
Newly Listed
First tracked at rank #830
GitHub → npm: @insforge/mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 60.7 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/insforge-insforge.svg)](https://hvtracker.net/agents/insforge-insforge)
HTML:
<a href="https://hvtracker.net/agents/insforge-insforge"><img src="https://hvtracker.net/badge/insforge-insforge.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.4 · Raw JSON