Genexus18MCP

GeneXus 18 MCP server for Claude, Cursor, and AI agents — read, edit, analyze KB objects (transactions, web panels, proc

MCP Servers C# Grade C Listed MIT
50.0/100
Rank #764 of 1320
Compare Genexus18MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-04 · 0d ago
Recent change
Rank +6

Is Genexus18MCP safe? Genexus18MCP scores 50.0/100 (Grade C), ranked #764 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.0/10; 1% of recent commits are signed; last pushed 2026-09-04. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 15 spots (#749 → #764)
2026-09-03
Rank Moved
Rank dropped 47 spots (#702 → #749)
2026-09-02
Rank Moved
Rank dropped 32 spots (#670 → #702)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.0/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
65.0
Activity sub-score · out of 100
#398

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 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-09-04 14:33 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
28
Forks
21
Last Push
2026-09-04
today
Commits (4 wk)
195
Downloads (7d)
HN mentions (30d)
Open Issues
0
Rank Change
▼15
was #749

Analysis

HVTrust Dimensions vs MCP Servers

50.0 / 100 · 67.0% confidence

Genexus18MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.6 / 25
3.1 above avg 9.5
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.6 above avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
11.9 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.8 above avg 12.2
AdoptionLog-scaled stars · package downloads
3.5 / 20
2.7 below avg 6.2

Activity Inputs

65.0 / 100
StarsRepository reach
8.8 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.2 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
4.0 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
1%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 7
SAST 0
Security-Policy 10
Signed-Releases 0
Token-Permissions 0
Vulnerabilities 0

Is Genexus18MCP safe?

Public trust evidence for Genexus18MCP 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 Genexus18MCP publish package provenance?
Yes. Genexus18MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Genexus18MCP have an OpenSSF Scorecard?
Genexus18MCP has an OpenSSF Scorecard score of 4.0/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 Genexus18MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Genexus18MCP use?
Genexus18MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Genexus18MCP's commits signed?
1% of the last 100 commits to Genexus18MCP 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
medium confidence
Implemented
Genexus18MCP 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

Maintain Genexus18MCP?

For maintainers

HVTrust scores Genexus18MCP 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
Rank 15Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 15 spots (#749 → #764)
2026-09-03
Rank Moved
Rank dropped 47 spots (#702 → #749)
2026-09-02
Rank Moved
Rank dropped 32 spots (#670 → #702)
2026-09-01
Rank Moved
Rank dropped 26 spots (#644 → #670)
2026-08-31
Rank Moved
Rank dropped 33 spots (#611 → #644)
2026-08-29
Rank Moved
Rank dropped 38 spots (#566 → #604)
2026-08-28
Rank Moved
Rank dropped 13 spots (#553 → #566)
2026-08-27
Rank Moved
Rank dropped 15 spots (#538 → #553)
2026-08-26
Scorecard Added
OSSF Scorecard: 4.0/10
2026-08-26
Grade Changed
Trust grade D → C
2026-08-26
Rank Moved
Rank rose 13 spots (#551 → #538)
2026-08-26
HVTrust Changed
HVTrust up 5.7pts (44.4 → 50.1)
2026-08-24
Rank Moved
Rank dropped 11 spots (#537 → #548)
2026-08-22
Rank Moved
Rank rose 11 spots (#546 → #535)
2026-08-17
Rank Moved
Rank rose 12 spots (#551 → #539)
2026-08-16
Rank Moved
Rank dropped 10 spots (#541 → #551)
2026-08-13
Rank Moved
Rank dropped 11 spots (#529 → #540)
2026-08-10
Rank Moved
Rank dropped 17 spots (#521 → #538)
2026-08-08
Newly Listed
First tracked at rank #525

Embed Badge Badge guide for maintainers →

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