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/linglistack/linkednav-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/linglistack/linkednav-mcp/linkednav)<a href="https://agentmods.dev/mcp/linglistack/linkednav-mcp/linkednav"><img src="https://agentmods.dev/badge/mcp/linglistack/linkednav-mcp/linkednav/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/linglistack/linkednav-mcp/linkednav"><img src="https://agentmods.dev/badge/mcp/linglistack/linkednav-mcp/linkednav.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linkednav 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 17d 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
{
"linkednav": {
"type": "http",
"url": "https://mcp.linkednav.com/"
}
}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.
- 17d ago First seen · 6 lines scan A 809ebf4b6437
linkednav is an MCP server published in the GitHub repository linglistack/linkednav-mcp (0 stars, last pushed 17d 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-10-11.
Other mcp servers, from other repositories
insaight
MCP server "insaight" as configured in spirosbax/insaight. Runs locally from the git+https://github.com/spirosbax/[email protected] Python package.
linkedin-mcp-server
MCP server "linkedin-mcp-server" as configured in prakharagarwal-dev/linkedin-mcp-server. Runs in Docker (ghcr.io/prakharagarwal-dev/linkedin-mcp-server:0.16.0).
1social
Publish, schedule and verify social posts across seven networks from your AI assistant. Remote server at mcp.1social.dev.
sales-navigator
MCP server that gives AI assistants access to LinkedIn Sales Navigator contact and account search. Runs locally from the linkedin-sales-nav-mcp Python package.
linkedin-sales-nav-mcp
MCP server that gives AI assistants access to LinkedIn Sales Navigator contact and account search. Runs locally from the linkedin-sales-nav-mcp Python package.
storeinspect
MCP server "storeinspect", hosted remotely at mcp.storeinspect.com, as configured in StoreInspect/storeinspect-mcp.