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/brilliantdirectories/brilliant-directories-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/mcp/brilliantdirectories/brilliant-directories-mcp/brilliant-directories)<a href="https://agentmods.dev/mcp/brilliantdirectories/brilliant-directories-mcp/brilliant-directories"><img src="https://agentmods.dev/badge/mcp/brilliantdirectories/brilliant-directories-mcp/brilliant-directories/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/brilliantdirectories/brilliant-directories-mcp/brilliant-directories"><img src="https://agentmods.dev/badge/mcp/brilliantdirectories/brilliant-directories-mcp/brilliant-directories.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
brilliant-directories 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 12d 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
{
"brilliant-directories": {
"type": "http",
"url": "https://brilliantmcp.com",
"headers": {
"X-Api-Key": "${BD_API_KEY}",
"X-BD-Site-URL": "${BD_SITE_URL}"
}
}
}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.
- 12d ago First seen · 10 lines scan A e3f33bc413e9
brilliant-directories is an MCP server published in the GitHub repository brilliantdirectories/brilliant-directories-mcp (18 stars, last pushed 4d 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
mcp-memory-server
Hosted memory for AI agents that learns from outcomes — one key across Claude, Cursor & ChatGPT. Runs locally from the @mnemoverse/mcp-memory-server npm package. Needs 2 environment variables to run.
codeseeker
MCP server "codeseeker" as configured in jghiringhelli/codeseeker. Runs ./dist/cli/codeseeker-cli.js with node. Needs 1 environment variable to run.
dex-core
MCP server "dex-core" as configured in davekilleen/Dex. Runs ${CLAUDE_PLUGIN_ROOT}/bin/dex-python.mjs with node.
google-search-console-mcp
MCP server for Google Search Console: query performance data, inspect URLs, check indexing, and generate HTML SEO audit reports from Claude, Cursor, Zed, and any Model Context Protocol client. Runs locally from the mcp-google-search-console Python package. Needs 6 environment variables to run.
roamzy
MCP server for Roamzy — buy and manage global eSIM through Claude, Cursor, Continue, and any MCP client. Runs locally from the @roamzy/mcp-server npm package.
qobrix-crm-mcp
MCP server "qobrix-crm-mcp" as configured in gca-ltd/qobrix-crm-mcp. Runs locally from the qobrix-crm-mcp npm package.