Local MCP server for verifiable DOCX redline history and fail-closed tracked-change edits
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"veqtor-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<!-- SPDX-License-Identifier: Apache-2.0 --> # Veqtor MCP [Website](https://veqtor.pro) · [Demo](https://veqtor.pro/demo) · [Documentation](https://veqtor.pro/docs) · [PyPI](https://pypi.org/project/veqtor-mcp/) · [GitHub Releases](https://github.com/JohnDeer-ai/veqtor-mcp/releases) > **Public technical Alpha:** a local MCP server for verifiable DOCX negotiation > history and fail-closed tracked-change edits. Supported on macOS and Linux > with Python 3.12-3.14. Veqtor gives MCP-compatible AI clients deterministic tools to inspect a mechanical accepted/current projection of contract wording, read redlines, verify quotations, dry-run complete counterproposal batches, create a new DOCX with real tracked changes, and keep re-checkable local provenance. The model remains the legal-reasoning layer; Veqtor handles document facts and writes. Veqtor is not legal advice, a generic Word editor, a hosted service, or a tamper-evident audit system. Review the [known limitations](https://github.com/JohnDeer-ai/veqtor-mcp/blob/main/KNOWN_LIMITATIONS.md) before using it on a real matter. This source tree is the release candidate for package `0.3.0` and advertises MCP contract `veqtor.mcp.v0.3`. Source, CI, or a candidate artifact is not publication; only matching public PyPI and immutable GitHub Release entries establish that the version is installable. Before installing, check both the generic [PyPI project](https://pypi.org/project/veqtor-mcp/) and the [GitHub Releases list](https://github.com/JohnDeer-ai/veqtor-mcp/releases), then select one exact version for every command below: | Official state | Replace `X.Y.Z` with | |---|---| | Both sources expose `0.3.0`, and the GitHub release contains the complete verified asset set | `0.3.0` | | Otherwise | `0.1.2` | Do not run the placeholder literally or mix versions within one installation. ## Claude Desktop Extension status `veqtor-mcp-0.3.0-macos.mcpb` is an official public download only if it appears inside the verifie…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.