Jobvetta MCP Server
REMOTE · API.JOBVETTA.COM · SCANNED AUG 5
Search live, vetted India jobs by keyword, location, posting age, and job ID.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 160 tokens (~80/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.jobvetta.com
claude mcp add --transport http jobvetta-job-search https://api.jobvetta.com/mcp
[mcp_servers.jobvetta-job-search] url = "https://api.jobvetta.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jobvetta-job-search": {
"type": "remote",
"url": "https://api.jobvetta.com/mcp",
"enabled": true
}
}
} openclaw mcp add jobvetta-job-search --url https://api.jobvetta.com/mcp --transport streamable-http
mcp_servers:
jobvetta-job-search:
url: "https://api.jobvetta.com/mcp" {
"mcpServers": {
"jobvetta-job-search": {
"type": "http",
"url": "https://api.jobvetta.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 5 Aug 26 71
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 5 Aug 2026 · Probed https://api.jobvetta.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jobvetta.com | CN=WE1,O=Google Trust Services,C=US | 8 Jul 2026 | 6 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | d23f87b58c98b6c3138ed401613286c2 |
| SANs: jobvetta.com, api.jobvetta.com, *.api.jobvetta.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.jobvetta.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jobvetta.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.jobvetta.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.jobvetta.com/mcp | HTTPS enforced | 301 | https://api.jobvetta.com/mcp |
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.
get_job ~37
Full details for one job (description, qualifications, salary, metadata) by job_id from search_jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | — |
No output schema declared.
No examples provided.
search_jobs ~123
Search live job openings across India, checked at official employer sources. India only — non-Indian locations return no results. Returns up to 10 jobs per call with title, company, location, and a jobvetta URL.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | — | Only jobs posted within the last N days (e.g. 2) |
| limit | number | — | Max results (1-10, default 10) |
| location | string | — | Indian city, town, or state (India only) |
| q | string | — | Role, skill, or company keywords |
No output schema declared.
No examples provided.