io.github.CloudCorpRecords/indeeddata
NPM · @RENETURCIOS/INDEEDDATA · 2 COMPONENTS
Indeed job data as JSON: listing search by keyword and location, plus full job details.
Available components
Last scanned (19 hours ago)
Scores higher than 49% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 476 tokens (~238/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Nov 26 +4
- Stability: unverified → 0.33 ▲ functional
- 11 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 10 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@reneturcios/indeeddata@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hasdata_indeed_job_getJobDetails indeed_job: GET / ~104
Get Indeed Job Details Fetches a single Indeed job posting by its viewjob URL. Returns job title, company, location, salary/compensation, employment type, full description, and benefits. Use for ATS/CRM enrichment, compensation benchmarking, resume-to-JD matching with LLMs, and structured archival of postings discovered via the Indeed Listing endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL of the job vacancy to retrieve details for. |
No output schema declared.
No examples provided.
hasdata_indeed_listing_getJobListings indeed_listing: GET / ~372
Get Indeed Job Listings Searches Indeed job listings by keyword and location with sort (relevance/date), country domain targeting, date-posted (1/3/7/14 days) and remote/hybrid filters, and offset-based pagination (start). Returns an array of jobs with title, company, location, salary, posted date, job URL, sponsored flag, and jobKey (Indeed's stable job id, the only reliable dedup key for sponsored postings) for the requested page. With sponsoredOnly the request exits from the domain's country, where Indeed serves Canadian searches as sponsored postings. Use for job-market dashboards, role/geo hiring-trend analysis, sourcing pipelines, and generating URL lists to feed into the Indeed Job endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| datePosted | number | – | Returns only jobs posted within the given number of days. |
| domain | string | – | The domain of the Indeed site (optional). Provide one exact documented value (62 allowed), e.g. `ar.indeed.com`, `au.indeed.com`. |
| keyword | string | yes | The keyword used to search for job listings. |
| location | string | yes | The location to search for job listings. |
| remoteType | string | – | Returns only remote (`remote`) or hybrid (`hybrid`) jobs. In the US, Indeed ties fully remote jobs to the country rather than a city, so use a country-wide location such as `United States`: with a ci… |
| sort | string | – | The sorting option for the search results. |
| sponsoredOnly | boolean | – | When enabled, the request is made in a way that returns more sponsored listings. Defaults to false. |
| start | number | – | The starting index of the results to retrieve (optional). |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/indeeddata MCP server?
io.github.CloudCorpRecords/indeeddata runs locally as an npm package, launched with npx -y @reneturcios/indeeddata mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/indeeddata
claude mcp add cloudcorprecords-indeeddata -- npx -y @reneturcios/indeeddata mcp
What is the io.github.CloudCorpRecords/indeeddata MCP server?
io.github.CloudCorpRecords/indeeddata is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/indeeddata. Indeed job data as JSON: listing search by keyword and location, plus full job details. This page covers its npm package (@reneturcios/indeeddata).
Is the io.github.CloudCorpRecords/indeeddata MCP server safe to use?
io.github.CloudCorpRecords/indeeddata scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.CloudCorpRecords/indeeddata MCP server expose?
io.github.CloudCorpRecords/indeeddata exposes 2 tools: hasdata_indeed_job_getJobDetails, hasdata_indeed_listing_getJobListings. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/indeeddata MCP server still maintained?
io.github.CloudCorpRecords/indeeddata is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/indeeddata MCP server under?
io.github.CloudCorpRecords/indeeddata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/indeeddata MCP server?
VerifyMCP ran 16 checks on io.github.CloudCorpRecords/indeeddata, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.