Is Cap Js MCP Server safe to use?

Cap Js MCP Server has an HVTrust score of 87.0/100 (Grade A), ranked #55 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Cap Js MCP Server?

Cap Js MCP Server scores 87.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 112 GitHub stars and is categorized under MCP Servers.

Cap Js MCP Server

cap-js/mcp-server

MCP server for AI-assisted development of CAP applications

MCP Servers JavaScript Listed Apache-2.0

Is Cap Js MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 7.6 / 10

Provenance Attested

Signed commits 74%

Last push yesterday

Compare Cap Js MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Cap Js MCP Server scores 87.0/100 (Grade A), ranked #55 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.6/10; 74% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Cap Js MCP Server compares in MCP Servers

Bars show each HVTrust score; the tick marks Cap Js MCP Server’s 87.0.

Where the 87.0 comes from

HVTrust dimensions vs the MCP Servers average

87.0 / 100 · 100.0% confidence

Cap Js MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

20.7 / 25

10.4 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

15.0 / 17

2.8 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

17.0 / 20

4.9 above avg 12.1

AdoptionLog-scaled stars · package downloads

11.2 / 20

4.0 above avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Keep signals current Trust posture is already in a healthy range. The main job is to keep provenance, maintenance, and public evidence fresh.

Compare with another agent Get email alerts for Cap Js MCP Server View MCP Servers Report missing data

59.1

Activity sub-score · out of 100

#15

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 A 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

112

Forks

Last Push

2026-09-25

yesterday

Commits (4 wk)

Downloads (7d)

48,847

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #55

Analysis

Activity Inputs

59.1 / 100

StarsRepository reach

12.3 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

15.9 / 25

CommunityFork signal

5.9 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.6 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

74%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 10

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 8

SAST 8

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 8

Common questions about Cap Js MCP Server

Public supply-chain signals for Cap Js MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Cap Js MCP Server carries less obvious unverified-evidence risk than projects with thin signals.

Does Cap Js MCP Server publish package provenance?

Yes. Cap Js MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Cap Js MCP Server have an OpenSSF Scorecard?

Cap Js MCP Server has an OpenSSF Scorecard score of 7.6/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 Cap Js MCP Server actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Cap Js MCP Server use?

Cap Js MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Cap Js MCP Server's commits signed?

73% of the last 100 commits to Cap Js MCP Server 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

Cap Js MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

medium confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

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 Cap Js MCP Server'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

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

Maintain Cap Js MCP Server?

For maintainers

HVTrust scores Cap Js MCP Server 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

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 586 spots (#642 → #56)

2026-09-23

HVTrust Changed

HVTrust up 54.4pts (32.4 → 86.8)

2026-09-22

Newly Listed

First tracked at rank #642

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank rose 30 spots (#91 → #61)

2026-09-10

Rank Moved

Rank rose 30 spots (#125 → #95)

2026-09-05

Grade Changed

Trust grade C → A

2026-09-05

Rank Moved

Rank rose 625 spots (#735 → #110)

2026-09-05

HVTrust Changed

HVTrust up 29.5pts (51.7 → 81.2)

2026-09-04

Rank Moved

Rank dropped 25 spots (#710 → #735)

2026-09-03

Rank Moved

Rank dropped 34 spots (#676 → #710)

2026-09-02

Grade Changed

Trust grade A → C

2026-09-02

Rank Moved

Rank dropped 577 spots (#99 → #676)

2026-09-02

HVTrust Changed

HVTrust down 29.0pts (80.2 → 51.2)

2026-08-31

Grade Changed

Trust grade C → A

2026-08-31

Rank Moved

Rank rose 498 spots (#593 → #95)

2026-08-31

HVTrust Changed

HVTrust up 29.1pts (51.1 → 80.2)

2026-08-30

Grade Changed

Trust grade A → C

2026-08-30

Rank Moved

Rank dropped 505 spots (#88 → #593)

2026-08-30

HVTrust Changed

HVTrust down 29.5pts (80.6 → 51.1)

2026-08-29

Scorecard Added

OSSF Scorecard: 6.2/10

2026-08-29

Grade Changed

Trust grade B → A

2026-08-29

Rank Moved

Rank rose 124 spots (#212 → #88)

2026-08-29

HVTrust Changed

HVTrust up 13.0pts (67.6 → 80.6)

2026-08-27

Rank Moved

Rank dropped 11 spots (#198 → #209)

2026-08-26

Rank Moved

Rank dropped 29 spots (#169 → #198)

2026-08-24

Grade Changed

Trust grade D → B

2026-08-24

Rank Moved

Rank rose 395 spots (#562 → #167)

2026-08-24

HVTrust Changed

HVTrust up 25.3pts (43.4 → 68.7)

2026-08-22

Grade Changed

Trust grade B → D

2026-08-22

Rank Moved

Rank dropped 394 spots (#170 → #564)

2026-08-22

HVTrust Changed

HVTrust down 25.2pts (68.7 → 43.5)

2026-08-21

Rank Moved

Rank rose 24 spots (#194 → #170)

2026-08-17

Rank Moved

Rank rose 11 spots (#190 → #179)

2026-08-16

Rank Moved

Rank dropped 14 spots (#176 → #190)

2026-08-13

Grade Changed

Trust grade D → B

2026-08-13

Rank Moved

Rank rose 394 spots (#566 → #172)

2026-08-13

HVTrust Changed

HVTrust up 25.0pts (42.9 → 67.9)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-12

Grade Changed

Trust grade B → D

2026-08-12

Rank Moved

Rank dropped 384 spots (#182 → #566)

2026-08-12

HVTrust Changed

HVTrust down 24.3pts (67.2 → 42.9)

2026-08-08

Newly Listed

First tracked at rank #555

GitHub → npm: @cap-js/mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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