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/WeJob-IT/WeJob-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/wejob-it/wejob-mcp/wejob)<a href="https://agentmods.dev/mcp/wejob-it/wejob-mcp/wejob"><img src="https://agentmods.dev/badge/mcp/wejob-it/wejob-mcp/wejob/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/wejob-it/wejob-mcp/wejob"><img src="https://agentmods.dev/badge/mcp/wejob-it/wejob-mcp/wejob.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wejob 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
{
"wejob": {
"url": "https://mcp.wejob.ch/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 8584825e9d55
wejob is an MCP server published in the GitHub repository WeJob-IT/WeJob-MCP (1 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
cca-study-mcp
MCP server "cca-study-mcp" as configured in timothywarner-org/claude-architect. Runs tsx with node.
molecare-mcp
Educational dermatology knowledge and lesion tooling. No credentials needed. Not a medical device. Runs locally from the molecare-mcp npm package. Needs 5 environment variables to run.
memora-mcp
Flashcards, quizzes, and cloze cards with spaced repetition, as an inline MCP App. Runs locally from the @servation/memora-mcp npm package.
connectry-architect-mcp
Free certification prep for the Claude Certified Architect exam by Connectry LABS. Runs locally from the connectry-architect-mcp npm package.
context7
Context7's hosted MCP server: up-to-date library documentation and code examples on demand. Remote server at mcp.context7.com.
student-progress-tracker
MCP server "student-progress-tracker" as configured in woodstocksoftware/student-progress-tracker. Runs locally from the student-progress-tracker Python package.