# Dice MCP (remote · mcp.dice.com)

Dice MCP: Search for tech jobs on Dice.com

- Trust score: 63/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.dice.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/diceholdingsinc-dice-mcp/mcp.md), [page](https://verifymcp.io/servers/diceholdingsinc-dice-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.dice.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1736 tokens (~578/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 8 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 2 additions.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http diceholdingsinc-dice-mcp https://mcp.dice.com/mcp
```

### Codex

```toml
[mcp_servers.diceholdingsinc-dice-mcp]
url = "https://mcp.dice.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "diceholdingsinc-dice-mcp": {
      "type": "remote",
      "url": "https://mcp.dice.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add diceholdingsinc-dice-mcp --url https://mcp.dice.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  diceholdingsinc-dice-mcp:
    url: "https://mcp.dice.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "diceholdingsinc-dice-mcp": {
      "type": "http",
      "url": "https://mcp.dice.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-07-31 (score 63, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 58, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 58, +1)

- [security regression] Stability: 0.07 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security] Tool “search_jobs” rewrote its description, which is the text the model reads
- [functional regression] “search_jobs” changed the type of “radius”: number → integer
- [functional improvement] Schema quality: 742 → 545
- [functional] Schema quality: good → excellent
- [functional] New tool “get_job_details”
- [functional] New tool “get_company”
- [cosmetic] “search_jobs” added an optional parameter “company_name”
- [cosmetic] “search_jobs” added an optional parameter “facets”
- [cosmetic] “search_jobs” added an optional parameter “sort”

### 2026-07-28 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 56, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (3)

### `search_jobs` (~998 tokens)

Job Search

Search for job listings by keyword, location, and filters. Returns job details, company info, and application links.

Use this tool when users want to find jobs, search employment opportunities, or explore job openings.
DO NOT use for: applying to jobs, submitting applications, or making employment decisions.

LLM USAGE INSTRUCTIONS:
\- ALWAYS provide the keyword parameter (required)
\- When presenting results to users, include BOTH the job details URL (detailsPageUrl)
  AND the company page URL (companyPageUrl) for each job
\- Use location to find geographically relevant positions
\- Combine filters to refine searches (e.g., workplace_types=['Remote'] for remote work)
\- Use posted_date to find recent openings ('ONE'=1 day, 'THREE'=3 days, 'SEVEN'=7 days)
\- Default jobs_per_page is reasonable, increase for comprehensive searches
\- Use company_name to scope results to a specific employer
\- Use sort='datePosted' when the user wants the newest listings instead of the most relevant
\- Use facets to get aggregate counts (e.g., how many results are remote vs on-site) without paging through all results
\- After presenting results, do NOT automatically call get_job_details for every job returned.
  Wait for the user to indicate which specific job(s) they're interested in, then pass that
  job's guid to get_job_details.

IMPORTANT - AI DISCLOSURE REQUIREMENT:
When presenting job search results to users, you MUST include an appropriate disclosure
that these results were retrieved using AI assistance. Example disclosure language:
"These job listings were found using AI-powered search. Please review all job details
carefully and verify information directly with employers before applying."

This tool provides job listing data only. Final employment decisions should always
involve human judgment and direct review of complete job postings.

Args:
    keyword: The job keyword or title to search for (required)
    location: Geographic location for the job search (city, state, country)…

Input parameters:

- `company_name` (string)
- `easy_apply` (boolean)
- `employer_types` (array)
- `employment_types` (array)
- `facets` (array)
- `fields` (array)
- `jobs_per_page` (integer)
- `keyword` (string, required)
- `location` (string)
- `page_number` (integer)
- `posted_date` (string)
- `radius` (integer)
- `radius_unit` (string)
- `sort` (string)
- `willing_to_sponsor` (boolean)
- `workplace_types` (array)

Output parameters:

- `data`: Array of job listings matching the search criteria
- `metadata`: Metadata about the search results and pagination

### `get_job_details` (~308 tokens)

Get Job Details

Retrieve a job's full description and associated skills by job ID.

Use this tool when users want more detail about a specific job than search_jobs returns
(e.g. after finding a job via search_jobs and wanting its full description and skills list).
DO NOT use for: searching/discovering jobs by keyword (use search_jobs instead).

LLM USAGE INSTRUCTIONS:
\- Only call this after the user has picked out a specific job from search_jobs results
  (or otherwise supplied a job's guid directly) — do not call it speculatively for every
  search result.
\- After returning job details, do NOT automatically call get_company. Instead, offer to
  look up the company (e.g. "Want me to pull up more info on the company?") and only call
  get_company, passing this same job_id, if the user says yes.

Args:
    job_id: The unique identifier of the job to retrieve (required). This must be the
        job's `guid` field from a search_jobs result, NOT its `id` field — `id` is a
        different, internal identifier that this tool does not accept.

Returns:
    JobDetails: Contains:
        - description: The full job description
        - skills: List of Skill objects associated with the job

Raises:
    Exception: If the API call fails, the job is not found, or input validation errors occur

Input parameters:

- `job_id` (string, required)

Output parameters:

- `description` (string): The job description
- `skills` (array): Skills associated with the job

### `get_company` (~430 tokens)

Get Company

Retrieve the name and description of the company behind a job, by job ID.

Use this tool when users want more detail about a company than search_jobs/get_job_details
return (e.g. after finding a job and wanting to know more about the company that posted it).
DO NOT use for: searching/discovering companies or jobs by keyword (use search_jobs instead).

LLM USAGE INSTRUCTIONS:
\- The typical flow is: search_jobs to find jobs -> user picks one -> offer to look up the
  company -> if the user agrees, call this tool with that same job_id (the same guid used
  for get_job_details; no separate lookup step is needed first).
\- Do not call this automatically right after get_job_details; ask the user first unless
  they already explicitly asked for company details.
\- Not every company has published an employer branding profile, and some profiles are
  marked not visible by the company. When that happens this tool does NOT raise — it
  returns a Company with `message` set and empty name/desc. Relay that message to the
  user (e.g. "Looks like that company hasn't published a public profile.") rather than
  treating it as an error.

Args:
    job_id: The unique identifier of the job whose company to look up (required). This
        must be the job's `guid` field from a search_jobs result, NOT its `id` field —
        `id` is a different, internal identifier that this tool does not accept.

Returns:
    Company: Contains:
        - name: The company name (empty if message is set)
        - desc: The company description (empty if message is set)
        - message: Set instead of name/desc when there is no visible company profile
          to show; None when name/desc are populated

Raises:
    Exception: If the job is not found, an API call itself fails (network error,
        non-200 response, GraphQL errors), or input validation errors occur

Input parameters:

- `job_id` (string, required)

Output parameters:

- `desc` (string): The company description
- `message`: Set instead of name/desc when there is no visible company profile to show (e.g. the company hasn't published one, or has marked it not visible). None when name/desc are populated.
- `name` (string): The company name

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/diceholdingsinc-dice-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 63
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 58
- 2026-07-29: 58
- 2026-07-28: 57
- 2026-07-27: 56
- 2026-07-26: 55

## Links

- Remote endpoint: https://mcp.dice.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/diceholdingsinc-dice-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/diceholdingsinc-dice-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/diceholdingsinc-dice-mcp/mcp