Is Octen MCP safe to use?

Octen MCP has an HVTrust score of 68.7/100 (Grade B), ranked #381 of 1371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Octen MCP?

Octen MCP scores 68.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 21 GitHub stars and is categorized under MCP Servers.

Octen MCP

Repository

Website

MCP server for Octen — real-time web search, broad multi-angle search, news, URL extraction, and image/video search for Claude Code, Cursor, and any MCP client

MCP Servers JavaScript Listed MIT

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

OSSF Scorecard 4.1 / 10

Provenance Attested

Signed commits 42%

Last push 3d ago

Advisories None known

Compare Octen MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Octen MCP scores 68.7/100 (Grade B), ranked #381 of 1371 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 4.1/10; 42% of recent commits are signed; no published advisory affects its latest release (octen-mcp); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →

How Octen MCP 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.

Raise the OSSF Scorecard from 4.1 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Dependency-Update-Tool 0 +10.3 → 79.0 B · #90 of 781
Sign every commit42% signed today +2.9 → 71.6 B · #191 of 781

Already done? Suggest a correction Add the trust badge

Chain of custody

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

Source Partly signed

github.com/Octen-Team/octen-mcp, MIT, last pushed 2026-10-08. 42% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 4.1/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies3
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0
Published packages Linked and attested
- npm octen-mcp Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: octen-mcp 0.6.0. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-08-26 OSSF Scorecard: 3.9/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 Octen MCP’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 Octen MCP compares in MCP Servers

#226 Podman MCP Server 68.8 +0.1
#227 Robinhood Portfolio Research 68.7 ±0
#228 Octen MCP 68.7 this agent
#229 Upstash MCP Server 68.7 ±0
#230 Excalidraw Architect 68.6 −0.1

Bars show each HVTrust score; the tick marks Octen MCP’s 68.7.

Where the 68.7 comes from

HVTrust dimensions vs the MCP Servers average

68.7 / 100 · 100.0% confidence

Octen MCP MCP Servers average (781 agents)

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

14.7 / 25

4.3 above avg 10.4

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.5 above avg 13.5

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.4 / 20

1.2 above avg 12.2

AdoptionLog-scaled stars · package downloads

5.9 / 20

1.5 below avg 7.4

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-10-09

Rank Moved

Rank dropped 12 spots (#373 → #385)

2026-10-08

Rank Moved

Rank dropped 50 spots (#323 → #373)

2026-10-07

Rank Moved

Rank rose 54 spots (#377 → #323)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.1/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.

Compare with another agent Get email alerts for Octen MCP View MCP Servers Report missing data

43.8

Activity sub-score · out of 100

#228

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 B 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-09-29 2026-10-11

Activity & Reach

Stars

Forks

Last Push

2026-10-08

3 days ago

Commits (4 wk)

Downloads (7d)

108

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲3

was #384

Analysis

Activity Inputs

43.8 / 100

StarsRepository reach

8.1 / 30

FreshnessLast push recency

24.6 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

1.4 / 20

Common questions about Octen MCP

Octen MCP 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 Octen MCP publish package provenance?

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

Does Octen MCP have an OpenSSF Scorecard?

Octen MCP has an OpenSSF Scorecard score of 4.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 Octen MCP actively maintained?

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

What license does Octen MCP use?

Octen MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Octen MCP's commits signed?

42% of the last 100 commits to Octen MCP 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

Octen MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

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

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 Octen MCP'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-09-16

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-16

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

Maintain Octen MCP?

For maintainers

HVTrust scores Octen MCP 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-10-09

Rank Moved

Rank dropped 12 spots (#373 → #385)

2026-10-08

Rank Moved

Rank dropped 50 spots (#323 → #373)

2026-10-07

Rank Moved

Rank rose 54 spots (#377 → #323)

2026-10-01

Rank Moved

Rank dropped 62 spots (#297 → #359)

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

2026-09-23

Rank Moved

Rank rose 653 spots (#962 → #309)

2026-09-23

HVTrust Changed

HVTrust up 45.4pts (25.6 → 71.0)

2026-09-22

Newly Listed

First tracked at rank #962

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Rank Moved

Rank dropped 13 spots (#295 → #308)

2026-09-16

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-16

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-15

Rank Moved

Rank rose 17 spots (#306 → #289)

2026-09-14

Rank Moved

Rank dropped 10 spots (#296 → #306)

2026-09-10

Rank Moved

Rank dropped 24 spots (#262 → #286)

2026-09-08

Grade Changed

Trust grade D → B

2026-09-08

Rank Moved

Rank rose 702 spots (#959 → #257)

2026-09-08

HVTrust Changed

HVTrust up 25.4pts (47.1 → 72.5)

2026-09-07

Rank Moved

Rank dropped 22 spots (#937 → #959)

2026-09-06

Rank Moved

Rank dropped 16 spots (#921 → #937)

2026-09-05

Rank Moved

Rank dropped 51 spots (#870 → #921)

2026-09-04

Rank Moved

Rank dropped 29 spots (#841 → #870)

2026-09-03

Rank Moved

Rank dropped 43 spots (#798 → #841)

2026-09-02

Rank Moved

Rank dropped 42 spots (#756 → #798)

2026-09-01

Rank Moved

Rank dropped 15 spots (#741 → #756)

2026-08-31

Rank Moved

Rank dropped 28 spots (#713 → #741)

2026-08-30

Rank Moved

Rank dropped 26 spots (#687 → #713)

2026-08-29

Rank Moved

Rank dropped 51 spots (#636 → #687)

2026-08-28

Rank Moved

Rank dropped 22 spots (#614 → #636)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.9/10

2026-08-26

HVTrust Changed

HVTrust up 5.1pts (41.1 → 46.2)

2026-08-16

Rank Moved

Rank dropped 10 spots (#595 → #605)

2026-08-14

Rank Moved

Rank rose 13 spots (#609 → #596)

2026-08-10

Rank Moved

Rank dropped 24 spots (#580 → #604)

2026-08-08

Newly Listed

First tracked at rank #581

GitHub → Website → npm: octen-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Octen MCP

How Octen MCP could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Octen MCP compares in MCP Servers

Where the 68.7 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Octen MCP

AI agent surface

Maintain Octen MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers