planetscale/mcp-server is an open-source collection of TypeScript tools and shared code for the PlanetScale MCP server, which lets compatible coding agents interact with PlanetScale. It supports local development, testing, and deployment of the repository’s maintained tools; other server features are generated from PlanetScale’s API specification. The catalogue entries provide instructions, an MCP configuration, and a skill for working with it.
Borrowing it
Nothing to install: this file belongs to planetscale/mcp-server. 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/planetscale/mcp-server/main/.cursor/skills/verify-ps-mcp/SKILL.mdgit clone --depth 1 https://github.com/planetscale/mcp-serverWrote 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/planetscale/mcp-server/verify-ps-mcp)<a href="https://agentmods.dev/skills/planetscale/mcp-server/verify-ps-mcp"><img src="https://agentmods.dev/badge/skills/planetscale/mcp-server/verify-ps-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/planetscale/mcp-server/verify-ps-mcp"><img src="https://agentmods.dev/badge/skills/planetscale/mcp-server/verify-ps-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.00056 | $0.01489 |
| Opus 5.5 | $0.00022 | $0.00596 |
| Sonnet 5.5 | $0.00011 | $0.00298 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
verify-ps-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 19d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify the PlanetScale MCP server
The user-facing surface of this repo is an MCP server spoken over stdio: a client
(Cursor, MCP Inspector, the hosted Gram deployment) starts src/server.ts, lists
tools, and calls them. Verification means being that client — start the real
server, call a real tool the way a real client would, and keep the response.
npm run lint only proves the code typechecks. It does not prove a tool returns
the right fields, so it is never sufficient as a proof on its own.
Launch
There is no long-lived server to babysit. Each drive spawns its own
node_modules/.bin/tsx src/server.ts child over stdio and kills it when the run
ends, so runs are isolated from each other and can overlap safely.
One-time setup in a fresh checkout:
npm install
cp .env.example .env # then fill in PLANETSCALE_API_TOKEN
The server loads .env itself through dotenv/config. Auth resolves in
src/lib/auth.ts: PLANETSCALE_OAUTH2_ACCESS_TOKEN wins if set, otherwise
PLANETSCALE_API_TOKEN (a <token-id>:pscale_tkn_... service token) is sent
as-is. Never echo either value into a terminal, a log, or an evidence file.
Doctor
Run this first whenever anything looks wrong. It is read-only: it starts a server, initializes the MCP session, lists tools, and checks the fourteen expected tools are registered.
node .cursor/skills/verify-ps-mcp/drive.mjs doctor
Healthy output names all fourteen tools and exits 0:
OK 14 tools registered: execute_read_query, execute_write_query, get_branch_metrics, get_insights, get_payment_method_setup, get_postgres_logs, get_query_tag, list_cluster_sizes, list_query_error_executions, list_query_error_patterns, list_query_tag_summaries, list_query_tags, search_documentation, update_payment_method
A crash here means the server itself is broken (a bad import, a Zod schema that throws at construction), not the tool you were investigating. Fix that before driving a feature.
Drive
node .cursor/skills/verify-ps-mcp/drive.mjs call <tool> '<json args>' \
[--expect <substring>] [--label <name>]
What ships with it
14 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.
- drive.mjs 7.3 KB runs code
- features/execute-read-query.md 2.5 KB
- features/execute-write-query.md 2.7 KB
- features/get-branch-metrics.md 2.3 KB
- features/get-insights.md 6.8 KB
- features/get-postgres-logs.md 9.1 KB
- features/get-query-tag.md 4.5 KB
- features/list-cluster-sizes.md 1.8 KB
- features/list-query-error-executions.md 4.4 KB
- features/list-query-error-patterns.md 3.5 KB
- features/list-query-tag-summaries.md 8.5 KB
- features/list-query-tags.md 6.1 KB
- features/README.md 3.2 KB
- features/search-documentation.md 4.7 KB
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.
- 19d ago Changed 3922e3eb102f
- 2mo ago First seen · 142 lines · 56 tokens per session scan A 7e2efb0ee0d0
verify-ps-mcp is a skill published in the GitHub repository planetscale/mcp-server (5 stars, last pushed 18d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,489 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other skills, from other repositories
datasets
Use when a collection needs queried or joined test inputs, a reusable named view, spreadsheet worksheet data, live database rows, or script access through pm.datasets(). Chooses between a simple iteration file and a dataset while preserving query semantics, portability, and credential boundaries. Use for requests such…
lore-onboard
First-time setup wizard for LoreConvo. Verifies the MCP server is connected, the database is accessible, hooks are configured, and runs a test save/load cycle. Use when the user says "set up loreconvo", "onboard", "/lore-onboard", "verify loreconvo", "test loreconvo setup", or after first installing the plugin.
amazon aurora dsql
Deprecated compatibility redirect for Aurora DSQL guidance. Use when a request concerns DSQL, Aurora DSQL, distributed SQL, DSQL schemas, migrations, queries, authentication, performance, or application development.
flutter-mcp-toolkit-control
Drive a running Flutter app — tap, scroll, type, fill forms, hot-reload, navigate. Use when you need to interact with the UI.
flutter-mcp-e2e-harness
Use this skill when writing or running repeatable E2E scenarios for Flutter apps as checked-in Dart with the fluttermcpharness package (packages/harness) — build/launch the app, attach to its VM service, drive widgets (snapshot/tap/enter text) and assert without MCP; also covers the repo showcase launcher (make…
harness-engineering-lifecycle
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and…