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/veezeehq/veezee-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/veezeehq/veezee-mcp/linkedin)<a href="https://agentmods.dev/mcp/veezeehq/veezee-mcp/linkedin"><img src="https://agentmods.dev/badge/mcp/veezeehq/veezee-mcp/linkedin/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/veezeehq/veezee-mcp/linkedin"><img src="https://agentmods.dev/badge/mcp/veezeehq/veezee-mcp/linkedin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linkedin 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 8d 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
{ "linkedin": { "url": "https://mcp.veezee.io/linkedin", "type": "streamable-http" } }
What else
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 8d ago First seen · 6 lines scan A f5caedd3d0ab
linkedin is an MCP server published in the GitHub repository veezeehq/veezee-mcp (0 stars, last pushed 1mo 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
1social
Publish, schedule and verify social posts across seven networks from your AI assistant. Remote server at mcp.1social.dev.
linkedin-mcp-pro
MCP server "linkedin-mcp-pro" as configured in horizonbymuneeb/linkedin-mcp-pro. Runs locally from the linkedin-mcp-pro Python package.
linkedin-jobs
MCP server "linkedin-jobs" as configured in administrativetrick/linkedin-mcp. Launched with @administrativetrick/linkedin-jobs-mcp.
what2post
Read-only access to your what2post LinkedIn data: posts, profile stats, follower growth and goals. Remote server at what2postapp.com.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
lunchmoney-mcp
MCP server for managing LunchMoney personal finances: transactions, budgets, categories, and more. Runs locally from the @akutishevsky/lunchmoney-mcp npm package. Needs 2 environment variables to run.