Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Octen-Team/octen-mcp

NPM · OCTEN-MCP

URL to LLM-ready markdown — plus per-page category, page_structure, and query-driven highlights.

Available components

−1 this week 93 Trust /100

Last scanned (2 hours ago)

Scores higher than 96% of npm servers

Category Web Scraping

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Octen-Team/octen-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 6 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 264 tokens (~264/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −2
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.87 functional
  • 31 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 23 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified ▼ functional
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 17 Oct 26 +3
    • Stability: 0.80 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/octen-mcp@0.1.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Octen-Team/octen-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Octen-Team/octen-mcp/.github/workflows/publish.yml@refs/tags/v0.1.5
Rekor log index 1583236873
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:434a96def11a74cbb34a1056e9d8a2b5168e177343433de4e254a46b5915435817459e76d4e865acaf0b32353da770cea9b3cd5526ae27d27a82a9c4d

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~264 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
extract ~264

Fetch one or more URLs and return LLM-ready content from Octen. Unique to Octen: pass a `query` to get the most relevant highlights per page instead of the full body; every result includes a `category` (topical) and `page_structure` (typology) classification. Bare hosts like 'octen.ai' are auto-normalized to https. Cached when fresh.

NameTypeReqDescription
formatstring–Output format. Default markdown.
include_audioboolean–Return audio URLs found on each page.
include_faviconboolean–Return each page's favicon URL.
include_imagesboolean–Return image URLs found on each page.
include_videosboolean–Return video URLs found on each page.
max_age_secondsinteger–Maximum age of cached content in seconds. Default 24h. Lower this for time-sensitive pages (news / prices).
querystring–Optional intent-focused keywords. When set, each result returns `highlights` (most relevant snippets, ranked) instead of `full_content`.
timeoutinteger–Per-URL timeout in seconds (1-60).
urlsarrayyesURLs to extract. 1-20 per call. Bare hosts ok.

No output schema declared.

No examples provided.

Install

How do I install the io.github.Octen-Team/octen-mcp server?

io.github.Octen-Team/octen-mcp runs locally as an npm package, launched with npx -y octen-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · octen-mcp

# add to Claude Code
claude mcp add octen-team-octen-mcp -- npx -y octen-mcp
Common questions

What is the io.github.Octen-Team/octen-mcp server?

io.github.Octen-Team/octen-mcp is listed in the public MCP registry as io.github.Octen-Team/octen-mcp. URL to LLM-ready markdown, plus per-page category, page_structure, and query-driven highlights. This page covers its npm package (octen-mcp).

Is the io.github.Octen-Team/octen-mcp server safe to use?

io.github.Octen-Team/octen-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Octen-Team/octen-mcp server expose?

io.github.Octen-Team/octen-mcp exposes 1 tool: extract. Their descriptions and schemas cost roughly 264 tokens of context every time the server is loaded.

Is the io.github.Octen-Team/octen-mcp server still maintained?

io.github.Octen-Team/octen-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Octen-Team/octen-mcp server under?

io.github.Octen-Team/octen-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.