Borrowing it
Nothing to install: this file belongs to eamonboyle/mssql-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eamonboyle/mssql-mcp/main/.cursor/skills/verify-mssql-mcp/SKILL.mdgit clone --depth 1 https://github.com/eamonboyle/mssql-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/eamonboyle/mssql-mcp/verify-mssql-mcp)<a href="https://agentmods.dev/skills/eamonboyle/mssql-mcp/verify-mssql-mcp"><img src="https://agentmods.dev/badge/skills/eamonboyle/mssql-mcp/verify-mssql-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/eamonboyle/mssql-mcp/verify-mssql-mcp"><img src="https://agentmods.dev/badge/skills/eamonboyle/mssql-mcp/verify-mssql-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00072 | $0.01745 |
| Opus 5 | $0.00036 | $0.00873 |
| Sonnet 5 | $0.00014 | $0.00349 |
| Haiku 4.5 | $0.00007 | $0.00175 |
Grade A, and why
verify-mssql-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify MSSQL MCP
The product a user touches is the MCP server. Cursor, VS Code, Claude Desktop, and any JSON-RPC client call tools, read resources, and get prompts. There is no web UI. Stdio is the default client transport. Verification drives the same server over Streamable HTTP because that is how this repo already scripts a real client.
Do not drive an MCP process you did not start with verify-ctl.sh launch.
Read features/README.md before a run. Drive the mapped feature file, not a convenient substitute.
Launch
From the repo root:
cp -n .env.example .env
.cursor/skills/verify-mssql-mcp/scripts/verify-ctl.sh launch
The script copies .env.example to .env when .env is missing. It starts mssql-mcp-dev with npm run db:up when that container is absent. It builds dist/ when dist/index.js is missing. It then starts node dist/index.js with MCP_TRANSPORT=http, MCP_HTTP_HOST=127.0.0.1, MCP_HTTP_PORT=3334, ENABLE_DDL=true, and READONLY=false.
Ready means initialize against http://127.0.0.1:3334/mcp succeeds. The process logs MCP Streamable HTTP server listening on http://127.0.0.1:3334/mcp to /tmp/verify-mssql-mcp/state/server.log.
Override the bind with MCP_VERIFY_HTTP_HOST and MCP_VERIFY_HTTP_PORT. Override state and evidence directories with VERIFY_STATE_DIR and VERIFY_EVIDENCE_DIR. Defaults are /tmp/verify-mssql-mcp/state and /tmp/verify-mssql-mcp/evidence.
A second HTTP instance can share Docker SQL Server if it uses another port. Writes share AppDB. Use unique emails and table names. If port 3334 already has a listener this skill did not start, launch refuses. It does not kill that process.
npm run test:e2e is a different launcher. It binds port 3333 and kills whatever already owns that port. Do not run it while a verify instance is up unless you intend to take over 3333.
Teardown is verify-ctl.sh cleanup. Docker SQL Server stays running.
Doctor
.cursor/skills/verify-mssql-mcp/scripts/verify-ctl.sh doctor
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 124 lines · 72 tokens per session scan A c30b6e9e4817
verify-mssql-mcp is a skill published in the GitHub repository eamonboyle/mssql-mcp (5 stars, last pushed 9d ago), licensed MIT. It adds 72 tokens to every session and 1,745 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
azure-cosmos-db-py
Build Azure Cosmos DB NoSQL services with Python/FastAPI following production-grade patterns. Use when implementing database client setup with dual auth (DefaultAzureCredential + emulator), service layer classes with CRUD operations, partition key strategies, parameterized queries, or TDD patterns for Cosmos. Triggers…
adding-dbt-unit-test
Creates unit test YAML definitions that mock upstream model inputs and validate expected outputs. Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt.
gh-issue
Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…
Drizzle ORM Testing
Testing patterns for Drizzle ORM covering migration testing, query builder testing, transaction testing, and database integration testing with PostgreSQL, SQLite, and MySQL.