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/nolenation04/anchord-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/nolenation04/anchord-mcp/anchord)<a href="https://agentmods.dev/mcp/nolenation04/anchord-mcp/anchord"><img src="https://agentmods.dev/badge/mcp/nolenation04/anchord-mcp/anchord/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/nolenation04/anchord-mcp/anchord"><img src="https://agentmods.dev/badge/mcp/nolenation04/anchord-mcp/anchord.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
anchord 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 11d 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
{
"anchord": {
"command": "npx",
"args": [
"-y",
"@anchord/mcp-server"
],
"env": {
"ANCHORD_API_KEY": "",
"ANCHORD_API_BASE_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.
- 11d ago First seen · 13 lines scan A dff3900f9130
anchord is an MCP server published in the GitHub repository nolenation04/anchord-mcp (0 stars, last pushed 5mo 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
hubspot-mcp
MCP server "hubspot-mcp" as configured in ohneben/Hubspot-MCP. Runs in Docker (ghcr.io/ohneben/hubspot-mcp:1.0.1). Needs 3 environment variables to run.
fein
MCP server "fein" as configured in clippycommits/fein. Runs locally from the fein npm package.
gtmos-mcp
Read-only CRM audit for Claude over MCP: score data integrity, find duplicate clusters and stalled revenue, in your environment through your own token. Runs locally from the gtmos-mcp Python package. Needs 1 environment variable to run.
hubspot-multi-mcp
Local, read-only MCP server that connects Claude to MANY HubSpot portals at once, by name. Unofficial, not affiliated with HubSpot. Runs locally from the hubspot-multi-mcp npm package.
leadpipe-mcp
AI-powered lead qualification engine for MCP. Ingest, enrich, score, and export leads to your CRM. Runs locally from the leadpipe-mcp-server npm package.
qorami
Check an email before an AI agent sends it: send / ask a human / block. Detects prompt injection. Runs locally from the qorami-mcp npm package. Needs 1 environment variable to run.