updated 2026-11-10 04:07 UTC

MCP Server Infranodus

Repository

The official InfraNodus MCP server

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 2.9 / 10
Provenance None
Signed commits 10%
Last push yesterday
Compare MCP Server Infranodus

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Server Infranodus scores 49.8/100 (Grade D), ranked #1012 of 1374 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 2.9/10; 10% of recent commits are signed; last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Infranodus 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 MCP Server Infranodus 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/infranodus/mcp-server-infranodus, MIT, last pushed 2026-11-09. 10% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages None

    No registry package. MCP Server Infranodus 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: 2.9/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 MCP Server Infranodus’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 MCP Server Infranodus compares in MCP Servers

  1. #570 Storeshots MCP 50.0 +0.2
  2. #571 Markdownify MCP 49.9 +0.1
  3. #572 MCP Server Infranodus 49.8 this agent
  4. #573 Zotero MCP (kujenga) 49.7 −0.1
  5. #574 Open SEO MCP 49.7 −0.1

Bars show each HVTrust score; the tick marks MCP Server Infranodus’s 49.8.

Where the 49.8 comes from

HVTrust dimensions vs the MCP Servers average

49.8 / 100 · 100.0% confidence

MCP Server Infranodus MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.1 / 25
6.7 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
1.3 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
6.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
4.9 / 20
2.7 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-07
Rank Moved
Rank rose 10 spots (#1032 → #1022)
2026-11-05
Rank Moved
Rank rose 58 spots (#1097 → #1039)
2026-11-04
Rank Moved
Rank rose 22 spots (#1119 → #1097)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/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
View MCP Servers Report missing data
64.0
Activity sub-score · out of 100
#572
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-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
105
Forks
28
Last Push
2026-11-09
yesterday
Commits (4 wk)
39
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #1012

Analysis

Activity Inputs

64.0 / 100
StarsRepository reach
12.2 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.0 / 25
CommunityFork signal
6.8 / 20

Common questions about MCP Server Infranodus

Public trust evidence for MCP Server Infranodus 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 MCP Server Infranodus publish package provenance?
No published build provenance is currently detected for MCP Server Infranodus. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Server Infranodus have an OpenSSF Scorecard?
MCP Server Infranodus has an OpenSSF Scorecard score of 2.9/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 MCP Server Infranodus actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does MCP Server Infranodus use?
MCP Server Infranodus ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Server Infranodus's commits signed?
10% of the last 100 commits to MCP Server Infranodus 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
MCP Server Infranodus 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
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 MCP Server Infranodus'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-10-21
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Server Infranodus?

For maintainers

HVTrust scores MCP Server Infranodus 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 34Score 5HVTrust 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1
2026-11-07
Rank Moved
Rank rose 10 spots (#1032 → #1022)
2026-11-05
Rank Moved
Rank rose 58 spots (#1097 → #1039)
2026-11-04
Rank Moved
Rank rose 22 spots (#1119 → #1097)
2026-11-04
Activity Score Changed
Activity score up 6pts (56 → 62)
2026-10-31
Rank Moved
Rank dropped 27 spots (#1094 → #1121)
2026-10-30
Rank Moved
Rank rose 46 spots (#1140 → #1094)
2026-10-21
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-21
Rank Moved
Rank rose 25 spots (#1157 → #1132)
2026-10-21
Activity Score Changed
Activity score up 8pts (43 → 51)
2026-10-20
Rank Moved
Rank dropped 26 spots (#1131 → #1157)
2026-10-20
Activity Score Changed
Activity score down 6pts (50 → 43)
2026-10-16
Rank Moved
Rank rose 18 spots (#1146 → #1128)
2026-10-09
Rank Moved
Rank dropped 12 spots (#1106 → #1118)
2026-09-29
Activity Score Changed
Activity score down 8pts (56 → 49)
2026-09-28
Rank Moved
Rank dropped 29 spots (#978 → #1007)
2026-09-25
Rank Moved
Rank dropped 11 spots (#964 → #975)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank dropped 434 spots (#528 → #962)
2026-09-23
HVTrust Changed
HVTrust up 9.9pts (39.1 → 49.0)
2026-09-22
Newly Listed
First tracked at rank #528
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank rose 27 spots (#968 → #941)
2026-09-12
Rank Moved
Rank dropped 10 spots (#947 → #957)
2026-09-11
Rank Moved
Rank dropped 11 spots (#936 → #947)
2026-09-10
Rank Moved
Rank rose 17 spots (#953 → #936)
2026-09-08
Rank Moved
Rank dropped 18 spots (#927 → #945)
2026-09-07
Rank Moved
Rank dropped 39 spots (#888 → #927)
2026-09-06
Rank Moved
Rank dropped 13 spots (#875 → #888)
2026-09-05
Rank Moved
Rank dropped 59 spots (#816 → #875)
2026-09-04
Rank Moved
Rank dropped 34 spots (#782 → #816)
2026-09-03
Rank Moved
Rank dropped 55 spots (#727 → #782)
2026-09-02
Rank Moved
Rank dropped 38 spots (#689 → #727)
2026-09-01
Rank Moved
Rank dropped 29 spots (#660 → #689)
2026-08-31
Rank Moved
Rank dropped 39 spots (#621 → #660)
2026-08-30
Rank Moved
Rank rose 18 spots (#639 → #621)
2026-08-30
Activity Score Changed
Activity score up 5pts (58 → 63)
2026-08-29
Rank Moved
Rank dropped 40 spots (#599 → #639)
2026-08-28
Rank Moved
Rank dropped 11 spots (#588 → #599)
2026-08-27
Rank Moved
Rank dropped 16 spots (#572 → #588)
2026-08-26
Scorecard Added
OSSF Scorecard: 2.9/10
2026-08-26
Rank Moved
Rank rose 444 spots (#1016 → #572)
2026-08-26
HVTrust Changed
HVTrust up 26.4pts (21.4 → 47.8)
2026-08-24
Rank Moved
Rank dropped 20 spots (#997 → #1017)
2026-08-22
Rank Moved
Rank rose 22 spots (#1024 → #1002)
2026-08-17
Rank Moved
Rank rose 11 spots (#1028 → #1017)
2026-08-16
Rank Moved
Rank dropped 30 spots (#998 → #1028)
GitHub →

Embed Badge Badge guide for maintainers →

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