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.

Six Figure Work

REMOTE · SIXFIGUREWORK.COM

Read-only jobs server: $100K+ base-pay roles, each with the employer's own pay evidence and source.

+3 this week 73 Trust /100

Last scanned (13 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

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 Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 769 tokens (~153/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
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_stats" 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

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

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.

  • 20 Nov 26 +1

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

  • 17 Nov 26 +1
    • Tool “get_employer” rewrote its description, which is the text the model reads security
    • Schema quality: 137 → 153 ▼ functional
    • “get_employer” reworded the description of “id” cosmetic
    • “get_employer” reworded the description of “slug” cosmetic
    • “get_job” reworded the description of “id” cosmetic
  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 11 Nov 26 +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.

  • 10 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 9 Nov 26 68

    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://sixfigurework.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=sixfigurework.com CN=YE1,O=Let's Encrypt,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA384 52c7645ad9ff29c6dcb98105d4e472dcd83
SANs: *.sixfigurework.com, sixfigurework.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sixfigurework.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
sixfigurework.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
Header Value
content-security-policy default-src 'self'; script-src 'self' https://www.googletagmanager.com 'sha256-rWfJeQ3WvVKAeQNr2z41/Za0RbZyCl3hE8VzGMZXnIo='; style-src 'self'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; font-src 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; object-src 'none'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interstitial-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sixfigurework.com/mcp Verified 200
http (plaintext) http://sixfigurework.com/mcp HTTPS enforced 301 https://sixfigurework.com/mcp
MCP tools · 5 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_employer ~144

An employer's live six-figure postings (highest published floors first, up to 10), pay summary and how fresh its job sources are. Give exactly one of: id (the `employer_id` from a search_jobs or get_job result) or slug (the /companies/<slug> part, e.g. 'amazon'). Company names are not ids.

NameTypeReqDescription
idstring–Employer UUID: the `employer_id` field of a search_jobs result. Use this OR slug.
slugstring–Company slug from a /companies/<slug> URL, lowercase with hyphens, e.g. 'amazon'. Use this OR id.

No output schema declared.

No examples provided.

get_job ~105

One job by id (or sixfigurework.com job URL): published pay per location, the exact employer text the pay was read from, when it was last confirmed, where it sits among comparable jobs, and the employer's own posting link.

NameTypeReqDescription
idstringyesJob id: the `id` field of a search_jobs result (a UUID), or that job's sixfigurework.com /jobs/<title>-<uuid> URL. Not a title or employer name.

No output schema declared.

No examples provided.

list_filters ~35

The valid categories, states, metro areas, seniority levels, workplace types, sorts and limits that search_jobs and pay_stats accept.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pay_stats ~86

Median and quartiles of employer-published starting base pay, with the sample size N, for a job family, a state, both, or the whole site. Describes six-figure postings only, not what the market pays.

NameTypeReqDescription
categorystring–Job family id or name, e.g. software_engineering.
statestring–US state code or name.

No output schema declared.

No examples provided.

search_jobs ~267

Search live jobs where the employer has published an annual base salary of $100,000 or more. Returns up to 25 jobs per call with pay range, location, employer and sixfigurework.com URLs to cite. Not the whole labor market: only employer-published $100K+ base.

NameTypeReqDescription
categorystring–Job family id or name, e.g. software_engineering or 'Finance & Accounting'. See list_filters.
cursorstring–next_cursor from a previous call with the same filters.
limitinteger––
metrostring–Metro area id or name, e.g. 'new-york-ny' or 'Denver'. See list_filters.
min_salaryinteger–Only jobs whose published base minimum is at least this many dollars.
qstring–Free-text search over titles and descriptions, e.g. 'staff data engineer'.
senioritystring–entry, mid, senior, staff_principal, manager, director, vp_exec, intern, unknown.
sortstring–Default: relevance when q is set, else highest_min.
statestring–US state code or name, e.g. 'ca' or 'California'.
workplacestring––

No output schema declared.

No examples provided.

Install

How do I install the Six Figure Work MCP server?

Six Figure Work is a hosted endpoint at https://sixfigurework.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 · sixfigurework.com

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

What is the Six Figure Work MCP server?

Six Figure Work is an MCP server listed in the public MCP registry as com.sixfigurework/jobs. Read-only jobs server: $100K+ base-pay roles, each with the employer's own pay evidence and source. This page covers its hosted endpoint (https://sixfigurework.com/mcp).

Is the Six Figure Work MCP server safe to use?

Six Figure Work 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 Six Figure Work MCP server expose?

Six Figure Work exposes 5 tools: search_jobs, get_job, get_employer, pay_stats, list_filters. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.

Does the Six Figure Work MCP server require authentication?

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

Is the Six Figure Work MCP server still maintained?

Six Figure Work 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 Six Figure Work MCP server?

VerifyMCP ran 13 checks on Six Figure Work, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.