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/blockmatic/basilicWrote 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/blockmatic/basilic/docu)<a href="https://agentmods.dev/mcp/blockmatic/basilic/docu"><img src="https://agentmods.dev/badge/mcp/blockmatic/basilic/docu/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/mcp/blockmatic/basilic/docu"><img src="https://agentmods.dev/badge/mcp/blockmatic/basilic/docu.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
docu 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 1mo 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
{
"docu": {
"url": "https://mcp.vercel.com/gaboesquivel/basilic-docu",
"description": "Vercel project documentation context"
}
}What else mcp.json configures
This page is one entry in a file that holds 10. Installing the file brings all of them; each is measured and scanned on its own page.
- MCP server agents A not measured
- MCP server coderabbit A not measured
- MCP server fastify A not measured
- MCP server github A not measured
- MCP server next A not measured
- MCP server next-devtools A not measured
- MCP server shadcnui-jpisnice-react A not measured
- MCP server shadcnui-jpisnice-react-native A not measured
- MCP server shadcnui-official A not measured
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.
- 1mo ago First seen · 6 lines scan A 4ddca55cd233
docu is an MCP server published in the GitHub repository blockmatic/basilic (90 stars, last pushed 9d 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-09-06.
Other mcp servers, from other repositories
biligWorkpaperFile
MCP server "biligWorkpaperFile" as configured in proompteng/bilig. Launched with npm exec --yes --package @bilig/workpaper@latest -- bilig-workpaper-mcp --workpa.
bilig-workpaper
Formula-backed WorkPaper tools for workbook readback, input edits, and JSON persistence. Runs locally from the @bilig/workpaper npm package.
boxpdf
Resource-only MCP server with docs and templates for the boxpdf TypeScript PDF layout library. Runs locally from the boxpdf npm package.
yungle
Ask about your Yungle transfers, share big files, download what you're sent. Approve every send. Runs locally from the yungle-mcp npm package. Needs 2 environment variables to run.
supabase
Supabase's hosted MCP server: lets the agent manage projects, tables, SQL and migrations. Remote server at mcp.supabase.com.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.