MCP Toolbox for Databases is an open-source Model Context Protocol server that connects AI agents, development environments, and applications to enterprise databases through ready-made or custom tools. It is for exploring schemas, querying data, generating code, and building specialized database tools for production agents. The catalogue includes its skills, instructions, and MCP server integration.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add googleapis/mcp-toolbox --skill docsite-link-sweepgit clone --depth 1 https://github.com/googleapis/mcp-toolboxWrote 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/googleapis/mcp-toolbox/docsite-link-sweep)<a href="https://agentmods.dev/skills/googleapis/mcp-toolbox/docsite-link-sweep"><img src="https://agentmods.dev/badge/skills/googleapis/mcp-toolbox/docsite-link-sweep/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/googleapis/mcp-toolbox/docsite-link-sweep"><img src="https://agentmods.dev/badge/skills/googleapis/mcp-toolbox/docsite-link-sweep.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.00148 | $0.01817 |
| Opus 5.5 | $0.00059 | $0.00727 |
| Sonnet 5.5 | $0.00030 | $0.00363 |
| Haiku 4.5 | $0.00015 | $0.00182 |
Grade A, and why
docsite-link-sweep 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 16d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docsite Link Sweep (mcp-toolbox)
No link check runs in CI. Both link checker workflows are disabled at the GitHub Actions level, so a broken link now merges without warning and nobody files the weekly report issue. Run this skill yourself. Nothing else catches these.
The skill drives two tools, and each one misses what the other catches:
- Lychee resolves a link as a filesystem path or a network URL. It knows nothing about Hugo.
- Hugo resolves a
.mdlink to a pretty URL and generates links from shortcodes. It never checks an external URL.
The skill covers the gap. It applies safe mechanical fixes to internal links. It reports external and ambiguous failures for a maintainer to decide.
Prerequisites
- Clean git working tree. Commit or stash docs changes before you start.
lychee. Install withbrew install lychee, or rundocker run --rm -v "$PWD:/input" lycheeverse/lychee. Lychee is now the only external URL check anywhere in this repo. Without it, run the grep and build passes, then report that external URLs went unchecked.hugo, Extended v0.146.0 or later, for shortcode and build verification.
Default scope is README.md and docs/en/. Sweep the full scope by default, because no CI pass has covered these files since the workflows went dark. Narrow to the changed markdown files only when the maintainer asks to check one PR.
References
DEVELOPER.md: canonical link rules. Its "Link Checking and Fixing with Lychee" section says the repo uses lychee for link checks. That claim is stale for CI. The link rules and the.lycheeignoreguidance in it remain correct.references/link-forms.md: path-to-URL mapping, version leaks, and Hugo traps..lycheeignore: excluded domains and URLs. The local lychee CLI still reads this file, so it still applies. Every entry must carry a comment.link_checker.yamlandlink_checker_report.yaml: both disabled. The YAML still declares apull_requesttrigger and a weeklyschedule, so read the workflow state, not the file. Check withgh api repos/googleapis/mcp-toolbox/actions/workflows. Treat these files as the reference for flags to reuse, not as a check that runs.
What ships with it
2 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.
- 16d ago First seen · 144 lines · 148 tokens per session scan A f02572bd21b2
docsite-link-sweep is a skill published in the GitHub repository googleapis/mcp-toolbox (16,665 stars, last pushed today), licensed Apache-2.0. It adds 148 tokens to every session and 1,817 once invoked, about $0.0006 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-09-30.
Other skills, from other repositories
benchling-integration
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
agentfield-use
Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …
agentfield
Design and ship a multi-agent system on AgentField. Use when the user asks to build, scaffold, design, or run an agent, reasoner network, multi-agent backend, or 'an agent that does X' — whenever the work would otherwise be a single LLM call or a flat LangChain/CrewAI/AutoGen chain. The skill produces composite…
agentfield-personal
Build and install a personal AI agent on this machine's AgentField: real source in /agentfield-agents, packaged with agentfield-package.yaml, installed with af install, started with af run, registered on the local control plane, and visible in AgentField Desktop with a keys form and an auto-start toggle. Use when the…
api-reference
Memoria REST API endpoints, request/response formats, auth, rate limits. Use when calling or implementing API endpoints.
architecture
Memoria codebase structure, workspace layout, key traits, database tables, config patterns, and testing conventions. Use when navigating or modifying Memoria code.