SignOff Studio

io.github.samuccayaPublished by GitHub account samuccayav26.8.42Updated Nov 19, 2026

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

VerifiedSTDIODesktop onlyDatabasesDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an AI coding agent send HTTP requests and run read-only SQL to prove an API works and the database holds the right data.

What you can do
  • Send ad-hoc HTTP requests with inline checks on status, latency, headers, body text and JSON paths
  • Search, read and run saved requests or whole collections, paging through large results
  • Inspect database connections and schema, run read-only queries and assert on row counts, scalars or columns
  • Verify an API effect by binding a request to database checks in one verdict
  • Persist verified requests and checks to the workspace, import OpenAPI, Postman, Insomnia, Bruno or cURL, run a local mock API, and export HTML/Markdown, JUnit and PR summaries
When to use it
Useful when an agent needs to confirm that an endpoint behaves as expected and that the resulting data actually landed in the database, and when those checks should be saved so later sessions or teammates can rerun them.
Requirements
Runs locally over stdio; Node.js 22 or newer, or the SignOff Studio desktop app which ships the same server. Database passwords come from the connection's password environment key or the running desktop app. Optional SIGNOFF_WORKSPACE points at a workspace folder; SIGNOFF_TELEMETRY=0 or DO_NOT_TRACK=1 disables telemetry. No account or cloud relay.
Before you install
Database writes are possible through db_execute on connections the owner marked for agent writes, though production-tagged connections refuse them and dry-run rollback is the default; review that setting. Saved requests, checks and environments are written into the workspace, and every call is logged to an audit file. Anonymous usage counts are sent unless telemetry is turned off.

Installation

In SourceWeft

  1. Open SignOff Studio in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.
send_feedbackSend the SignOff Studio team a short note about the tool itself (bug, missing feature, idea); returns a known workaround if there is one. Never URLs, data or code. Off with SIGNOFF_AGENT_FEEDBACK=0.

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

Privacy Policy

Full policy: https://qasignoff.com/privacy and https://testapilocally.com/mcp#privacy. In short:

  • Collected:
    • Anonymous usage counts: which agent connected, how the server was started, and each tool's outcome or error code, at most once a day per combination.
    • When agent feedback is on, the short reports an agent writes about SignOff Studio itself (a bug, a missing feature, an idea), plus the product version, OS and the names and outcomes of recent tool calls. Reports that contain URLs, hostnames, emails, tokens, SQL, code, file paths or workspace secrets are refused before sending. Never request or response bodies, database rows, credentials or conversation content.
  • Use and storage: to fix bugs and decide what to build. Counts and reports are stored by the usage service (Cloudflare D1); reports are also filed in a private GitHub repository the SignOff Studio team triages. Not shared with or sold to third parties.
  • Retention: usage counts and feedback reports are deleted automatically after 18 months (a daily cleanup in the usage service).
  • Your copy: every feedback report is listed in ~/.signoff-studio/feedback/sent.jsonl.
  • Turning it off: SIGNOFF_AGENT_FEEDBACK=0 turns off feedback. SIGNOFF_TELEMETRY=0 or DO_NOT_TRACK=1 turns off both counts and feedback. The SignOff Studio app's Preferences has the same switches.
  • Contact: via https://qasignoff.com.

Links

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

Source: README.md at commit f70f66c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v26.8.42LatestNov 19, 2026
  2. v26.8.41Nov 19, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.