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.
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplateWrote 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/mcp/upex-galaxy/agentic-qa-boilerplate/dbhub)<a href="https://agentmods.dev/mcp/upex-galaxy/agentic-qa-boilerplate/dbhub"><img src="https://agentmods.dev/badge/mcp/upex-galaxy/agentic-qa-boilerplate/dbhub.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
dbhub 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 8d 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.
What it actually says
{
"dbhub": {
"command": "bunx",
"args": [
"-y",
"@bytebase/[email protected]",
"--config",
"dbhub.toml"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 11 lines scan A a9663f11934d
dbhub is an MCP server published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (21 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-30.
Other mcp servers, from other repositories
supabase
Lets the agent manage Supabase projects: inspect tables, run SQL, handle migrations and read logs. Runs locally from the @supabase/mcp-server-supabase npm package. Needs 1 environment variable to run.
Supabase
Lets the agent manage Supabase projects: inspect tables, run SQL, handle migrations and read logs. Runs locally from the @supabase/mcp-server-supabase npm package.
redis
MCP server "redis" as configured in latestaiagents/agent-skills. Runs locally from the @anthropic/mcp-redis npm package. Needs 1 environment variable to run.
postgres
MCP server "postgres" as configured in latestaiagents/agent-skills. Runs locally from the @anthropic/mcp-postgres npm package. Needs 1 environment variable to run.
convex
Client for the Convex Cloud. Runs locally from the convex npm package.
dataverse-mcp
An MCP server for interacting with Microsoft Dataverse environments during development. Runs locally from the dataverse-mcp Python package.