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/HasData/indeed-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/rules/hasdata/indeed-mcp/hasdata-indeed)<a href="https://agentmods.dev/rules/hasdata/indeed-mcp/hasdata-indeed"><img src="https://agentmods.dev/badge/rules/hasdata/indeed-mcp/hasdata-indeed/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/rules/hasdata/indeed-mcp/hasdata-indeed"><img src="https://agentmods.dev/badge/rules/hasdata/indeed-mcp/hasdata-indeed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00416 |
| Opus 5.5 | $0.00006 | $0.00166 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
hasdata-indeed 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 3d 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
Indeed through HasData
Two tools. hasdata_indeed_listing_getJobListings needs both keyword and location. hasdata_indeed_job_getJobDetails needs the posting url, which the listing tool returns.
Search shape
keyword is the role as a candidate would type it, location is the city and region in Indeed's own wording, such as Austin, TX. sort takes relevance or date, and start pages. domain picks the country site, so a search on indeed.com and one on uk.indeed.com are different markets, not the same list translated.
Listings expire fast
A posting that has been taken down answers with 400 and requestMetadata.status set to error. A URL from a search run a week ago is often already dead, so fetch details in the same session as the search, and treat a failure as an expired posting rather than a broken call.
Reading the payload
A keyword and location pair with no openings returns a successful result with an empty jobs array. Salary is present only where the employer published it, so report it as missing rather than estimating.
The listing already carries title, company, location, salary where given and the posting date. Open the details tool only when the task needs the full description, because that is one call per posting.
Prompts and resources
The server also serves resources that spell out the accepted values of every parameter that takes a fixed list, each one at hasdata://indeed/<parameter>. Reading one spends no credits and makes no upstream request, which beats discovering the vocabulary from a rejected call. Listing them needs no API key either, so a client can read them before the user has connected an account.
Ready-made prompts cover the usual workflows. Offer one of those before composing a tool call by hand.
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.
- 3d ago Changed · +6 lines d726fa1fcd16
- 23d ago First seen · 23 lines · 14 tokens per session scan A 9bb65c63ca0c
hasdata-indeed is a cursor rule published in the GitHub repository HasData/indeed-mcp (11 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 416 once invoked, about $0.0001 per session on Opus 5.5. 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-09-23.
Other cursor rules, from other repositories
hasdata-instagram
How to pull public Instagram profiles and post feeds through the HasData MCP server.
hasdata-booking
How to pull Booking.com hotel search and property details through the HasData MCP server.
hasdata-zillow
How to pull Zillow listings and property details through the HasData MCP server.
hasdata-tiktok
How to pull TikTok profiles, post feeds, keyword search and comments through the HasData MCP server.
hasdata-airbnb
How to pull Airbnb stays and listing details through the HasData MCP server.
hasdata-duckduckgo
How to pull DuckDuckGo results and the Search Assist answer through the HasData MCP server.