MCP server over a daily job market scan: four read-only tools to search postings and track market stats
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"jobscan-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# jobscan-mcp [](https://m8ven.ai/mcp/aminafara123-jobscan-mcp-1c9wqy) An MCP server over my [job-scan-automation](https://github.com/aminafara123/job-scan-automation) dataset: the daily market scan behind [uae-remote-jobs-daily](https://github.com/aminafara123/uae-remote-jobs-daily), exposed as tools that any MCP-capable AI client can call. MCP (Model Context Protocol) is the open standard for giving AI models controlled access to tools and data. This server is the pattern in miniature and in production: my own dataset, four read-only tools, and a model on the other end that can suddenly answer questions like "any new GRC postings this week?" with real data instead of guesses. ## Tools | Tool | What it does | |---|---| | `latest_report()` | Full text of the most recent daily scan | | `search_jobs(query, days)` | Search postings across the last N days of reports, links included | | `market_stats(days)` | Per-day relevant/new counts: the pulse of the niche market | | `is_seen(company, title)` | Whether the scanner's dedupe memory already knows a posting | ## Setup ```bash pipx install jobscan-mcp ``` `uvx jobscan-mcp` works too if you prefer no install. Hacking on a clone instead: ```bash python3 -m venv .venv .venv/bin/pip install mcp ``` It reads `~/aiProjects/aminWork/job-research/scraper`. Point `JOBSCAN_DATA_DIR` at your own data folder if your copy lives somewhere else. Wire it into Claude Code: ```bash claude mcp add jobscan -- jobscan-mcp ``` Running from a clone, point it at the venv instead: ```bash claude mcp add jobscan -- /path/to/jobscan-mcp/.venv/bin/python /path/to/jobscan-mcp/jobscan_mcp.py ``` ## Demo What it looks like from Claude Code: ``` > check the job scan: anything new in IAM in the last week? ⏺ jobscan · search_jobs("IAM", 7) 2 match(es) for 'IAM': [2026-09-26] - **IAM Engineer** at Falconride Logistics ht…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.