hexvero
NPM · HEXVERO
Electron release diff for security review: what changed in IPC, contextBridge, windows and hosts.
Available components
Last scanned (1 hour ago)
Scores higher than 38% of npm servers
Category Security
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 Security48
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to maximilianfeix/hexvero). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2021 tokens (~126/item across 16 items; 16 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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
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.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 0
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.9.8 → 0.11.1 functional
- Package version: 0.9.8 → 0.10.0 functional
- Package version: 0.9.8 → 0.9.9 functional
- 17 Oct 26 +1
- Stability: 0.03 → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Schema quality: 1835 → 2021 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.8.0 → 0.9.8 functional
- Package version: 0.8.0 → 0.9.6 functional
- Package version: 0.8.0 → 0.9.5 functional
- Package version: 0.8.0 → 0.9.4 functional
- Package version: 0.8.0 → 0.9.2 functional
- Package version: 0.8.0 → 0.9.1 functional
- Package version: 0.8.0 → 0.9.0 functional
- 16 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.7.5 → 0.8.0 functional
- 15 Oct 26 +42
- Injection markers: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → 0.86 ▲ functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 75 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- Package version: 0.6.0 → 0.7.5 functional
- Package version: 0.6.0 → 0.7.2 functional
- Package version: 0.6.0 → 0.6.2 functional
- 14 Oct 26 39
First indexed and scored.
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 19 Oct 2026 · Analysed npm/hexvero@0.11.1
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 | maximilianfeix/hexvero |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/maximilianfeix/hexvero/.github/workflows/release.yml@refs/tags/v0.11.1 |
| Rekor log index | 3315046877 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1cec327ef29fd3bb9b4953e378a3242ed60ac9e18a515f04c085cdd5ced9dfaab64da269a691f4c3ee804f8fb8ba2262cdcaf07dffd5a52916203658c |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
hexvero_analyze Analyze target ~265
Run the built-in analyzer for the target's format (ELF/PE/Mach-O, Go, .NET, WASM, EVM, SQLite, plist, APK, ZIP, Electron ASAR, JavaScript apps, source maps, HAR). Returns a summary, findings with confidence, limitations, a compact overview and the collections available for paging. Large JavaScript apps are read in batches: when `complete` is false, `coverage` says how many files are unread and every list covers the scanned part only; call again with scan to read more.
| Name | Type | Req | Description |
|---|---|---|---|
| batch | integer | – | JavaScript apps only: files per batch (default 5000) |
| detail | string | – | overview size: brief (default) lists only counts, full adds samples of every list |
| fresh | boolean | – | JavaScript apps only: discard the stored scan first; combines with scan |
| include | array | – | JavaScript apps only: read the unread files under these paths (prefix or * pattern) |
| scan | string | – | JavaScript apps only: continue = read the next batch of unread files, all = read every unread file, fresh = discard the stored scan and start again |
| targetId | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_bytes Read bytes ~59
Read a bounded window (max 64 KiB) of the target as hex plus an ASCII gutter.
| Name | Type | Req | Description |
|---|---|---|---|
| length | integer | yes | – |
| offset | integer | yes | – |
| targetId | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_call_graph Call graph ~159
Bounded call-graph neighborhood around a function (callers, callees or both, by depth and node count), or the shortest call path from root to goal. One engine run per target, cached; levels state what was cut.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Default callees |
| goal | string | – | With goal: shortest path root → goal in the given direction instead |
| maxDepth | integer | – | Hops from root (default 2) |
| maxNodes | integer | – | Default 150 |
| provider | string | yes | – |
| root | string | yes | Function name or address to start from |
| targetId | string | yes | Target id returned by hexvero_open |
| timeoutMs | integer | – | – |
No output schema declared.
No examples provided.
hexvero_check Check release policy ~155
Apply a release policy (inline JSON or file) to two builds, as `hexvero check`: status pass, fail or incomplete, and findings paged by offset. Reads a baseline, never writes one.
| Name | Type | Req | Description |
|---|---|---|---|
| baselinePath | string | – | Absolute path of a baseline file |
| format | string | – | Default json |
| limit | integer | – | Findings (default 100) |
| offset | integer | – | First finding (default 0) |
| policy | object | – | Policy JSON object |
| policyPath | string | – | Or: absolute path of a policy file |
| targetA | string | yes | Target id returned by hexvero_open |
| targetB | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_close Close target ~32
Release a target and its retained analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| targetId | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_collection Page a collection ~183
Page through one named list from the analysis, e.g. symbols, imports, exports, sections, libraries, types, methods, pinvokes, selectors, instructions, tables, columns, requests, endpoints, permissions, components, modules, edges, ipcChannels, findings. Use hexvero_analyze to see which exist.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | yes | – |
| limit | integer | – | Items per page (default 100) |
| maxBytes | integer | – | Hard upper bound for the serialized page in bytes (default 262144). A page reports next, bytes and, for an item cut to fit, itemTruncated + itemBytes |
| offset | integer | – | First item index (default 0) |
| targetId | string | yes | Target id returned by hexvero_open |
| text | string | – | Case-insensitive substring filter on each item |
No output schema declared.
No examples provided.
hexvero_compare Compare collections ~265
Diff one collection between two targets: added, removed, changed (with the fields that differ) and unchanged items, matched by key (auto-detected: name, channel, id, path, url, type+name … or pass key, a+b for composites). States completeness; unknown items are neither added nor removed. Each list pages on its own (list + offset). Without collection: counts per shared collection, to pick one.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | – | – |
| ignore | array | – | Fields to exclude from change detection, in addition to the position rule |
| key | string | – | Item field used as identity (default: name, then JSON) |
| limit | integer | – | Items per list in this answer (default 50 added/removed, 25 changed) |
| list | string | – | Page only this list; offset applies to it (each list has its own next) |
| offset | integer | – | With list: that list's next |
| strict | boolean | – | Count every difference. Default false: address fields of native symbols/sections that only moved are reported as relocated, with samples |
| targetA | string | yes | Target id returned by hexvero_open |
| targetB | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_export Export analysis ~81
Write the complete analysis as JSON to a file and return its path and size. Use this instead of paging when you need everything.
| Name | Type | Req | Description |
|---|---|---|---|
| overwrite | boolean | – | Replace an existing file (default false) |
| path | string | yes | Absolute destination file path; refused when the file exists |
| targetId | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_list List targets ~16
List targets opened in this session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hexvero_open Open target ~47
Register a local file or directory for analysis. Returns its id, size, hash and detected format. Ids are stable per content.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path |
No output schema declared.
No examples provided.
hexvero_provider_run Run provider operation ~129
Run one engine operation on a target: functions, disassemble, decompile, strings, imports, xrefs (references to an address), callers, callees, callgraph or search (names + strings). Output is bounded and cached.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Function address or symbol for disassemble/decompile/xrefs/callers/callees |
| operation | string | yes | – |
| provider | string | yes | – |
| targetId | string | yes | Target id returned by hexvero_open |
| text | string | – | Needle for search |
| timeoutMs | integer | – | – |
No output schema declared.
No examples provided.
hexvero_providers Providers ~31
Detect optional external engines (radare2/rizin, Ghidra) and the operations each supports.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
hexvero_recover Recover sources ~99
Write recoverable sources into a new directory: the modules of a webpack/Rspack/browserify/esbuild bundle (one file each plus hexvero-bundle.json with requires/exports), or the original files embedded in a source map (sourcesContent). No engine needed; nothing is executed.
| Name | Type | Req | Description |
|---|---|---|---|
| outputDir | string | yes | Absent or empty directory to write into |
| targetId | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_sourcemap Resolve source map position ~63
Map a generated line/column of a source map target back to its original source, line, column and name.
| Name | Type | Req | Description |
|---|---|---|---|
| column | integer | yes | – |
| line | integer | yes | – |
| targetId | string | yes | Target id returned by hexvero_open |
No output schema declared.
No examples provided.
hexvero_strings Strings ~172
Printable ASCII (and optional UTF-16LE) strings with offsets and tags (url, path, email, ip, format, secret-ish, base64-ish).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items per page (default 100) |
| maxBytes | integer | – | Hard upper bound for the serialized page in bytes (default 262144). A page reports next, bytes and, for an item cut to fit, itemTruncated + itemBytes |
| minLength | integer | – | – |
| offset | integer | – | First item index (default 0) |
| tag | string | – | Only strings carrying this tag |
| targetId | string | yes | Target id returned by hexvero_open |
| text | string | – | Case-insensitive substring filter on each item |
| utf16 | boolean | – | – |
No output schema declared.
No examples provided.
hexvero_unknowns Unknowns ledger ~153
Record a material question the investigation could not answer (with what was already checked), list open or resolved unknowns, or resolve one. Unknowns are exported with the analysis so reports never silently drop them.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| checked | array | – | record: collections, offsets or tools already examined |
| id | string | – | resolve: the unknown's id |
| limit | integer | – | – |
| offset | integer | – | – |
| question | string | – | record: the open question |
| resolution | string | – | resolve: what settled it, with evidence |
| status | string | – | list: filter by status |
| targetId | string | – | Target the question belongs to |
No output schema declared.
No examples provided.
How do I install the hexvero MCP server?
hexvero runs locally as an npm package, launched with npx -y hexvero. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · hexvero
claude mcp add maximilianfeix-hexvero -- npx -y hexvero
What is the hexvero MCP server?
hexvero is an MCP server listed in the public MCP registry as io.github.maximilianfeix/hexvero. Electron release diff for security review: what changed in IPC, contextBridge, windows and hosts. This page covers its npm package (hexvero).
Is the hexvero MCP server safe to use?
hexvero scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 19 October 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 hexvero MCP server expose?
hexvero exposes 16 tools: hexvero_open, hexvero_list, hexvero_close, hexvero_analyze, hexvero_collection, and 11 more. Their descriptions and schemas cost roughly 1,909 tokens of context every time the server is loaded.
Is the hexvero MCP server still maintained?
hexvero is still listed as active in the MCP registry. We last reached this channel on 19 October 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 hexvero MCP server under?
hexvero declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.