SignOff Studio

io.github.samuccaya由 GitHub 帳號 samuccaya 發布v26.8.42更新於 Nov 19, 2026

Local API and database verification for AI coding agents: HTTP checks and read-only SQL.

已驗證STDIO僅桌面資料庫開發者工具

概覽

AI 產生的概覽

本機 MCP 伺服器,讓 AI 程式助理送出 HTTP 請求並執行唯讀 SQL,以證明 API 可用且資料庫中的資料正確。

可以做什麼
  • 送出臨時 HTTP 請求,並對狀態碼、延遲、標頭、內文文字與 JSON 路徑做內嵌檢查
  • 依名稱、URL 或資料夾搜尋、讀取並執行已儲存的請求或整個集合,可分頁檢視大型結果
  • 檢視資料庫連線與結構,執行唯讀查詢,並對列數、純量或欄位內容做斷言
  • 把請求與資料庫檢查綁在一起,用一次判定驗證 API 造成的效果
  • 將驗證過的請求與檢查存回工作區,匯入 OpenAPI、Postman、Insomnia、Bruno 或 cURL,啟動本機 mock API,並匯出 HTML/Markdown 報告、JUnit 與 PR 摘要
適用情境
適合需要確認端點行為符合預期、且產生的資料確實寫入資料庫的情境,也適合希望把檢查保存下來,讓後續工作階段或同事重跑的情況。
執行需求
以 stdio 在本機執行;需要 Node.js 22 或更新版本,或使用內建同一伺服器的 SignOff Studio 桌面應用程式。資料庫密碼來自連線設定的密碼環境變數鍵,或來自執行中的桌面應用程式。可選用 SIGNOFF_WORKSPACE 指定工作區資料夾;SIGNOFF_TELEMETRY=0 或 DO_NOT_TRACK=1 可關閉遙測。不需帳號或雲端轉送。
安裝前請注意
對於擁有者標記為允許代理寫入的連線,db_execute 可執行寫入操作,但標記為正式環境的連線會拒絕代理寫入,且預設為可回滾的試執行;請先確認該設定。已儲存的請求、檢查與環境會寫入工作區,每次呼叫都會記錄到稽核檔。除非關閉遙測,否則會傳送匿名使用次數。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 SignOff Studio,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

SignOff Studio MCP server

Lets AI coding agents prove an API works and that the database holds the right data, on your machine. Works with Claude Code, Cursor, VS Code (Copilot agent mode), Gemini CLI, Claude Desktop and any other MCP client.

bash
npx -y @signoff-studio/mcp init      # in your project: registers the server with the agents it finds
  • Call APIs without curl. http_request returns status, timing, the headers that matter and a compact body (large JSON comes back as its shape plus the first items), with inline checks for status, latency, headers, body text and JSON path.
  • Check the database, read-only. db_query and db_assert run on PostgreSQL, MySQL/MariaDB, SQL Server, Oracle and SQLite. Read-only is enforced by the driver (a read-only transaction or connection), whatever the SQL says.
  • API and database in one step. verify_api_effect answers "POST /orders returned 201, and did the row land?" with one verdict.
  • Checks that persist. save_request and save_db_check write into the project's SignOff Studio workspace, so the next agent session and your teammates rerun them from git.

Runs locally over stdio. No account, no cloud relay. Secrets are redacted by value in every output.

This repository holds the public package docs, registry metadata, example configs and the Claude Code plugin. The server is built from the SignOff Studio product and published to npm as @signoff-studio/mcp.

Install

Needs Node.js 22 or newer (or the SignOff Studio desktop app, which ships the same server and needs no Node).

init only adds a signoff-studio entry: it keeps every other server and setting, never replaces an existing entry and lists each file before writing. Options: --dry-run, --agent claude,cursor,vscode,gemini|all, --global (user-wide), --agents-md (adds a short how-to section to AGENTS.md).

Or register it yourself:

AgentCommand or config
Claude Codeclaude mcp add signoff-studio -- npx -y @signoff-studio/mcp (native Windows: -- cmd /c npx -y @signoff-studio/mcp)
Claude Code pluginclaude plugin marketplace add samuccaya/signoff-studio-mcp then claude plugin install signoff-studio@signoff-studio (adds a verification skill and /signoff-studio:verify)
Cursor.cursor/mcp.json, see examples/cursor
VS Code.vscode/mcp.json, see examples/vscode. The SignOff Studio extension registers the server automatically.
Gemini CLIgemini mcp add signoff-studio npx -- -y @signoff-studio/mcp (native Windows: gemini mcp add signoff-studio cmd -- /c npx -y @signoff-studio/mcp), or examples/gemini
Desktop app (no Node)"<install>\QaSignOff.exe" --mcp-stdio; Microsoft Store install: signoff-mcp.exe. Or use Connect AI agents in the app.

Tools

ToolWhat it does
workspace_statusWhat the server sees: workspace, collections, environment names, DB connections, policy.
http_requestAd-hoc HTTP request with optional inline checks. Works without a workspace.
find_requests, get_requestSearch saved requests by name, "POST /orders", URL or folder; read one.
run_request, run_collectionRun saved requests or a whole collection with their checks; failures show expected vs actual.
get_resultPage through a large result by resultId.
db_connections, db_schemaWorkspace connections (no secrets) and a compact one-line-per-table schema.
db_queryOne read-only SELECT: grid, row count, truncation flag.
db_assertQuery plus expectation (rowCount, scalar, column contains, empty): pass or fail with the actual value.
db_executeWrites, only on connections the owner marked for agent writes, never on production; dry-run (rollback) by default.
verify_api_effectA request plus database checks bound to its response; one verdict.
save_request, save_db_check, create_environmentPersist what the agent verified into the workspace (no overwrite unless asked).
import_requestsImport OpenAPI, Postman, Insomnia, Bruno or cURL.
mock_serverStart or stop a local mock API from a collection or spec.
export_evidenceHTML/Markdown report plus JUnit, and a short summary for the PR.

Read tools carry readOnlyHint, so clients can approve them once. Response bodies and table rows are returned as data, never as instructions.

Safety

  • SQL is read-only unless the owner ticks Allow AI agent writes on a connection. Production-tagged connections never accept agent writes.
  • Database passwords come from the connection's password env key (workspace .env or the environment) or, for vault-only passwords, from the running SignOff Studio app. The model never sees them.
  • Every call is logged to .signoff/agent-audit.jsonl in the workspace (no secrets, no bodies).

Workspace discovery

The agent's open folder (MCP roots), then walking up from the working folder for signoff-workspace.json, then SIGNOFF_WORKSPACE, then the workspace last open in the app. --workspace <dir> overrides. Without a workspace, http_request still works.

Telemetry

Anonymous counts (which tools ran, error codes, which agent) help us fix confusing errors. No URLs, SQL, bodies or names are sent. Turn it off with SIGNOFF_TELEMETRY=0 or DO_NOT_TRACK=1. Details: https://testapilocally.com/mcp#privacy

Links

© Samuccaya Tech LLP. Free to use under the license in LICENSE.txt.

來源:README.md,提交 79dbb8f

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v26.8.41Nov 19, 2026

評分

已滿足適用檢查項的 40%

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

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

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

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

    請在儲存庫或註冊中心條目中宣告授權條款。