File Edit Check MCP Server

Created By
punkpeyea year ago
MCP server that enforces pre-read checks and detailed commit documentation
Overview

what is File Edit Check MCP Server?

File Edit Check MCP Server is a server that enforces pre-read checks and detailed commit documentation to prevent blind modifications to files.

how to use File Edit Check MCP Server?

To use the server, install it via npm, build the project, and add it to your MCP settings file to enforce pre-read checks before file modifications.

key features of File Edit Check MCP Server?

  • Enforces pre-read verification before file modifications
  • Prevents blind writes and diffs
  • Provides detailed commit message guidance
  • TypeScript implementation with proper error handling

use cases of File Edit Check MCP Server?

  1. Ensuring that files are read before any modifications are made.
  2. Maintaining detailed commit documentation for better project tracking.
  3. Preventing accidental overwrites in collaborative environments.

FAQ from File Edit Check MCP Server?

  • What is the purpose of pre-read checks?

Pre-read checks ensure that users are aware of the current state of a file before making any changes, preventing blind modifications.

  • Is this server suitable for collaborative projects?

Yes! It is designed to enhance collaboration by enforcing checks and documentation.

  • How do I install the server?

You can install it using npm with the command npm install followed by npm run build.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
punkpeye
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago