SolveLang

io.github.saiidz由 GitHub 帳號 saiidz 發布v0.3.0更新於 Nov 21, 2026

Read-only MCP server for repository context: context packs, graph impact analysis, and validation.

已驗證Streamable HTTP可網頁執行知識與記憶開發者工具

概覽

AI 產生的概覽

唯讀的遠端 MCP 伺服器,為助理提供程式碼倉庫脈絡:脈絡包、圖譜影響分析與驗證。

可以做什麼
  • 規劃、打包、擷取並交接有界的倉庫脈絡,摘錄經持久化脈絡索引雜湊驗證
  • 搜尋並排序圖譜節點,追蹤相依、被相依、路徑與遞移影響並附說明
  • 找出循環、熱點、進入點與不可達候選,並產生結構化安全摘要
  • 分析 n8n 工作流程 JSON,產生 Markdown 或適合 CI 的 JSON 報告
  • 透過本機 solvec 執行檔驗證 .solve 檔案
適用情境
適合助理在修改程式碼前理解程式庫:蒐集聚焦的脈絡、評估變更會影響哪些部分,或檢查工作流程與 .solve 檔案。適合希望取得確定性、唯讀分析而非執行程式碼的團隊。
執行需求
遠端 Streamable HTTP 端點 mcp.solve-lang.com,需在 Authorization 標頭提供 bearer 權杖。端點限制請求大小為 4 MiB,並依來源位址限流(預設每 60 秒 60 次請求)。另有本機 npm 套件供以工作區為基礎的使用,需要 Node.js 20 以上版本並設定工作區根目錄。
安裝前請注意
bearer 權杖屬於機密,請勿放入共用設定。託管端點是獨立的驗證邊界,不會自動繼承本機工作區權限。分析僅為結構性:不執行程式碼、不安裝相依套件,也無法證明執行期可達性、關鍵性或安全性。README 指出邊緣限流與監控仍待補強。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 SolveLang,將其新增到工作區。
  2. 連接 Authorization token 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.saiidz%2Fsolvelang/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "solvelang": {
      "type": "http",
      "url": "https://mcp.solve-lang.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

SolveLang MCP Server

[mcptry]

Current verification — 2026-09-20

MCP v0.3.0 is published on npm and GitHub; main protection is enforced. Older checkpoints below are historical.

Local-first, read-only workflow, Solve Graph and Solve Context analysis for MCP clients such as Codex and Claude Code.

Distribution status

MCP @solvelang/[email protected] is published on npm and GitHub, verified on 2026-09-20. It distributes the tagged release source; later main changes require separate distribution. Managed-workspace marketplace installation and public Plugin Directory listing remain unverified. v0.2.0 is historical.

That means:

  • npx --yes @solvelang/[email protected] uses the historical package line;
  • the current source tree must not be assumed to match the old v0.2.0 artifact;
  • source-checkout instructions below are the correct way to evaluate current-main capabilities;
  • repository packing/consumer tests prove release readiness, not external publication;
  • verify npm/package registry or marketplace records before claiming current-main behavior is publicly distributed there.

Published package usage

Node.js 20 or newer is required. For the published v0.3.0 line:

bash
SOLVELANG_WORKSPACE_ROOT=/absolute/path/to/project \  npx --yes @solvelang/[email protected]

Call solvelang_capabilities / MCP list-tools to inspect the exact tools exposed by the installed version. Do not infer current-main tools from this README when using an older published package.

Current source usage

To run the repository version:

bash
git clone https://github.com/saiidz/solvelang.gitcd solvelang/packages/mcp-servernpm cinpm run buildSOLVELANG_WORKSPACE_ROOT=/absolute/path/to/project node dist/src/index.js

For .solve validation, make solvec available on PATH or set:

bash
SOLVELANG_SOLVEC=/absolute/path/to/solvec \SOLVELANG_WORKSPACE_ROOT=/absolute/path/to/project \node dist/src/index.js

Current repository tool families

Workflow / n8n

  • solvelang_analyze_n8n — deterministic structural scan from workspace-relative path or bounded in-memory raw JSON.
  • solvelang_validate_solve — validates a .solve file through the local solvec executable.
  • solvelang_generate_n8n_report — Markdown or CI-friendly JSON evidence without writing files.

Solve Graph

Current source includes bounded deterministic tools for:

  • node find/ranked search;
  • dependencies/dependents;
  • shortest/alternative paths plus explanations;
  • transitive impact plus explanation;
  • affected validation candidates;
  • cycles and hotspots;
  • entrypoint/unreachable candidates;
  • structural security summary.

Graph input can be a workspace-relative canonical graph or raw canonical graph JSON. It must remain analyze-only, declare network/write access false, use stable canonical IDs and pass integrity validation. Graph queries are structural evidence; they do not execute repository code, install dependencies or prove runtime reachability/criticality/security.

Solve Context

Current repository source includes:

  • solvelang_context_plan
  • solvelang_context_pack
  • solvelang_context_retrieve
  • solvelang_context_handoff
  • solvelang_context_handoff_validate
  • solvelang_context_compact_structured
  • solvelang_context_expand_rle
  • solvelang_context_capabilities
  • solvelang_context_index_query
  • solvelang_context_index_status

The two index tools answer from the workspace's persistent Solve Context index (.solve/context-index.json, built and refreshed by the solvelang-context-index CLI in @solvelang/context-index) instead of re-walking the workspace: lexical + graph-structure ranking over content-hashed records, with every excerpt hash-verified against the index before it is returned. See docs/integrations/context-index.md.

Solve Context is deterministic/local-first. It selects exact bounded context, preserves source/excerpt provenance, rejects stale retrieval, supports portable Claude ↔ Codex handoff state, and provides correctness-first lossless structured compaction/expansion. These tools do not launch agents, call providers, mutate repositories or imply a provider proxy.

Solve Context evaluation commands

bash
npm run eval:contextnpm run eval:context:repositorynpm run eval:context:independentnpm run test:context-agent-eval-cli
  • eval:context — synthetic deterministic fixtures;
  • eval:context:repository — pinned first-party SolveLang source regressions;
  • eval:context:independent — independently pinned Chalk/node-fetch source subsets;
  • test:context-agent-eval-cli — validates the offline real-agent record/report claim boundaries.

To summarize separately authorized previously collected agent records:

bash
cat approved-agent-run-records.json | npm run eval:context:agent-records

The summarizer itself makes no provider/network call and uses no credentials. After #920, baseline/context record pairs must use the same outcome-evaluation basis and required-evidence denominator in addition to the same fixture/provider/model/agent/record class.

Repository evaluation does not establish a public token-savings percentage, improved agent success/latency, provider cache savings or competitor superiority.

Input and privacy boundaries

For n8n/workflow analysis, provide exactly one of:

  • path: workspace-relative JSON; or
  • rawJson: bounded n8n JSON supplied directly.

For Solve Graph, provide exactly one of path or canonical graph rawJson.

For Solve Context workspace operations, all file discovery/reading is bounded to the configured workspace and reviewed path/privacy rules. Likely sensitive paths are denied by the context runtime policy.

Raw supplied workflow/graph data is processed in memory, is not written by the read-only tools, and malformed-input errors must not echo sensitive source content.

Security boundaries

  • Workspace-relative paths only; traversal outside the configured root is rejected.
  • Bounded file/raw-input sizes and graph traversal/result/state limits are enforced by tool-specific contracts.
  • No workflow execution, arbitrary repository-source execution, network requests, file writes or credential-value inspection from read-only analysis/context tools.
  • Solve Graph integrity/stable IDs/endpoints/read-only flags are checked before queries.
  • Solve Context preserves explicit source/excerpt hashes, exact ranges and omission/truncation truth.
  • The stdio server writes MCP protocol messages to stdout and diagnostics to stderr.
  • Hosted/remote transport is a separate authenticated boundary and does not inherit local workspace authority automatically.

See the implementation/tool schemas for exact per-tool numeric limits; do not copy a limit from one tool family to another.

Build and qualify current source

bash
cd packages/mcp-servernpm cinpm testnpm run eval:contextnpm run eval:context:repositorynpm run eval:context:independentnpm run test:context-agent-eval-clinpm run test:plugin-roundtripnpm run test:packed

MCP CI also runs the exact locked dependency audit. test:plugin-roundtrip and test:packed pack/install current repository source into clean temporary consumers and verify the shared protocol/entrypoints/allowlist. They do not publish to npm or prove an external marketplace install.

Client configuration

See:

  • plugins/solvelang/ for the canonical published-package plugin bundle;
  • docs/integrations/mcp-codex-claude.md for published-vs-current-source Codex/Claude instructions;
  • plugins/codex/ and plugins/claude/ for legacy/manual examples.

Hosted remote boundary

The repository includes a deliberately read-only Streamable HTTP transport (solvelang-mcp-remote, src/remote.ts): the same raw-JSON-only analysis surface described in docs/integrations/remote-mcp.md, behind bearer authentication, a 4 MiB request ceiling, and a built-in per-address rate limiter (default 60 requests per 60 seconds, enforced before authentication and MCP parsing). Protocol-level tests and a real-client proof (an MCP SDK client completing a context-pack-driven impact task) pin the behavior, and a reviewed production deployment shape lives in deploy/.

The endpoint is LIVE (deployed 2026-11-20 on the owner's explicit production approval): https://mcp.solve-lang.com serves the 10 read-only remote tools behind bearer authentication, as a container on the production host behind TLS, with the built-in rate limit (60 requests per 60 seconds per source) active and the production token held on the host only. Verify at any time: GET https://mcp.solve-lang.com/healthz returns {"status":"ok","service":"solvelang-mcp","mode":"remote-read-only"}. Still outstanding as production hardening: edge rate limiting in front of the origin and monitoring. The hosted relay for the multi-agent bus is also live, at https://relay.solve-lang.com (see the Hosted relay section above).

Multi-agent bus

The package also ships the SolveLang multi-agent bus (solvelang-bus, src/bus-cli.ts, with src/bus-daemon.ts, src/bus-client.ts, src/bus-envelope.ts): a local-first coordination layer for agents sharing a workspace — presence, push signals, and atomic work claims with leases, so contention surfaces at claim time instead of merge time. It layers over the handoff documents above rather than replacing them: the bus carries signals, documents carry truth, and killing the daemon degrades clients to pure document handoffs with no state loss. Messages extend the handoff envelope (content-hash sch_ ids, at-least-once delivery with idempotent consumers) and can carry Phase 4 Ed25519 signatures in the reserved sig field, verified against the same solvelang.key-registry v1 registry as signed gates; without a registry the daemon runs in the explicitly named local-open mode (localhost only, no sender authenticity). Full design, lifecycle, and honest limits: docs/integrations/multi-agent-bus.md.

The bus is a separate bin and module set. It adds no MCP tools and does not change the read-only tool contract of solvelang-mcp or solvelang-mcp-remote.

Hosted relay (live)

The bus's hosted counterpart also ships in this package (solvelang-mcp-relay, src/relay-cli.ts, with src/relay.ts): the same bus envelope, claim leases, and Phase 4 signature verification, carried over authenticated HTTPS between workspaces on different machines — bearer tokens bind one (workspace, agent) pair each, workspaces are fully isolated, and a message that fails authenticity is refused, never relayed. It is a separate bin and adds no MCP tools.

The relay is deployed and live at https://relay.solve-lang.com (Phase 6, Nov 20, 2026): a dedicated container on the SolveLang production host beside the remote MCP endpoint, deployed from the reviewed shape in deploy/ (Dockerfile.relay, docker-compose.relay.yml) under the owner's explicit production approval, and verified end-to-end from outside the host with two independent clients (claim contention denied at claim time, signed signal delivery, presence, unsigned/revoked/bad-signature refusals, workspace isolation, rate-limit 429, and a stop/restart kill-switch cycle degrading to document handoffs). Full protocol, hosting shape, and honest limits: docs/integrations/hosted-relay.md.

Releases

MCP @solvelang/[email protected] is published on npm and GitHub, verified on 2026-09-20. It distributes the tagged release source; later main changes require separate distribution. Managed-workspace marketplace installation and public Plugin Directory listing remain unverified. v0.2.0 is historical.

Trusted Publishing/protected release controls remain the required publication path. Do not republish the old version number, add an npm access token, or create a release/publication outside the approved process.

來源:packages/mcp-server/README.md,提交 9b9edff

工具

0
該伺服器需要 API 金鑰等憑證,因此 SourceWeft 無法在沒有憑證的情況下讀取其工具,也未收錄。

版本歷史

1
  1. v0.3.0最新Nov 21, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分