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/asmisha/remoote-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/asmisha/remoote-mcp/remote-jobs)<a href="https://agentmods.dev/mcp/asmisha/remoote-mcp/remote-jobs"><img src="https://agentmods.dev/badge/mcp/asmisha/remoote-mcp/remote-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/asmisha/remoote-mcp/remote-jobs"><img src="https://agentmods.dev/badge/mcp/asmisha/remoote-mcp/remote-jobs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
remote-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 9d 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
{
"remote-jobs": {
"url": "https://api.remoote.app/remoote/agents/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.
- 9d ago First seen · 6 lines scan A 804b5d3832d5
remote-jobs is an MCP server published in the GitHub repository asmisha/remoote-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
jobscout-mcp
Multi-source job discovery, deduplication and AI/Web3 classification for AI agents. Runs locally from the @sarutobi-sasuke/jobscout-mcp npm package. Needs 3 environment variables to run.
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
jobfindsme
MCP server "jobfindsme" as configured in russeell/jobfindsme. Launched with bash -lc exec "${JOBFINDSME_PYTHON:-$HOME/.jobfindsme/runtime/bin/python}" -m jo.
multi-account-gmail-mcp
Multi-account Gmail MCP server for AI agents. Runs locally from the multi-account-gmail-mcp Python package. Needs 3 environment variables to run.
outlook_multi_mailbox
MCP server "outlookmultimailbox" as configured in ftaricano/mcp-outlook. Runs ${CODEX_PLUGIN_ROOT}/dist/plugin/stdio.js with node.