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/administrativetrick/linkedin-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/administrativetrick/linkedin-mcp/linkedin-jobs)<a href="https://agentmods.dev/mcp/administrativetrick/linkedin-mcp/linkedin-jobs"><img src="https://agentmods.dev/badge/mcp/administrativetrick/linkedin-mcp/linkedin-jobs/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/administrativetrick/linkedin-mcp/linkedin-jobs"><img src="https://agentmods.dev/badge/mcp/administrativetrick/linkedin-mcp/linkedin-jobs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
linkedin-jobs 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 10d 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-jobs": {
"command": "@administrativetrick/linkedin-jobs-mcp",
"args": [],
"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.
- 10d ago First seen · 7 lines scan A 7c89b1f98c57
linkedin-jobs is an MCP server published in the GitHub repository administrativetrick/linkedin-mcp (2 stars, last pushed 9mo 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
job-search-mcp
Claude searches real job boards, scores each job 0-100 for fit, and shows a ranked board. Runs locally from the @servation/job-search-mcp npm package. Needs 3 environment variables to run.
mcp-server-104
Unofficial MCP server for 104.com.tw (Taiwan job board): search jobs, job details, company openings. Runs locally from the mcp-server-104 npm package.
1social
Publish, schedule and verify social posts across seven networks from your AI assistant. Remote server at mcp.1social.dev.
all
Real-time LinkedIn, X (Twitter) and Reddit data for AI agents. Free key, self-minted, no signup. Remote server at mcp.veezee.io.
LinkedIn data for AI agents: search, profiles, companies, posts. Free key, self-minted, no signup. Remote server at mcp.veezee.io.
Reddit posts, comments, subreddits, and search for AI agents. Free key, self-minted, no signup. Remote server at mcp.veezee.io.