MCP.Market

Hex Line MCP server

by levnikolaevich·io.github.levnikolaevich/hex-line-mcp·v1.31.0·565 stars
No reviews yet

Hash-verified file editing MCP server with token efficiency hook for AI coding agents.

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

565 stars

Reviews

Write one

Nobody has reviewed Hex Line yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Hex Line tools (9, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • bulk_replace

    Search-and-replace text across multiple files inside an explicit root path. Use for renames and refactors when the project scope is known.

  • changes

    Semantic diff against git ref (default: HEAD). Returns canonical status, summary, next_action, changed symbols, and graph-backed risk hints when available.

  • edit_file

    Apply hash-verified partial edits to one file. Batch ALL hunks for the same file into ONE call via the `edits` array -- separate sequential edit_file calls on one file go stale and conflict (the most common edit failure). Carry base_revision only for a genuinely later follow-up after the file changed. Anchors accept tag.N, a bare line number, or unique line content (auto-resolved); range_checksum

  • grep_search

    Search file contents with ripgrep. Default: summary-first discovery output; use `content` with `edit_ready=true` when you need verified edit hunks.

  • inspect_path

    Inspect a file or directory path. Files return compact metadata; directories return a gitignore-aware tree or pattern matches.

  • outline

    AST-based structural outline with hash anchors for direct edit_file usage. Supports JavaScript/TypeScript, Python, C#, and PHP code files plus markdown headings (.md/.mdx, fence-aware).

  • read_file

    Read file with progressive disclosure. Default: minimal plain partial read for discovery; enable edit-ready metadata explicitly when preparing a verified edit.

  • verify

    Check if held checksums are still valid without rereading. Use before delayed or mixed-tool follow-up edits; returns canonical status, next_action, and reread guidance.

  • write_filewrite action

    Create a new file or overwrite existing. Creates parent dirs. For existing files prefer edit_file (shows diff, verifies hashes).

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 11 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Hex Line compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 48,273 servers
Tools
9
the typical server has 7
Tools that change things
11%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
565
more than 95% of 28,534 servers

What its tools let an agent do: 7 read · 1 create · 1 change

Install Hex Line in Claude Code, Cursor or VS Code

Runs npx -y @levnikolaevich/hex-line-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add hex-line-mcp -- npx -y @levnikolaevich/hex-line-mcp
Add to Cursor

What the publisher says

From the Hex Line repository's README, as published. We do not edit it. Read it on GitHub

Claude-Codex Skills

Give your AI agent a clear finish line.

You ask for a fix and get a new abstraction. A review lists generic advice. The agent says “done,” but you still have to work out what it checked.

These skills give Claude Code and Codex a concrete way to finish the task: establish the intended outcome, work within scope, verify the result, and make remaining gaps explicit. Choose the skill for the problem in front of you.

Project page · Install · Full catalog

What changes in your workflow

  • A clearer target. Turn an idea, bug report, or incident into an outcome the agent can check.
  • Focused work. Reuse existing capabilities, fix the owning cause, and remove what the change makes obsolete.
  • A result you can assess. See the evidence, failed or unavailable checks, and remaining risks behind the verdict.
  • Control over consequential actions. Reviews report findings; implementation stays within the agreed scope; publication and deployment follow their authorization boundaries.

Choose a route

Start where you need help. Each skill works independently; a small fix does not require a full lifecycle or audit.

For a larger task, combine only the steps needed to resolve decisions and produce evidence. Supplied requirements, existing designs, and current tests are valid starting points. Implementation includes its own verification; a separate test-building or review skill is optional.

Install

For a feature or fix, start with implementation-suite. Replace it with another plugin from Choose a route for a different task.

Claude Code:

/plugin marketplace add levnikolaevich/claude-code-skills
/plugin install implementation-suite@levnikolaevich-skills-marketplace
/reload-plugins

Codex:

codex plugin marketplace add levnikolaevich/claude-code-skills
codex plugin add implementation-suite@levnikolaevich-skills-marketplace

Invoke a skill by its full name: /implementation-suite:ln-41-surgical-change-implementer in Claude Code or $ln-41-surgical-change-implementer in Codex, followed by your task. For example: “Fix the total calculation when an item has a discount. Preserve the current rounding rules.”

Lifecycle and plugins

Standalone skills for Claude Code and Codex, grouped by the work you need to do. Browse the outcomes below to find the right skill for your task.

1 Product discovery → 2 Architecture → 3 Delivery planning
 → 4 Implementation → 5 Quality assurance → 6 Delivery → 7 Operations
 ↑ Product feedback / architecture changes / operational remediation ↵

8 Skill maintenance supports the collection itself.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Hex Line: common questions

Is Hex Line MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Hex Line safety report
How do I install Hex Line?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Hex Line need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Hex Line maintained?
The last commit was 47 days ago (2026-09-16). The latest release is v1.31.0.
What can I use instead of Hex Line?
Servers from other publishers that do the same job: Token Optimizer MCP server.
How does Hex Line compare with other MCP servers?
safety score 92/100 (higher than 90% of 48,273 servers); tools 9 (the typical server has 7); tools that change things 11% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Hex Line

Same job from other publishers: the closest match first, then the best rated.

  • Token Optimizer
    Context-window optimization: caching, compression & smart file tools that cut tokens 60-90%.
    C

More from levnikolaevich →