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/dominion525/familiarWrote 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/dominion525/familiar/familiar-mcp)<a href="https://agentmods.dev/mcp/dominion525/familiar/familiar-mcp"><img src="https://agentmods.dev/badge/mcp/dominion525/familiar/familiar-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/mcp/dominion525/familiar/familiar-mcp"><img src="https://agentmods.dev/badge/mcp/dominion525/familiar/familiar-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
familiar-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 7d 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
{
"familiar-mcp": {
"command": "npx",
"args": [
"-y",
"@dominion525/familiar-mcp"
],
"env": {}
}
}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.
- 7d ago First seen · 10 lines scan A ae4af1ede58f
familiar-mcp is an MCP server published in the GitHub repository dominion525/familiar (0 stars, last pushed 2mo 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-31.
Other mcp servers, from other repositories
safari-mcp
Native Safari browser automation for AI agents — 80 tools, zero Chrome overhead. Runs locally from the safari-mcp npm package.
wbrowser
MCP server "wbrowser" as configured in w-partners/Wbrowser. Runs locally from the wbrowser npm package.
browser-mcp
MCP server "browser-mcp" as configured in EndymionLee/PilotBrowseMCP. Runs BrowserPlugin\server\dist\index.js with node.
public-browser
Public Browser MCP Server - Chrome browser automation via CDP. Runs locally from the public-browser npm package.
chrome-faithful
MCP server "chrome-faithful" as configured in bpc-oss/chrome-faithful. Runs src/mcp-server.mjs with node. Needs 1 environment variable to run.
claude-in-chrome
MCP server "claude-in-chrome" as configured in hamzahamidi/claude-in-chrome-cli. Launched with claude --claude-in-chrome-mcp.