Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DomDom Jobs

REMOTE · DOMDOMJOBS.COM

Jobs from employers' own pages: robot training, remote nursing, UX, legal, veterans and side work.

Available components

+3 this week 73 Trust /100

Last scanned (15 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 836 tokens (~167/item across 5 items; 4 tools + 1 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 Management30
  • Stability observed for 9 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_snapshot" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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
    • The server rewrote its instructions, which are the text every model session reads security
  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 0
    • Resource “domdom-jobs” now points somewhere else: ui://widget/domdom-v1.html → ui://widget/domdom-v2.html security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_jobs” rewrote its description, which is the text the model reads security
  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Nov 26 +4
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 200 → 165 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • First check of Schema quality: 100 functional
    • New resource “domdom-jobs” functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 12 Nov 26 65

    First indexed and scored.

Diagnostics

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 · Probed https://domdomjobs.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=domdomjobs.com CN=WE1,O=Google Trust Services,C=US 11 Nov 2026 9 Feb 2027 ECDSA 256 ECDSA-SHA256 cdcffbc3a6890a713a7cb4ba55e1614
SANs: domdomjobs.com, legal.domdomjobs.com, *.legal.domdomjobs.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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of domdomjobs.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
domdomjobs.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://domdomjobs.com/mcp Verified 200
http (plaintext) http://domdomjobs.com/mcp HTTPS enforced 301 https://domdomjobs.com/mcp
MCP tools · 4 exposed · ~637 tokens

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 →

Tool Tokens
get_company ~83

One employer's open jobs on DomDom Jobs: how many per board, posted pay, its company pages, open jobs by day for the last 30 days, and its newest jobs.

NameTypeReqDescription
companystringyesEmployer name or slug, e.g. "Mercor", "Hinge Health".
limitinteger–Jobs to return, default 10.

No output schema declared.

No examples provided.

list_boards ~41

The DomDom Jobs boards and the types of work on each (the type values search_jobs takes), with open job counts from the nightly build and their URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pay_snapshot ~135

What jobs on one DomDom Jobs board pay, overall and per type of work: the pay sentence the board prints, the range most posted rates fall in (hourly and yearly kept apart) and how many jobs post pay. Pay as employers post it, estimates left out.

NameTypeReqDescription
boardstring–home searches every board; the others are robots, healthcare, ux, moonlight, veterans and legal.
typestring–Type of work: a hub key on the chosen board, e.g. nurses (healthcare), lawyers (legal), weekends (moonlight), operator (robots). See list_boards.

No output schema declared.

No examples provided.

search_jobs ~378

Search open jobs on DomDom Jobs: robot training and teleoperation (robots), remote nursing, telehealth and therapy (healthcare), UX research and design (ux), side jobs for evenings and weekends (moonlight), jobs for veterans (veterans) and remote legal work (legal). Filter names match the boards' own filters. Returns each job's DomDom page (hub_url), the employer's application link, pay as posted, and a browse_url that opens the same filtered list on the board. Newest first, at most two jobs per employer at the top. Every keyword must appear in the title or employer, so use one to three words.

NameTypeReqDescription
boardstring–home searches every board; the others are robots, healthcare, ux, moonlight, veterans and legal.
employerstring–Employer name or slug, e.g. "Mercor" or "mercor".
employmentstring–Employment type, where the posting states one.
fieldstring–Field of work.
limitinteger–Jobs to return, default 10.
paystring–Hourly jobs whose top posted rate reaches this many US dollars an hour.
postedstring–Only jobs posted in the last 7 days.
querystring–Words to match in the job title or employer name, e.g. "ICU", "paralegal".
typestring–Type of work: a hub key on the chosen board, e.g. nurses (healthcare), lawyers (legal), weekends (moonlight), operator (robots). See list_boards.
wherestring–Remote or on-site.
whostring–Who can apply to a remote job: US only, the countries the posting names, or worldwide.

No output schema declared.

No examples provided.

Install

How do I install the DomDom Jobs MCP server?

DomDom Jobs is a hosted endpoint at https://domdomjobs.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · domdomjobs.com

# add to Claude Code
claude mcp add --transport http com-domdomjobs-jobs 'https://domdomjobs.com/mcp'
Common questions

What is the DomDom Jobs MCP server?

DomDom Jobs is an MCP server listed in the public MCP registry as com.domdomjobs/jobs. Jobs from employers' own pages: robot training, remote nursing, UX, legal, veterans and side work. This page covers its hosted endpoint (https://domdomjobs.com/mcp).

Is the DomDom Jobs MCP server safe to use?

DomDom Jobs scores 73 out of 100 on VerifyMCP. 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 DomDom Jobs MCP server expose?

DomDom Jobs exposes 4 tools: search_jobs, list_boards, pay_snapshot, get_company. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.

Does the DomDom Jobs MCP server require authentication?

No. We connected to DomDom Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DomDom Jobs MCP server still maintained?

DomDom Jobs 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 did VerifyMCP test on the DomDom Jobs MCP server?

VerifyMCP ran 14 checks on DomDom Jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.