hasdata-indeed-mcp 1.0.1__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- hasdata_indeed_mcp-1.0.1/.github/ISSUE_TEMPLATE/inaccuracy.md +21 -0
- hasdata_indeed_mcp-1.0.1/.github/workflows/contract.yml +31 -0
- hasdata_indeed_mcp-1.0.1/.github/workflows/publish.yml +65 -0
- hasdata_indeed_mcp-1.0.1/.gitignore +11 -0
- hasdata_indeed_mcp-1.0.1/LICENSE +21 -0
- hasdata_indeed_mcp-1.0.1/PKG-INFO +373 -0
- hasdata_indeed_mcp-1.0.1/README.md +359 -0
- hasdata_indeed_mcp-1.0.1/glama.json +7 -0
- hasdata_indeed_mcp-1.0.1/hasdata_indeed_mcp/__init__.py +28 -0
- hasdata_indeed_mcp-1.0.1/index.mjs +24 -0
- hasdata_indeed_mcp-1.0.1/package.json +40 -0
- hasdata_indeed_mcp-1.0.1/pyproject.toml +24 -0
- hasdata_indeed_mcp-1.0.1/server.json +44 -0
- hasdata_indeed_mcp-1.0.1/test/tools.test.mjs +135 -0
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: Something in the README is wrong
|
|
3
|
+
about: A tool table, a response sample or a documented behaviour does not match reality
|
|
4
|
+
labels: documentation
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
**Where in the README**
|
|
8
|
+
|
|
9
|
+
Section or heading.
|
|
10
|
+
|
|
11
|
+
**What it says**
|
|
12
|
+
|
|
13
|
+
Quote the line.
|
|
14
|
+
|
|
15
|
+
**The call you made**
|
|
16
|
+
|
|
17
|
+
Tool name and arguments, or the equivalent REST URL with your key removed.
|
|
18
|
+
|
|
19
|
+
**What came back**
|
|
20
|
+
|
|
21
|
+
Trimmed response, with anything private removed.
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# The tool contract is checked on a schedule as well as on push, because the upstream tool list
|
|
2
|
+
# can change without a single commit in this repository.
|
|
3
|
+
name: tool contract
|
|
4
|
+
|
|
5
|
+
on:
|
|
6
|
+
push:
|
|
7
|
+
branches: [main]
|
|
8
|
+
pull_request:
|
|
9
|
+
schedule:
|
|
10
|
+
- cron: '0 6 * * 1'
|
|
11
|
+
workflow_dispatch:
|
|
12
|
+
|
|
13
|
+
permissions:
|
|
14
|
+
contents: read
|
|
15
|
+
|
|
16
|
+
jobs:
|
|
17
|
+
contract:
|
|
18
|
+
runs-on: ubuntu-latest
|
|
19
|
+
timeout-minutes: 5
|
|
20
|
+
steps:
|
|
21
|
+
- uses: actions/checkout@v4
|
|
22
|
+
- uses: actions/setup-node@v4
|
|
23
|
+
with:
|
|
24
|
+
node-version: '22'
|
|
25
|
+
# Forks cannot read repository secrets. The suite skips its live checks when the key is
|
|
26
|
+
# absent, so a pull request from a fork stays green instead of failing for a reason the
|
|
27
|
+
# contributor cannot fix.
|
|
28
|
+
- name: Assert the tool list still matches the README
|
|
29
|
+
env:
|
|
30
|
+
HASDATA_API_KEY: ${{ secrets.HASDATA_API_KEY }}
|
|
31
|
+
run: npm test
|
|
@@ -0,0 +1,65 @@
|
|
|
1
|
+
# Publishes the npm and PyPI wrapper packages on a version tag, using OIDC
|
|
2
|
+
# trusted publishing. No NPM_TOKEN or PYPI_TOKEN is stored anywhere: GitHub
|
|
3
|
+
# mints a short-lived OIDC token per run, and npmjs.org / pypi.org accept it
|
|
4
|
+
# because this repo + workflow are configured as trusted publishers.
|
|
5
|
+
#
|
|
6
|
+
# One-time setup, done once per package on the registries (not in this repo):
|
|
7
|
+
# npmjs.org -> package settings -> Trusted Publisher -> GitHub Actions,
|
|
8
|
+
# repo HasData/indeed-mcp, workflow publish.yml
|
|
9
|
+
# pypi.org -> the hasdata org -> Publishing -> add a trusted publisher
|
|
10
|
+
# (pending publisher works before the first release),
|
|
11
|
+
# repo HasData/indeed-mcp, workflow publish.yml
|
|
12
|
+
#
|
|
13
|
+
# The MCP registry entry (com.hasdata/indeed) is NOT published here. It uses
|
|
14
|
+
# domain auth, which would need the namespace-wide Ed25519 key as a secret in
|
|
15
|
+
# every repo. That key stays off CI; the registry entry is published by hand
|
|
16
|
+
# when server.json changes, after the package versions below are live.
|
|
17
|
+
#
|
|
18
|
+
# Release: bump nothing by hand. Tag the commit `vX.Y.Z` and push the tag; the
|
|
19
|
+
# tag is the single source of the version and is written into both manifests.
|
|
20
|
+
|
|
21
|
+
name: publish
|
|
22
|
+
|
|
23
|
+
on:
|
|
24
|
+
push:
|
|
25
|
+
tags: ['v*.*.*']
|
|
26
|
+
|
|
27
|
+
permissions:
|
|
28
|
+
contents: read
|
|
29
|
+
id-token: write
|
|
30
|
+
|
|
31
|
+
jobs:
|
|
32
|
+
npm:
|
|
33
|
+
runs-on: ubuntu-latest
|
|
34
|
+
steps:
|
|
35
|
+
- uses: actions/checkout@v4
|
|
36
|
+
- uses: actions/setup-node@v4
|
|
37
|
+
with:
|
|
38
|
+
node-version: '22'
|
|
39
|
+
registry-url: 'https://registry.npmjs.org'
|
|
40
|
+
- name: Set version from the tag
|
|
41
|
+
run: npm version "${GITHUB_REF_NAME#v}" --no-git-tag-version --allow-same-version
|
|
42
|
+
- name: Publish to npm (OIDC, no token)
|
|
43
|
+
run: npm publish --access public
|
|
44
|
+
|
|
45
|
+
pypi:
|
|
46
|
+
runs-on: ubuntu-latest
|
|
47
|
+
steps:
|
|
48
|
+
- uses: actions/checkout@v4
|
|
49
|
+
- uses: actions/setup-python@v5
|
|
50
|
+
with:
|
|
51
|
+
python-version: '3.12'
|
|
52
|
+
- name: Set version from the tag
|
|
53
|
+
run: |
|
|
54
|
+
python - "${GITHUB_REF_NAME#v}" <<'PY'
|
|
55
|
+
import re, sys
|
|
56
|
+
v = sys.argv[1]
|
|
57
|
+
p = "pyproject.toml"
|
|
58
|
+
t = open(p, encoding="utf-8").read()
|
|
59
|
+
t = re.sub(r'(?m)^version = ".*"$', f'version = "{v}"', t, count=1)
|
|
60
|
+
open(p, "w", encoding="utf-8", newline="\n").write(t)
|
|
61
|
+
PY
|
|
62
|
+
- name: Build the wheel and sdist
|
|
63
|
+
run: pipx run build
|
|
64
|
+
- name: Publish to PyPI (OIDC, no token)
|
|
65
|
+
uses: pypa/gh-action-pypi-publish@release/v1
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 HasData
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
|
@@ -0,0 +1,373 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: hasdata-indeed-mcp
|
|
3
|
+
Version: 1.0.1
|
|
4
|
+
Summary: MCP server for Indeed through HasData's hosted API. No Indeed developer account.
|
|
5
|
+
Project-URL: Homepage, https://hasdata.com/apis/indeed-api
|
|
6
|
+
Project-URL: Repository, https://github.com/HasData/indeed-mcp
|
|
7
|
+
License: MIT
|
|
8
|
+
License-File: LICENSE
|
|
9
|
+
Keywords: hasdata,indeed,job-search,jobs,mcp,model-context-protocol
|
|
10
|
+
Requires-Python: >=3.10
|
|
11
|
+
Requires-Dist: mcp-proxy>=0.12.0
|
|
12
|
+
Requires-Dist: mcp<2,>=1.17
|
|
13
|
+
Description-Content-Type: text/markdown
|
|
14
|
+
|
|
15
|
+
# Indeed MCP Server
|
|
16
|
+
|
|
17
|
+
<!-- mcp-name: com.hasdata/indeed -->
|
|
18
|
+
|
|
19
|
+
A hosted Model Context Protocol (MCP) server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Indeed tools. Search job listings by keyword and location, and read a single posting in full, all as structured JSON, with no Indeed developer account and no partner approval.
|
|
20
|
+
|
|
21
|
+
It reads public job postings that a signed-out visitor can see.
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
https://mcp.hasdata.com/api/mcp?apis=indeed
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
[](https://glama.ai/mcp/servers/HasData/indeed-mcp)
|
|
28
|
+
[](https://github.com/HasData/indeed-mcp/actions/workflows/contract.yml)
|
|
29
|
+
[](https://modelcontextprotocol.io)
|
|
30
|
+
[](#tools)
|
|
31
|
+
[](https://www.npmjs.com/package/@hasdata/indeed-mcp)
|
|
32
|
+
[](https://pypi.org/project/hasdata-indeed-mcp/)
|
|
33
|
+
[](LICENSE)
|
|
34
|
+
|
|
35
|
+
## Contents
|
|
36
|
+
|
|
37
|
+
- [What you need](#what-you-need)
|
|
38
|
+
- [Quick start](#quick-start)
|
|
39
|
+
- [Example prompts](#example-prompts)
|
|
40
|
+
- [Tools](#tools)
|
|
41
|
+
- [Errors and failure paths](#errors-and-failure-paths)
|
|
42
|
+
- [Pricing, free tier and limits](#pricing-free-tier-and-limits)
|
|
43
|
+
- [Tool selection](#tool-selection)
|
|
44
|
+
- [How it compares](#how-it-compares)
|
|
45
|
+
- [FAQ](#faq)
|
|
46
|
+
- [HasData links](#hasdata-links)
|
|
47
|
+
- [Development](#development)
|
|
48
|
+
- [Contributing](#contributing)
|
|
49
|
+
- [License](#license)
|
|
50
|
+
|
|
51
|
+
## What you need
|
|
52
|
+
|
|
53
|
+
An MCP client and a HasData API key from the [dashboard](https://app.hasdata.com/sign-up?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp), free to create with no card, and the trial covers about 200 calls at the 5-credit rate. This is a remote server, so the simplest path is a URL and an `x-api-key` header, with no container to run and no Indeed developer account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as `@hasdata/indeed-mcp` on npm and `hasdata-indeed-mcp` on PyPI, shown below.
|
|
54
|
+
|
|
55
|
+
## Quick start
|
|
56
|
+
|
|
57
|
+
The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.
|
|
58
|
+
|
|
59
|
+
| Field | Value |
|
|
60
|
+
| :--- | :--- |
|
|
61
|
+
| URL | `https://mcp.hasdata.com/api/mcp?apis=indeed` |
|
|
62
|
+
| Transport | HTTP, streamable |
|
|
63
|
+
| Auth header | `x-api-key: HASDATA_API_KEY` |
|
|
64
|
+
|
|
65
|
+
Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.
|
|
66
|
+
|
|
67
|
+
<details>
|
|
68
|
+
<summary><b>Claude Code</b></summary>
|
|
69
|
+
|
|
70
|
+
```bash
|
|
71
|
+
claude mcp add --transport http indeed "https://mcp.hasdata.com/api/mcp?apis=indeed" \
|
|
72
|
+
--header "x-api-key: HASDATA_API_KEY"
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
</details>
|
|
76
|
+
|
|
77
|
+
<details>
|
|
78
|
+
<summary><b>Claude Desktop</b></summary>
|
|
79
|
+
|
|
80
|
+
Settings, then Connectors, then Add custom connector, then paste `https://mcp.hasdata.com/api/mcp?apis=indeed` and sign in.
|
|
81
|
+
|
|
82
|
+
For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The `@hasdata/indeed-mcp` package is that launcher, and it reads the key from the environment. Add this to `claude_desktop_config.json`:
|
|
83
|
+
|
|
84
|
+
```json
|
|
85
|
+
{
|
|
86
|
+
"mcpServers": {
|
|
87
|
+
"indeed": {
|
|
88
|
+
"command": "npx",
|
|
89
|
+
"args": ["-y", "@hasdata/indeed-mcp"],
|
|
90
|
+
"env": { "HASDATA_API_KEY": "YOUR_KEY" }
|
|
91
|
+
}
|
|
92
|
+
}
|
|
93
|
+
}
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
For Python instead of Node, swap the launcher for the PyPI package, which `uvx` runs without a manual install:
|
|
97
|
+
|
|
98
|
+
```json
|
|
99
|
+
{
|
|
100
|
+
"mcpServers": {
|
|
101
|
+
"indeed": {
|
|
102
|
+
"command": "uvx",
|
|
103
|
+
"args": ["hasdata-indeed-mcp"],
|
|
104
|
+
"env": { "HASDATA_API_KEY": "YOUR_KEY" }
|
|
105
|
+
}
|
|
106
|
+
}
|
|
107
|
+
}
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
</details>
|
|
111
|
+
|
|
112
|
+
<details>
|
|
113
|
+
<summary><b>Cursor</b></summary>
|
|
114
|
+
|
|
115
|
+
`~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one:
|
|
116
|
+
|
|
117
|
+
```json
|
|
118
|
+
{
|
|
119
|
+
"mcpServers": {
|
|
120
|
+
"indeed": {
|
|
121
|
+
"url": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
122
|
+
"headers": { "x-api-key": "HASDATA_API_KEY" }
|
|
123
|
+
}
|
|
124
|
+
}
|
|
125
|
+
}
|
|
126
|
+
```
|
|
127
|
+
|
|
128
|
+
</details>
|
|
129
|
+
|
|
130
|
+
<details>
|
|
131
|
+
<summary><b>Windsurf</b></summary>
|
|
132
|
+
|
|
133
|
+
`~/.codeium/windsurf/mcp_config.json`. Windsurf calls the field `serverUrl`, not `url`:
|
|
134
|
+
|
|
135
|
+
```json
|
|
136
|
+
{
|
|
137
|
+
"mcpServers": {
|
|
138
|
+
"indeed": {
|
|
139
|
+
"serverUrl": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
140
|
+
"headers": { "x-api-key": "HASDATA_API_KEY" }
|
|
141
|
+
}
|
|
142
|
+
}
|
|
143
|
+
}
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
</details>
|
|
147
|
+
|
|
148
|
+
<details>
|
|
149
|
+
<summary><b>VS Code</b></summary>
|
|
150
|
+
|
|
151
|
+
`.vscode/mcp.json` in the workspace:
|
|
152
|
+
|
|
153
|
+
```json
|
|
154
|
+
{
|
|
155
|
+
"servers": {
|
|
156
|
+
"indeed": {
|
|
157
|
+
"type": "http",
|
|
158
|
+
"url": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
159
|
+
"headers": { "x-api-key": "HASDATA_API_KEY" }
|
|
160
|
+
}
|
|
161
|
+
}
|
|
162
|
+
}
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
</details>
|
|
166
|
+
|
|
167
|
+
## Example prompts
|
|
168
|
+
|
|
169
|
+
Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 5 credits.
|
|
170
|
+
|
|
171
|
+
> Search Indeed for "python developer" jobs in New York sorted by date, and give me the ten most recent with company and salary.
|
|
172
|
+
|
|
173
|
+
*One call, 5 credits. A listing page carries company, salary and posted date already.*
|
|
174
|
+
|
|
175
|
+
> Take the top posting from that search and pull its full description and requirements.
|
|
176
|
+
|
|
177
|
+
*One call, 5 credits. The listing carries a job URL, which the details tool takes directly.*
|
|
178
|
+
|
|
179
|
+
> Find "data analyst" jobs in Austin, then pull full details on the three that list a salary.
|
|
180
|
+
|
|
181
|
+
*Four calls, 20 credits. One listing, then one details call for each of the three.*
|
|
182
|
+
|
|
183
|
+
> Compare the salaries posted for "registered nurse" in Chicago against Houston.
|
|
184
|
+
|
|
185
|
+
*Two calls, 10 credits, one listing per city.*
|
|
186
|
+
|
|
187
|
+
Salary is on a listing only when the posting states one, so a "jobs with salary" prompt filters on the field rather than assuming it. Paging costs a call each time, through the `start` offset.
|
|
188
|
+
|
|
189
|
+
## Tools
|
|
190
|
+
|
|
191
|
+
Two tools, read-only. Samples below are trimmed from real calls, and the numbers move as Indeed updates. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.
|
|
192
|
+
|
|
193
|
+
The samples are the payload, not the whole response. A `tools/call` result carries one text block, and that text is itself JSON holding `url`, `status`, `text` and `json`, with the scraped data under `json`. From a raw JSON-RPC response the path is `result.content[0].text`, parsed, then `.json`. A chat client unwraps that for you and code talking to the endpoint directly does not.
|
|
194
|
+
|
|
195
|
+
### Get Indeed job listings
|
|
196
|
+
|
|
197
|
+
[`hasdata_indeed_listing_getJobListings`](https://docs.hasdata.com/apis/indeed/listing?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp)
|
|
198
|
+
|
|
199
|
+
A page of search results by keyword and location.
|
|
200
|
+
|
|
201
|
+
| Parameter | Type | Required | Notes |
|
|
202
|
+
| :--- | :--- | :--- | :--- |
|
|
203
|
+
| `keyword` | string | yes | The search term, as a candidate would type it |
|
|
204
|
+
| `location` | string | yes | City and state, or any location string Indeed accepts |
|
|
205
|
+
| `sort` | string | | `relevance` by default, or `date` for newest first |
|
|
206
|
+
| `domain` | string | | A country site such as `au.indeed.com`. Defaults to the US site |
|
|
207
|
+
| `start` | number | | Result offset for the next page, a number and not a URL. Read the offset from `pagination.nextPage` in the previous response |
|
|
208
|
+
|
|
209
|
+
Returns `searchInformation`, a `jobs` array, `peopleAlsoSearchFor`, and `pagination` whose `nextPage` is the URL of the following page. Each job carries `title`, `company`, `location`, `url`, a short `description`, `sponsored`, the relative `date` and the absolute `isoDate`, a `details` array of labels like `Full-time` and `Hybrid work`, a `benefits` array, and a `salary` object when the posting states one.
|
|
210
|
+
|
|
211
|
+
> A listing carries `details` as an array of plain strings. The job-details tool below returns `details` as an object with `jobType` and `workSetting` arrays. Same name, different shape, so read each per its own tool.
|
|
212
|
+
|
|
213
|
+
```json
|
|
214
|
+
{
|
|
215
|
+
"title": "Hedge Fund Application Developer",
|
|
216
|
+
"company": "TBA",
|
|
217
|
+
"location": "Stamford, CT 06901",
|
|
218
|
+
"url": "https://www.indeed.com/pagead/clk?...",
|
|
219
|
+
"sponsored": true,
|
|
220
|
+
"date": "30+ days ago",
|
|
221
|
+
"isoDate": "2025-06-03T17:22:54.869Z",
|
|
222
|
+
"details": ["Full-time", "Hybrid work"],
|
|
223
|
+
"benefits": ["Health insurance", "401(k)", "401(k) matching"],
|
|
224
|
+
"salary": { "min": 80000, "max": 150000, "type": "YEARLY" }
|
|
225
|
+
}
|
|
226
|
+
```
|
|
227
|
+
|
|
228
|
+
### Get Indeed job details
|
|
229
|
+
|
|
230
|
+
[`hasdata_indeed_job_getJobDetails`](https://docs.hasdata.com/apis/indeed/job?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp)
|
|
231
|
+
|
|
232
|
+
One posting in full, by its job URL.
|
|
233
|
+
|
|
234
|
+
| Parameter | Type | Required | Notes |
|
|
235
|
+
| :--- | :--- | :--- | :--- |
|
|
236
|
+
| `url` | string | yes | A posting URL, the `url` field from a listing result |
|
|
237
|
+
|
|
238
|
+
Returns `title`, `company`, `location`, `sponsored`, a `details` object with `jobType` and `workSetting` arrays, a `salary` object when present, and the posting body in both `description` (plain text) and `descriptionHtml` (the same content with its list and paragraph markup kept). Use `descriptionHtml` when you want the structure and `description` when you want to feed clean text to a model.
|
|
239
|
+
|
|
240
|
+
```json
|
|
241
|
+
{
|
|
242
|
+
"title": "Python Developer",
|
|
243
|
+
"company": "Think IT Technologies",
|
|
244
|
+
"location": "New York, NY 10114",
|
|
245
|
+
"sponsored": false,
|
|
246
|
+
"details": { "jobType": ["Contract"], "workSetting": ["In-person"] },
|
|
247
|
+
"salary": { "min": 60.5, "max": 65, "type": "HOURLY" },
|
|
248
|
+
"description": "Overview\nWe are seeking a Python Developer...",
|
|
249
|
+
"descriptionHtml": "<p><b>Overview</b></p><p>We are seeking a Python Developer...</p>"
|
|
250
|
+
}
|
|
251
|
+
```
|
|
252
|
+
|
|
253
|
+
## Errors and failure paths
|
|
254
|
+
|
|
255
|
+
Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with `isError` set to `true` and the reason as text. The agent reads a message where you might expect a status line.
|
|
256
|
+
|
|
257
|
+
**A wrong key surfaces as tool output, not as a failed connection.** `tools/list` accepts any non-empty key and returns both tools, so the client completes its handshake and shows green. The first tool call then comes back with `isError: true` and the text `HasData API error: 401 Unauthorized`. Watch for that string, because nothing earlier in the flow reports the problem.
|
|
258
|
+
|
|
259
|
+
**A missing key is the one real HTTP error.** Authorization runs before any tool, and the connection itself fails with 401. CORS headers are present, and a browser client reads the status and not an opaque network failure.
|
|
260
|
+
|
|
261
|
+
**An argument that breaks a tool's schema is rejected before it becomes a scrape.** The server answers with `isError: true` and the text `MCP error -32602: Input validation error`, naming the offending field. Nothing is fetched and nothing is charged.
|
|
262
|
+
|
|
263
|
+
**A search that matches nothing returns a successful result with an empty `jobs` array**, not an error. A keyword and location combination with no openings still comes back with `requestMetadata.status` set to `ok`. Test for the array length before you iterate.
|
|
264
|
+
|
|
265
|
+
**A posting that has been taken down returns 400** with `requestMetadata.status` set to `error`. Indeed expires listings quickly, so a URL from an old search can be gone.
|
|
266
|
+
|
|
267
|
+
Results that carry data also carry a `requestMetadata.id` worth quoting in support.
|
|
268
|
+
|
|
269
|
+
## Pricing, free tier and limits
|
|
270
|
+
|
|
271
|
+
Each Indeed tool costs **5 credits per successful call**. Response size does not change the price. A listing page with fifty jobs costs the same as one with two.
|
|
272
|
+
|
|
273
|
+
The free trial is **1,000 credits over 30 days with no card**, which is 200 Indeed calls. After that an active account keeps getting 100 credits topped up each day whenever its balance drops below 100, so a low-volume agent runs on the free tier indefinitely.
|
|
274
|
+
|
|
275
|
+
Paid plans start at **$49 a month** for 200,000 credits, which is 40,000 calls. The unit price falls with volume, from **$1.23 per 1,000 calls** on the entry plan to **$0.50** on Business, **$0.42** on Growth and **$0.37** on the largest [high-volume plans](https://hasdata.com/prices?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp).
|
|
276
|
+
|
|
277
|
+
Your plan also sets concurrency. The free trial allows 1 request at a time, Startup 15, Business 30, Growth 50, and the high-volume plans run from 200 to 1,500. Handle the overflow case defensively in anything unattended.
|
|
278
|
+
|
|
279
|
+
A request that comes back non-200 is not billed. A successful call that finds nothing is still a call.
|
|
280
|
+
|
|
281
|
+
## Tool selection
|
|
282
|
+
|
|
283
|
+
The `apis` query parameter decides which tools your agent sees. Fewer tools means less context spent on tool definitions, and fewer chances for the model to reach for the wrong one.
|
|
284
|
+
|
|
285
|
+
```
|
|
286
|
+
?apis=indeed the two tools in this repo
|
|
287
|
+
?apis=indeed,glassdoor add Glassdoor jobs
|
|
288
|
+
?apis=indeed,google_serp add Google search
|
|
289
|
+
```
|
|
290
|
+
|
|
291
|
+
The parameter takes provider names like `indeed` and individual API names like `indeed_listing`. Misspelled names are ignored. If every name is wrong the request fails with 400, and the body lists both what it did not recognise and every valid value. Drop the parameter and the same endpoint exposes all 57 HasData tools.
|
|
292
|
+
|
|
293
|
+
## How it compares
|
|
294
|
+
|
|
295
|
+
Indeed retired its public Publisher and Job Search APIs, and programmatic access now runs through approved partnerships and ATS integrations rather than a self-serve key. For reading public listings and postings across arbitrary searches, there is no open official route.
|
|
296
|
+
|
|
297
|
+
| | Official Indeed access | This server |
|
|
298
|
+
| :--- | :--- | :--- |
|
|
299
|
+
| Access | Partner or ATS approval | One key and one URL |
|
|
300
|
+
| Scope | Whatever the partnership grants | Any public search or posting |
|
|
301
|
+
| Setup | Business review | None |
|
|
302
|
+
| Output | Depends on the integration | Structured JSON, salary pre-parsed |
|
|
303
|
+
| Writes | Application flows for approved partners | Read-only, public data only |
|
|
304
|
+
|
|
305
|
+
**What this server does not do.** No application submission, no employer dashboard, no candidate data, no private postings. It reads what a signed-out visitor can see.
|
|
306
|
+
|
|
307
|
+
## FAQ
|
|
308
|
+
|
|
309
|
+
### Is there an official Indeed MCP server?
|
|
310
|
+
|
|
311
|
+
Indeed does not publish one. This one is maintained by HasData and reads public pages, which is why it needs no Indeed developer account.
|
|
312
|
+
|
|
313
|
+
### What is an Indeed MCP server?
|
|
314
|
+
|
|
315
|
+
A server that exposes Indeed job data as tools an AI client can call. The client sends a tool call over the Model Context Protocol, the server fetches the data and returns structured JSON, and the model works with the result. This one exposes two tools and runs remotely.
|
|
316
|
+
|
|
317
|
+
### Do I need an Indeed API key or partner account?
|
|
318
|
+
|
|
319
|
+
No. The only credential is your HasData key. There is no Publisher account to apply for, because the tools read public Indeed pages.
|
|
320
|
+
|
|
321
|
+
### How do I page through more than one screen of results?
|
|
322
|
+
|
|
323
|
+
Pass the `start` offset to the listing tool as a number, not a URL. The response returns `pagination.nextPage`, whose own `start` value is the offset for the next page, so read that number and pass it back rather than feeding the URL in.
|
|
324
|
+
|
|
325
|
+
### Why is a salary sometimes missing?
|
|
326
|
+
|
|
327
|
+
Because the posting does not state one. The `salary` object is present only when Indeed shows a figure. Read it defensively.
|
|
328
|
+
|
|
329
|
+
### Can I use this together with other HasData APIs?
|
|
330
|
+
|
|
331
|
+
Yes. The `apis` parameter takes a list, and `?apis=indeed,glassdoor` gives your agent Indeed plus Glassdoor. [Drop the parameter](#tool-selection) and you get everything.
|
|
332
|
+
|
|
333
|
+
### Compliance and personal data
|
|
334
|
+
|
|
335
|
+
HasData accesses publicly available data only. A platform's terms may restrict automated access, and you are responsible for your own compliance. Where the data you collect includes personal information, make sure you have a lawful basis for it under GDPR, CCPA or the equivalent rules in your jurisdiction.
|
|
336
|
+
|
|
337
|
+
## HasData links
|
|
338
|
+
|
|
339
|
+
| | |
|
|
340
|
+
| :--- | :--- |
|
|
341
|
+
| Product page and request builder | [Indeed Scraper API](https://hasdata.com/apis/indeed-api?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
342
|
+
| Server documentation | [MCP server docs](https://docs.hasdata.com/mcp-server?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
343
|
+
| All 57 tools in one server | [HasData/hasdata-mcp](https://github.com/HasData/hasdata-mcp) |
|
|
344
|
+
| Client walkthroughs | [MCP clients and integrations](https://hasdata.com/integrations/mcp?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
345
|
+
| Everything else we scrape | [Indeed Scraper API and 54 more](https://hasdata.com/apis/?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
346
|
+
| Plans and credit costs | [Plans and credit costs](https://hasdata.com/prices?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
347
|
+
| Keys and usage | [HasData dashboard](https://app.hasdata.com?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
348
|
+
| Node launcher on npm | [@hasdata/indeed-mcp](https://www.npmjs.com/package/@hasdata/indeed-mcp) |
|
|
349
|
+
| Python launcher on PyPI | [hasdata-indeed-mcp](https://pypi.org/project/hasdata-indeed-mcp/) |
|
|
350
|
+
|
|
351
|
+
## Development
|
|
352
|
+
|
|
353
|
+
This repository is configuration and documentation for a remote server. There is no build step and nothing to containerize.
|
|
354
|
+
|
|
355
|
+
The tests in `test/` assert the tool contract, the part that can break without a commit here. They check that `?apis=indeed` returns exactly two tools, that every tool still declares its required parameters, that no name changed, and that the key in use is actually accepted. That last check calls a tool for real and costs 5 credits, which is the price of a canary that can fail for the right reason.
|
|
356
|
+
|
|
357
|
+
```bash
|
|
358
|
+
# macOS and Linux
|
|
359
|
+
HASDATA_API_KEY=your_key_here npm test
|
|
360
|
+
|
|
361
|
+
# Windows PowerShell
|
|
362
|
+
$env:HASDATA_API_KEY="your_key_here"; npm test
|
|
363
|
+
```
|
|
364
|
+
|
|
365
|
+
The same suite runs in CI on every push and once a week on a schedule, because the upstream tool list can change without anyone touching this repository. A failure means the tool list moved, the key stopped working, or the endpoint was unreachable, and the assertion message says which.
|
|
366
|
+
|
|
367
|
+
## Contributing
|
|
368
|
+
|
|
369
|
+
Corrections to the tool tables and the response samples are the most useful contribution, because those are the parts that drift. Include the call you made and the response you got. Pull requests from forks run the suite without a key, and the live checks skip instead of going red.
|
|
370
|
+
|
|
371
|
+
## License
|
|
372
|
+
|
|
373
|
+
MIT. See [LICENSE](LICENSE).
|
|
@@ -0,0 +1,359 @@
|
|
|
1
|
+
# Indeed MCP Server
|
|
2
|
+
|
|
3
|
+
<!-- mcp-name: com.hasdata/indeed -->
|
|
4
|
+
|
|
5
|
+
A hosted Model Context Protocol (MCP) server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Indeed tools. Search job listings by keyword and location, and read a single posting in full, all as structured JSON, with no Indeed developer account and no partner approval.
|
|
6
|
+
|
|
7
|
+
It reads public job postings that a signed-out visitor can see.
|
|
8
|
+
|
|
9
|
+
```
|
|
10
|
+
https://mcp.hasdata.com/api/mcp?apis=indeed
|
|
11
|
+
```
|
|
12
|
+
|
|
13
|
+
[](https://glama.ai/mcp/servers/HasData/indeed-mcp)
|
|
14
|
+
[](https://github.com/HasData/indeed-mcp/actions/workflows/contract.yml)
|
|
15
|
+
[](https://modelcontextprotocol.io)
|
|
16
|
+
[](#tools)
|
|
17
|
+
[](https://www.npmjs.com/package/@hasdata/indeed-mcp)
|
|
18
|
+
[](https://pypi.org/project/hasdata-indeed-mcp/)
|
|
19
|
+
[](LICENSE)
|
|
20
|
+
|
|
21
|
+
## Contents
|
|
22
|
+
|
|
23
|
+
- [What you need](#what-you-need)
|
|
24
|
+
- [Quick start](#quick-start)
|
|
25
|
+
- [Example prompts](#example-prompts)
|
|
26
|
+
- [Tools](#tools)
|
|
27
|
+
- [Errors and failure paths](#errors-and-failure-paths)
|
|
28
|
+
- [Pricing, free tier and limits](#pricing-free-tier-and-limits)
|
|
29
|
+
- [Tool selection](#tool-selection)
|
|
30
|
+
- [How it compares](#how-it-compares)
|
|
31
|
+
- [FAQ](#faq)
|
|
32
|
+
- [HasData links](#hasdata-links)
|
|
33
|
+
- [Development](#development)
|
|
34
|
+
- [Contributing](#contributing)
|
|
35
|
+
- [License](#license)
|
|
36
|
+
|
|
37
|
+
## What you need
|
|
38
|
+
|
|
39
|
+
An MCP client and a HasData API key from the [dashboard](https://app.hasdata.com/sign-up?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp), free to create with no card, and the trial covers about 200 calls at the 5-credit rate. This is a remote server, so the simplest path is a URL and an `x-api-key` header, with no container to run and no Indeed developer account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as `@hasdata/indeed-mcp` on npm and `hasdata-indeed-mcp` on PyPI, shown below.
|
|
40
|
+
|
|
41
|
+
## Quick start
|
|
42
|
+
|
|
43
|
+
The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.
|
|
44
|
+
|
|
45
|
+
| Field | Value |
|
|
46
|
+
| :--- | :--- |
|
|
47
|
+
| URL | `https://mcp.hasdata.com/api/mcp?apis=indeed` |
|
|
48
|
+
| Transport | HTTP, streamable |
|
|
49
|
+
| Auth header | `x-api-key: HASDATA_API_KEY` |
|
|
50
|
+
|
|
51
|
+
Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.
|
|
52
|
+
|
|
53
|
+
<details>
|
|
54
|
+
<summary><b>Claude Code</b></summary>
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
claude mcp add --transport http indeed "https://mcp.hasdata.com/api/mcp?apis=indeed" \
|
|
58
|
+
--header "x-api-key: HASDATA_API_KEY"
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
</details>
|
|
62
|
+
|
|
63
|
+
<details>
|
|
64
|
+
<summary><b>Claude Desktop</b></summary>
|
|
65
|
+
|
|
66
|
+
Settings, then Connectors, then Add custom connector, then paste `https://mcp.hasdata.com/api/mcp?apis=indeed` and sign in.
|
|
67
|
+
|
|
68
|
+
For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The `@hasdata/indeed-mcp` package is that launcher, and it reads the key from the environment. Add this to `claude_desktop_config.json`:
|
|
69
|
+
|
|
70
|
+
```json
|
|
71
|
+
{
|
|
72
|
+
"mcpServers": {
|
|
73
|
+
"indeed": {
|
|
74
|
+
"command": "npx",
|
|
75
|
+
"args": ["-y", "@hasdata/indeed-mcp"],
|
|
76
|
+
"env": { "HASDATA_API_KEY": "YOUR_KEY" }
|
|
77
|
+
}
|
|
78
|
+
}
|
|
79
|
+
}
|
|
80
|
+
```
|
|
81
|
+
|
|
82
|
+
For Python instead of Node, swap the launcher for the PyPI package, which `uvx` runs without a manual install:
|
|
83
|
+
|
|
84
|
+
```json
|
|
85
|
+
{
|
|
86
|
+
"mcpServers": {
|
|
87
|
+
"indeed": {
|
|
88
|
+
"command": "uvx",
|
|
89
|
+
"args": ["hasdata-indeed-mcp"],
|
|
90
|
+
"env": { "HASDATA_API_KEY": "YOUR_KEY" }
|
|
91
|
+
}
|
|
92
|
+
}
|
|
93
|
+
}
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
</details>
|
|
97
|
+
|
|
98
|
+
<details>
|
|
99
|
+
<summary><b>Cursor</b></summary>
|
|
100
|
+
|
|
101
|
+
`~/.cursor/mcp.json` for every project, or `.cursor/mcp.json` for one:
|
|
102
|
+
|
|
103
|
+
```json
|
|
104
|
+
{
|
|
105
|
+
"mcpServers": {
|
|
106
|
+
"indeed": {
|
|
107
|
+
"url": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
108
|
+
"headers": { "x-api-key": "HASDATA_API_KEY" }
|
|
109
|
+
}
|
|
110
|
+
}
|
|
111
|
+
}
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
</details>
|
|
115
|
+
|
|
116
|
+
<details>
|
|
117
|
+
<summary><b>Windsurf</b></summary>
|
|
118
|
+
|
|
119
|
+
`~/.codeium/windsurf/mcp_config.json`. Windsurf calls the field `serverUrl`, not `url`:
|
|
120
|
+
|
|
121
|
+
```json
|
|
122
|
+
{
|
|
123
|
+
"mcpServers": {
|
|
124
|
+
"indeed": {
|
|
125
|
+
"serverUrl": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
126
|
+
"headers": { "x-api-key": "HASDATA_API_KEY" }
|
|
127
|
+
}
|
|
128
|
+
}
|
|
129
|
+
}
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
</details>
|
|
133
|
+
|
|
134
|
+
<details>
|
|
135
|
+
<summary><b>VS Code</b></summary>
|
|
136
|
+
|
|
137
|
+
`.vscode/mcp.json` in the workspace:
|
|
138
|
+
|
|
139
|
+
```json
|
|
140
|
+
{
|
|
141
|
+
"servers": {
|
|
142
|
+
"indeed": {
|
|
143
|
+
"type": "http",
|
|
144
|
+
"url": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
145
|
+
"headers": { "x-api-key": "HASDATA_API_KEY" }
|
|
146
|
+
}
|
|
147
|
+
}
|
|
148
|
+
}
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
</details>
|
|
152
|
+
|
|
153
|
+
## Example prompts
|
|
154
|
+
|
|
155
|
+
Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 5 credits.
|
|
156
|
+
|
|
157
|
+
> Search Indeed for "python developer" jobs in New York sorted by date, and give me the ten most recent with company and salary.
|
|
158
|
+
|
|
159
|
+
*One call, 5 credits. A listing page carries company, salary and posted date already.*
|
|
160
|
+
|
|
161
|
+
> Take the top posting from that search and pull its full description and requirements.
|
|
162
|
+
|
|
163
|
+
*One call, 5 credits. The listing carries a job URL, which the details tool takes directly.*
|
|
164
|
+
|
|
165
|
+
> Find "data analyst" jobs in Austin, then pull full details on the three that list a salary.
|
|
166
|
+
|
|
167
|
+
*Four calls, 20 credits. One listing, then one details call for each of the three.*
|
|
168
|
+
|
|
169
|
+
> Compare the salaries posted for "registered nurse" in Chicago against Houston.
|
|
170
|
+
|
|
171
|
+
*Two calls, 10 credits, one listing per city.*
|
|
172
|
+
|
|
173
|
+
Salary is on a listing only when the posting states one, so a "jobs with salary" prompt filters on the field rather than assuming it. Paging costs a call each time, through the `start` offset.
|
|
174
|
+
|
|
175
|
+
## Tools
|
|
176
|
+
|
|
177
|
+
Two tools, read-only. Samples below are trimmed from real calls, and the numbers move as Indeed updates. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.
|
|
178
|
+
|
|
179
|
+
The samples are the payload, not the whole response. A `tools/call` result carries one text block, and that text is itself JSON holding `url`, `status`, `text` and `json`, with the scraped data under `json`. From a raw JSON-RPC response the path is `result.content[0].text`, parsed, then `.json`. A chat client unwraps that for you and code talking to the endpoint directly does not.
|
|
180
|
+
|
|
181
|
+
### Get Indeed job listings
|
|
182
|
+
|
|
183
|
+
[`hasdata_indeed_listing_getJobListings`](https://docs.hasdata.com/apis/indeed/listing?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp)
|
|
184
|
+
|
|
185
|
+
A page of search results by keyword and location.
|
|
186
|
+
|
|
187
|
+
| Parameter | Type | Required | Notes |
|
|
188
|
+
| :--- | :--- | :--- | :--- |
|
|
189
|
+
| `keyword` | string | yes | The search term, as a candidate would type it |
|
|
190
|
+
| `location` | string | yes | City and state, or any location string Indeed accepts |
|
|
191
|
+
| `sort` | string | | `relevance` by default, or `date` for newest first |
|
|
192
|
+
| `domain` | string | | A country site such as `au.indeed.com`. Defaults to the US site |
|
|
193
|
+
| `start` | number | | Result offset for the next page, a number and not a URL. Read the offset from `pagination.nextPage` in the previous response |
|
|
194
|
+
|
|
195
|
+
Returns `searchInformation`, a `jobs` array, `peopleAlsoSearchFor`, and `pagination` whose `nextPage` is the URL of the following page. Each job carries `title`, `company`, `location`, `url`, a short `description`, `sponsored`, the relative `date` and the absolute `isoDate`, a `details` array of labels like `Full-time` and `Hybrid work`, a `benefits` array, and a `salary` object when the posting states one.
|
|
196
|
+
|
|
197
|
+
> A listing carries `details` as an array of plain strings. The job-details tool below returns `details` as an object with `jobType` and `workSetting` arrays. Same name, different shape, so read each per its own tool.
|
|
198
|
+
|
|
199
|
+
```json
|
|
200
|
+
{
|
|
201
|
+
"title": "Hedge Fund Application Developer",
|
|
202
|
+
"company": "TBA",
|
|
203
|
+
"location": "Stamford, CT 06901",
|
|
204
|
+
"url": "https://www.indeed.com/pagead/clk?...",
|
|
205
|
+
"sponsored": true,
|
|
206
|
+
"date": "30+ days ago",
|
|
207
|
+
"isoDate": "2025-06-03T17:22:54.869Z",
|
|
208
|
+
"details": ["Full-time", "Hybrid work"],
|
|
209
|
+
"benefits": ["Health insurance", "401(k)", "401(k) matching"],
|
|
210
|
+
"salary": { "min": 80000, "max": 150000, "type": "YEARLY" }
|
|
211
|
+
}
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
### Get Indeed job details
|
|
215
|
+
|
|
216
|
+
[`hasdata_indeed_job_getJobDetails`](https://docs.hasdata.com/apis/indeed/job?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp)
|
|
217
|
+
|
|
218
|
+
One posting in full, by its job URL.
|
|
219
|
+
|
|
220
|
+
| Parameter | Type | Required | Notes |
|
|
221
|
+
| :--- | :--- | :--- | :--- |
|
|
222
|
+
| `url` | string | yes | A posting URL, the `url` field from a listing result |
|
|
223
|
+
|
|
224
|
+
Returns `title`, `company`, `location`, `sponsored`, a `details` object with `jobType` and `workSetting` arrays, a `salary` object when present, and the posting body in both `description` (plain text) and `descriptionHtml` (the same content with its list and paragraph markup kept). Use `descriptionHtml` when you want the structure and `description` when you want to feed clean text to a model.
|
|
225
|
+
|
|
226
|
+
```json
|
|
227
|
+
{
|
|
228
|
+
"title": "Python Developer",
|
|
229
|
+
"company": "Think IT Technologies",
|
|
230
|
+
"location": "New York, NY 10114",
|
|
231
|
+
"sponsored": false,
|
|
232
|
+
"details": { "jobType": ["Contract"], "workSetting": ["In-person"] },
|
|
233
|
+
"salary": { "min": 60.5, "max": 65, "type": "HOURLY" },
|
|
234
|
+
"description": "Overview\nWe are seeking a Python Developer...",
|
|
235
|
+
"descriptionHtml": "<p><b>Overview</b></p><p>We are seeking a Python Developer...</p>"
|
|
236
|
+
}
|
|
237
|
+
```
|
|
238
|
+
|
|
239
|
+
## Errors and failure paths
|
|
240
|
+
|
|
241
|
+
Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with `isError` set to `true` and the reason as text. The agent reads a message where you might expect a status line.
|
|
242
|
+
|
|
243
|
+
**A wrong key surfaces as tool output, not as a failed connection.** `tools/list` accepts any non-empty key and returns both tools, so the client completes its handshake and shows green. The first tool call then comes back with `isError: true` and the text `HasData API error: 401 Unauthorized`. Watch for that string, because nothing earlier in the flow reports the problem.
|
|
244
|
+
|
|
245
|
+
**A missing key is the one real HTTP error.** Authorization runs before any tool, and the connection itself fails with 401. CORS headers are present, and a browser client reads the status and not an opaque network failure.
|
|
246
|
+
|
|
247
|
+
**An argument that breaks a tool's schema is rejected before it becomes a scrape.** The server answers with `isError: true` and the text `MCP error -32602: Input validation error`, naming the offending field. Nothing is fetched and nothing is charged.
|
|
248
|
+
|
|
249
|
+
**A search that matches nothing returns a successful result with an empty `jobs` array**, not an error. A keyword and location combination with no openings still comes back with `requestMetadata.status` set to `ok`. Test for the array length before you iterate.
|
|
250
|
+
|
|
251
|
+
**A posting that has been taken down returns 400** with `requestMetadata.status` set to `error`. Indeed expires listings quickly, so a URL from an old search can be gone.
|
|
252
|
+
|
|
253
|
+
Results that carry data also carry a `requestMetadata.id` worth quoting in support.
|
|
254
|
+
|
|
255
|
+
## Pricing, free tier and limits
|
|
256
|
+
|
|
257
|
+
Each Indeed tool costs **5 credits per successful call**. Response size does not change the price. A listing page with fifty jobs costs the same as one with two.
|
|
258
|
+
|
|
259
|
+
The free trial is **1,000 credits over 30 days with no card**, which is 200 Indeed calls. After that an active account keeps getting 100 credits topped up each day whenever its balance drops below 100, so a low-volume agent runs on the free tier indefinitely.
|
|
260
|
+
|
|
261
|
+
Paid plans start at **$49 a month** for 200,000 credits, which is 40,000 calls. The unit price falls with volume, from **$1.23 per 1,000 calls** on the entry plan to **$0.50** on Business, **$0.42** on Growth and **$0.37** on the largest [high-volume plans](https://hasdata.com/prices?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp).
|
|
262
|
+
|
|
263
|
+
Your plan also sets concurrency. The free trial allows 1 request at a time, Startup 15, Business 30, Growth 50, and the high-volume plans run from 200 to 1,500. Handle the overflow case defensively in anything unattended.
|
|
264
|
+
|
|
265
|
+
A request that comes back non-200 is not billed. A successful call that finds nothing is still a call.
|
|
266
|
+
|
|
267
|
+
## Tool selection
|
|
268
|
+
|
|
269
|
+
The `apis` query parameter decides which tools your agent sees. Fewer tools means less context spent on tool definitions, and fewer chances for the model to reach for the wrong one.
|
|
270
|
+
|
|
271
|
+
```
|
|
272
|
+
?apis=indeed the two tools in this repo
|
|
273
|
+
?apis=indeed,glassdoor add Glassdoor jobs
|
|
274
|
+
?apis=indeed,google_serp add Google search
|
|
275
|
+
```
|
|
276
|
+
|
|
277
|
+
The parameter takes provider names like `indeed` and individual API names like `indeed_listing`. Misspelled names are ignored. If every name is wrong the request fails with 400, and the body lists both what it did not recognise and every valid value. Drop the parameter and the same endpoint exposes all 57 HasData tools.
|
|
278
|
+
|
|
279
|
+
## How it compares
|
|
280
|
+
|
|
281
|
+
Indeed retired its public Publisher and Job Search APIs, and programmatic access now runs through approved partnerships and ATS integrations rather than a self-serve key. For reading public listings and postings across arbitrary searches, there is no open official route.
|
|
282
|
+
|
|
283
|
+
| | Official Indeed access | This server |
|
|
284
|
+
| :--- | :--- | :--- |
|
|
285
|
+
| Access | Partner or ATS approval | One key and one URL |
|
|
286
|
+
| Scope | Whatever the partnership grants | Any public search or posting |
|
|
287
|
+
| Setup | Business review | None |
|
|
288
|
+
| Output | Depends on the integration | Structured JSON, salary pre-parsed |
|
|
289
|
+
| Writes | Application flows for approved partners | Read-only, public data only |
|
|
290
|
+
|
|
291
|
+
**What this server does not do.** No application submission, no employer dashboard, no candidate data, no private postings. It reads what a signed-out visitor can see.
|
|
292
|
+
|
|
293
|
+
## FAQ
|
|
294
|
+
|
|
295
|
+
### Is there an official Indeed MCP server?
|
|
296
|
+
|
|
297
|
+
Indeed does not publish one. This one is maintained by HasData and reads public pages, which is why it needs no Indeed developer account.
|
|
298
|
+
|
|
299
|
+
### What is an Indeed MCP server?
|
|
300
|
+
|
|
301
|
+
A server that exposes Indeed job data as tools an AI client can call. The client sends a tool call over the Model Context Protocol, the server fetches the data and returns structured JSON, and the model works with the result. This one exposes two tools and runs remotely.
|
|
302
|
+
|
|
303
|
+
### Do I need an Indeed API key or partner account?
|
|
304
|
+
|
|
305
|
+
No. The only credential is your HasData key. There is no Publisher account to apply for, because the tools read public Indeed pages.
|
|
306
|
+
|
|
307
|
+
### How do I page through more than one screen of results?
|
|
308
|
+
|
|
309
|
+
Pass the `start` offset to the listing tool as a number, not a URL. The response returns `pagination.nextPage`, whose own `start` value is the offset for the next page, so read that number and pass it back rather than feeding the URL in.
|
|
310
|
+
|
|
311
|
+
### Why is a salary sometimes missing?
|
|
312
|
+
|
|
313
|
+
Because the posting does not state one. The `salary` object is present only when Indeed shows a figure. Read it defensively.
|
|
314
|
+
|
|
315
|
+
### Can I use this together with other HasData APIs?
|
|
316
|
+
|
|
317
|
+
Yes. The `apis` parameter takes a list, and `?apis=indeed,glassdoor` gives your agent Indeed plus Glassdoor. [Drop the parameter](#tool-selection) and you get everything.
|
|
318
|
+
|
|
319
|
+
### Compliance and personal data
|
|
320
|
+
|
|
321
|
+
HasData accesses publicly available data only. A platform's terms may restrict automated access, and you are responsible for your own compliance. Where the data you collect includes personal information, make sure you have a lawful basis for it under GDPR, CCPA or the equivalent rules in your jurisdiction.
|
|
322
|
+
|
|
323
|
+
## HasData links
|
|
324
|
+
|
|
325
|
+
| | |
|
|
326
|
+
| :--- | :--- |
|
|
327
|
+
| Product page and request builder | [Indeed Scraper API](https://hasdata.com/apis/indeed-api?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
328
|
+
| Server documentation | [MCP server docs](https://docs.hasdata.com/mcp-server?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
329
|
+
| All 57 tools in one server | [HasData/hasdata-mcp](https://github.com/HasData/hasdata-mcp) |
|
|
330
|
+
| Client walkthroughs | [MCP clients and integrations](https://hasdata.com/integrations/mcp?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
331
|
+
| Everything else we scrape | [Indeed Scraper API and 54 more](https://hasdata.com/apis/?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
332
|
+
| Plans and credit costs | [Plans and credit costs](https://hasdata.com/prices?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
333
|
+
| Keys and usage | [HasData dashboard](https://app.hasdata.com?utm_source=github&utm_medium=syndication&utm_campaign=indeed-mcp) |
|
|
334
|
+
| Node launcher on npm | [@hasdata/indeed-mcp](https://www.npmjs.com/package/@hasdata/indeed-mcp) |
|
|
335
|
+
| Python launcher on PyPI | [hasdata-indeed-mcp](https://pypi.org/project/hasdata-indeed-mcp/) |
|
|
336
|
+
|
|
337
|
+
## Development
|
|
338
|
+
|
|
339
|
+
This repository is configuration and documentation for a remote server. There is no build step and nothing to containerize.
|
|
340
|
+
|
|
341
|
+
The tests in `test/` assert the tool contract, the part that can break without a commit here. They check that `?apis=indeed` returns exactly two tools, that every tool still declares its required parameters, that no name changed, and that the key in use is actually accepted. That last check calls a tool for real and costs 5 credits, which is the price of a canary that can fail for the right reason.
|
|
342
|
+
|
|
343
|
+
```bash
|
|
344
|
+
# macOS and Linux
|
|
345
|
+
HASDATA_API_KEY=your_key_here npm test
|
|
346
|
+
|
|
347
|
+
# Windows PowerShell
|
|
348
|
+
$env:HASDATA_API_KEY="your_key_here"; npm test
|
|
349
|
+
```
|
|
350
|
+
|
|
351
|
+
The same suite runs in CI on every push and once a week on a schedule, because the upstream tool list can change without anyone touching this repository. A failure means the tool list moved, the key stopped working, or the endpoint was unreachable, and the assertion message says which.
|
|
352
|
+
|
|
353
|
+
## Contributing
|
|
354
|
+
|
|
355
|
+
Corrections to the tool tables and the response samples are the most useful contribution, because those are the parts that drift. Include the call you made and the response you got. Pull requests from forks run the suite without a key, and the live checks skip instead of going red.
|
|
356
|
+
|
|
357
|
+
## License
|
|
358
|
+
|
|
359
|
+
MIT. See [LICENSE](LICENSE).
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
"""Thin launcher for HasData's hosted Indeed MCP server.
|
|
2
|
+
|
|
3
|
+
Connects an MCP client to the remote streamable-HTTP endpoint through mcp-proxy.
|
|
4
|
+
The server runs on HasData's infrastructure. This package only proxies stdio to it.
|
|
5
|
+
"""
|
|
6
|
+
import os
|
|
7
|
+
import sys
|
|
8
|
+
import subprocess
|
|
9
|
+
|
|
10
|
+
URL = "https://mcp.hasdata.com/api/mcp?apis=indeed"
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
def main() -> None:
|
|
14
|
+
key = os.environ.get("HASDATA_API_KEY")
|
|
15
|
+
if not key:
|
|
16
|
+
sys.stderr.write(
|
|
17
|
+
"HASDATA_API_KEY is not set. Create a free key at https://app.hasdata.com "
|
|
18
|
+
"and set HASDATA_API_KEY.\n"
|
|
19
|
+
)
|
|
20
|
+
raise SystemExit(1)
|
|
21
|
+
args = [
|
|
22
|
+
sys.executable, "-m", "mcp_proxy", URL,
|
|
23
|
+
"--transport=streamablehttp",
|
|
24
|
+
"--headers", "x-api-key", key,
|
|
25
|
+
]
|
|
26
|
+
rc = subprocess.call(args)
|
|
27
|
+
# subprocess returns -N when mcp_proxy is killed by signal N; map to 128+N.
|
|
28
|
+
raise SystemExit(rc if rc >= 0 else 128 - rc)
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
#!/usr/bin/env node
|
|
2
|
+
// Thin launcher: connects an MCP client to HasData's hosted Indeed MCP server
|
|
3
|
+
// (streamable HTTP) through the mcp-remote stdio bridge. The server runs remotely.
|
|
4
|
+
// This package only proxies, so nothing here scrapes anything.
|
|
5
|
+
import { spawn } from 'node:child_process';
|
|
6
|
+
import { createRequire } from 'node:module';
|
|
7
|
+
import { dirname, join } from 'node:path';
|
|
8
|
+
|
|
9
|
+
const URL = 'https://mcp.hasdata.com/api/mcp?apis=indeed';
|
|
10
|
+
const key = process.env.HASDATA_API_KEY;
|
|
11
|
+
if (!key) {
|
|
12
|
+
process.stderr.write('HASDATA_API_KEY is not set. Create a free key at https://app.hasdata.com and set HASDATA_API_KEY.\n');
|
|
13
|
+
process.exit(1);
|
|
14
|
+
}
|
|
15
|
+
// Resolve mcp-remote's CLI from its own package.json bin, so a future layout change
|
|
16
|
+
// or an exports map does not break a hardcoded deep path.
|
|
17
|
+
const require = createRequire(import.meta.url);
|
|
18
|
+
const pkg = require('mcp-remote/package.json');
|
|
19
|
+
const proxy = join(dirname(require.resolve('mcp-remote/package.json')), pkg.bin['mcp-remote']);
|
|
20
|
+
const child = spawn(process.execPath, [proxy, URL, '--header', `x-api-key:${key}`], { stdio: 'inherit' });
|
|
21
|
+
child.on('exit', (code, signal) => {
|
|
22
|
+
if (signal) process.kill(process.pid, signal);
|
|
23
|
+
else process.exit(code ?? 0);
|
|
24
|
+
});
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@hasdata/indeed-mcp",
|
|
3
|
+
"mcpName": "com.hasdata/indeed",
|
|
4
|
+
"version": "1.0.1",
|
|
5
|
+
"description": "MCP server for Indeed through HasData's hosted API: search job listings by keyword and location, and read a single posting in full. No Indeed developer account.",
|
|
6
|
+
"type": "module",
|
|
7
|
+
"bin": {
|
|
8
|
+
"hasdata-indeed-mcp": "index.mjs"
|
|
9
|
+
},
|
|
10
|
+
"files": [
|
|
11
|
+
"index.mjs",
|
|
12
|
+
"README.md",
|
|
13
|
+
"LICENSE"
|
|
14
|
+
],
|
|
15
|
+
"scripts": {
|
|
16
|
+
"test": "node --test"
|
|
17
|
+
},
|
|
18
|
+
"dependencies": {
|
|
19
|
+
"mcp-remote": "^0.1.43"
|
|
20
|
+
},
|
|
21
|
+
"engines": {
|
|
22
|
+
"node": ">=18"
|
|
23
|
+
},
|
|
24
|
+
"license": "MIT",
|
|
25
|
+
"repository": {
|
|
26
|
+
"type": "git",
|
|
27
|
+
"url": "https://github.com/HasData/indeed-mcp.git"
|
|
28
|
+
},
|
|
29
|
+
"homepage": "https://hasdata.com/apis/indeed-api",
|
|
30
|
+
"keywords": [
|
|
31
|
+
"mcp",
|
|
32
|
+
"indeed",
|
|
33
|
+
"indeed-mcp",
|
|
34
|
+
"jobs",
|
|
35
|
+
"job-search",
|
|
36
|
+
"model-context-protocol",
|
|
37
|
+
"hasdata",
|
|
38
|
+
"scraper"
|
|
39
|
+
]
|
|
40
|
+
}
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
[project]
|
|
2
|
+
name = "hasdata-indeed-mcp"
|
|
3
|
+
version = "1.0.1"
|
|
4
|
+
description = "MCP server for Indeed through HasData's hosted API. No Indeed developer account."
|
|
5
|
+
readme = "README.md"
|
|
6
|
+
requires-python = ">=3.10"
|
|
7
|
+
license = { text = "MIT" }
|
|
8
|
+
keywords = ["mcp", "indeed", "jobs", "job-search", "model-context-protocol", "hasdata"]
|
|
9
|
+
# mcp is pinned below 2 because mcp-proxy 0.12.0 imports request_ctx, removed in the mcp 2.x SDK.
|
|
10
|
+
dependencies = ["mcp-proxy>=0.12.0", "mcp>=1.17,<2"]
|
|
11
|
+
|
|
12
|
+
[project.urls]
|
|
13
|
+
Homepage = "https://hasdata.com/apis/indeed-api"
|
|
14
|
+
Repository = "https://github.com/HasData/indeed-mcp"
|
|
15
|
+
|
|
16
|
+
[project.scripts]
|
|
17
|
+
hasdata-indeed-mcp = "hasdata_indeed_mcp:main"
|
|
18
|
+
|
|
19
|
+
[build-system]
|
|
20
|
+
requires = ["hatchling"]
|
|
21
|
+
build-backend = "hatchling.build"
|
|
22
|
+
|
|
23
|
+
[tool.hatch.build.targets.wheel]
|
|
24
|
+
packages = ["hasdata_indeed_mcp"]
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
{
|
|
2
|
+
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
|
|
3
|
+
"name": "com.hasdata/indeed",
|
|
4
|
+
"title": "HasData Indeed",
|
|
5
|
+
"description": "Indeed job listings by keyword and location, and full postings, as structured JSON.",
|
|
6
|
+
"version": "1.0.1",
|
|
7
|
+
"websiteUrl": "https://hasdata.com/apis/indeed-api",
|
|
8
|
+
"repository": {
|
|
9
|
+
"url": "https://github.com/HasData/indeed-mcp",
|
|
10
|
+
"source": "github"
|
|
11
|
+
},
|
|
12
|
+
"remotes": [
|
|
13
|
+
{
|
|
14
|
+
"type": "streamable-http",
|
|
15
|
+
"url": "https://mcp.hasdata.com/api/mcp?apis=indeed",
|
|
16
|
+
"headers": [
|
|
17
|
+
{
|
|
18
|
+
"name": "x-api-key",
|
|
19
|
+
"description": "HasData API key, created at app.hasdata.com. The free trial needs no card.",
|
|
20
|
+
"isRequired": true,
|
|
21
|
+
"isSecret": true
|
|
22
|
+
}
|
|
23
|
+
]
|
|
24
|
+
}
|
|
25
|
+
],
|
|
26
|
+
"packages": [
|
|
27
|
+
{
|
|
28
|
+
"registryType": "npm",
|
|
29
|
+
"identifier": "@hasdata/indeed-mcp",
|
|
30
|
+
"version": "1.0.1",
|
|
31
|
+
"transport": {
|
|
32
|
+
"type": "stdio"
|
|
33
|
+
},
|
|
34
|
+
"environmentVariables": [
|
|
35
|
+
{
|
|
36
|
+
"name": "HASDATA_API_KEY",
|
|
37
|
+
"description": "HasData API key, created at app.hasdata.com. The free trial needs no card.",
|
|
38
|
+
"isRequired": true,
|
|
39
|
+
"isSecret": true
|
|
40
|
+
}
|
|
41
|
+
]
|
|
42
|
+
}
|
|
43
|
+
]
|
|
44
|
+
}
|
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
// Tool contract test.
|
|
2
|
+
//
|
|
3
|
+
// The README promises two tools with specific names and required parameters. The upstream list
|
|
4
|
+
// can change without a single commit here, and the README would start lying silently. These
|
|
5
|
+
// checks catch that before a user does.
|
|
6
|
+
//
|
|
7
|
+
// The last test calls a tool for real. Listing tools accepts any non-empty key, so a contract
|
|
8
|
+
// check that only lists tools stays green with a revoked or mistyped key. That call costs
|
|
9
|
+
// 5 credits, which is the price of a canary that can fail for the right reason.
|
|
10
|
+
//
|
|
11
|
+
// Run: HASDATA_API_KEY=your_key_here npm test
|
|
12
|
+
|
|
13
|
+
import { test } from 'node:test';
|
|
14
|
+
import assert from 'node:assert/strict';
|
|
15
|
+
|
|
16
|
+
const ENDPOINT = 'https://mcp.hasdata.com/api/mcp?apis=indeed';
|
|
17
|
+
const KEY = process.env.HASDATA_API_KEY;
|
|
18
|
+
const TIMEOUT_MS = 30_000;
|
|
19
|
+
|
|
20
|
+
const EXPECTED = {
|
|
21
|
+
hasdata_indeed_listing_getJobListings: ['keyword', 'location'],
|
|
22
|
+
hasdata_indeed_job_getJobDetails: ['url'],
|
|
23
|
+
};
|
|
24
|
+
|
|
25
|
+
// A streamable HTTP body arrives either as plain JSON or as server-sent events. One SSE event
|
|
26
|
+
// can span several data: lines, several events can share one response, and a server is free to
|
|
27
|
+
// send progress notifications before the answer. So collect every event and pick the message
|
|
28
|
+
// carrying our request id instead of trusting the first data: line.
|
|
29
|
+
function parseRpc(raw, id) {
|
|
30
|
+
const trimmed = raw.trim();
|
|
31
|
+
if (trimmed.startsWith('{') || trimmed.startsWith('[')) return JSON.parse(trimmed);
|
|
32
|
+
|
|
33
|
+
const messages = [];
|
|
34
|
+
for (const event of trimmed.split(/\r?\n\r?\n+/)) {
|
|
35
|
+
const data = event
|
|
36
|
+
.split(/\r?\n/)
|
|
37
|
+
.filter((l) => l.startsWith('data:'))
|
|
38
|
+
.map((l) => l.slice(5).replace(/^ /, ''))
|
|
39
|
+
.join('\n');
|
|
40
|
+
if (!data || data === '[DONE]') continue;
|
|
41
|
+
try {
|
|
42
|
+
messages.push(JSON.parse(data));
|
|
43
|
+
} catch {
|
|
44
|
+
// A keep-alive or a partial event is not our response.
|
|
45
|
+
}
|
|
46
|
+
}
|
|
47
|
+
assert.ok(messages.length, `no JSON-RPC message in the response: ${raw.slice(0, 300)}`);
|
|
48
|
+
const match = messages.find((m) => m.id === id);
|
|
49
|
+
assert.ok(match, `no message with id ${id} in the response: ${raw.slice(0, 300)}`);
|
|
50
|
+
return match;
|
|
51
|
+
}
|
|
52
|
+
|
|
53
|
+
let nextId = 1;
|
|
54
|
+
|
|
55
|
+
async function rpc(method, params = {}) {
|
|
56
|
+
const id = nextId++;
|
|
57
|
+
const res = await fetch(ENDPOINT, {
|
|
58
|
+
method: 'POST',
|
|
59
|
+
headers: {
|
|
60
|
+
'x-api-key': KEY,
|
|
61
|
+
'Content-Type': 'application/json',
|
|
62
|
+
// The server answers over streamable HTTP, so accept both a plain body and a stream.
|
|
63
|
+
Accept: 'application/json, text/event-stream',
|
|
64
|
+
},
|
|
65
|
+
body: JSON.stringify({ jsonrpc: '2.0', id, method, params }),
|
|
66
|
+
signal: AbortSignal.timeout(TIMEOUT_MS),
|
|
67
|
+
});
|
|
68
|
+
assert.equal(res.status, 200, `${method} returned ${res.status}`);
|
|
69
|
+
const raw = await res.text();
|
|
70
|
+
return { raw, body: parseRpc(raw, id) };
|
|
71
|
+
}
|
|
72
|
+
|
|
73
|
+
// One network round trip for every test that needs the list.
|
|
74
|
+
let toolsPromise;
|
|
75
|
+
function listTools() {
|
|
76
|
+
toolsPromise ??= rpc('tools/list').then(({ body }) => {
|
|
77
|
+
assert.ok(body.result?.tools, 'the response carried no result.tools');
|
|
78
|
+
return body.result.tools;
|
|
79
|
+
});
|
|
80
|
+
return toolsPromise;
|
|
81
|
+
}
|
|
82
|
+
|
|
83
|
+
const live = { skip: KEY ? false : 'HASDATA_API_KEY is not set, skipping the live checks' };
|
|
84
|
+
|
|
85
|
+
test('apis=indeed exposes exactly two tools', live, async () => {
|
|
86
|
+
const tools = await listTools();
|
|
87
|
+
const names = tools.map((t) => t.name).sort().join(', ');
|
|
88
|
+
assert.equal(
|
|
89
|
+
tools.length,
|
|
90
|
+
Object.keys(EXPECTED).length,
|
|
91
|
+
`expected ${Object.keys(EXPECTED).length} tools, got ${tools.length}: ${names}`
|
|
92
|
+
);
|
|
93
|
+
});
|
|
94
|
+
|
|
95
|
+
test('the tool names have not changed', live, async () => {
|
|
96
|
+
const tools = await listTools();
|
|
97
|
+
const names = new Set(tools.map((t) => t.name));
|
|
98
|
+
for (const expected of Object.keys(EXPECTED)) {
|
|
99
|
+
assert.ok(names.has(expected), `tool ${expected} is missing from the list`);
|
|
100
|
+
}
|
|
101
|
+
});
|
|
102
|
+
|
|
103
|
+
test('every tool still declares its required parameter', live, async () => {
|
|
104
|
+
const tools = await listTools();
|
|
105
|
+
for (const tool of tools) {
|
|
106
|
+
const required = tool.inputSchema?.required ?? [];
|
|
107
|
+
const want = EXPECTED[tool.name];
|
|
108
|
+
assert.ok(want, `tool ${tool.name} is not covered by this test`);
|
|
109
|
+
for (const param of want) {
|
|
110
|
+
assert.ok(
|
|
111
|
+
required.includes(param),
|
|
112
|
+
`${tool.name} should require ${param}, declares: ${required.join(', ') || 'nothing'}`
|
|
113
|
+
);
|
|
114
|
+
}
|
|
115
|
+
}
|
|
116
|
+
});
|
|
117
|
+
|
|
118
|
+
test('every tool carries a description', live, async () => {
|
|
119
|
+
const tools = await listTools();
|
|
120
|
+
for (const tool of tools) {
|
|
121
|
+
assert.ok(
|
|
122
|
+
(tool.description || '').trim().length > 20,
|
|
123
|
+
`${tool.name} has an empty or near-empty description`
|
|
124
|
+
);
|
|
125
|
+
}
|
|
126
|
+
});
|
|
127
|
+
|
|
128
|
+
test('the key is accepted by HasData', live, async () => {
|
|
129
|
+
const { raw } = await rpc('tools/call', {
|
|
130
|
+
name: 'hasdata_indeed_listing_getJobListings',
|
|
131
|
+
arguments: { keyword: 'developer', location: 'New York, NY' },
|
|
132
|
+
});
|
|
133
|
+
assert.ok(!raw.includes('401 Unauthorized'), 'HasData rejected the key');
|
|
134
|
+
assert.ok(!raw.includes('"isError":true'), `the tool call failed: ${raw.slice(0, 300)}`);
|
|
135
|
+
});
|