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.

Theyond

REMOTE · THEYOND.COM

Live jobs from employer career pages. Read-only. Hit Apply on theyond.com. You land on the employer.

Available components

0 this week 83 Trust /100

Last scanned (20 hours ago)

Scores higher than 83% 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 Security80
  • 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
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 808 tokens (~269/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Stability: 0.97 → pass security
  • 3 Nov 26 +1

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

  • 2 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_job” rewrote its description, which is the text the model reads security
    • Tool “hiring_now” rewrote its description, which is the text the model reads security
    • Tool “search_jobs” rewrote its description, which is the text the model reads security
    • Schema quality: 238 → 269 ▼ functional
    • “search_jobs” reworded the description of “new” cosmetic
    • “search_jobs” reworded the description of “remote” cosmetic
    • “search_jobs” reworded the description of “seniority” cosmetic
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
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://theyond.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=theyond.com CN=WE1,O=Google Trust Services,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA256 6191fb6296a05a8213da2eca68fa2df8
SANs: theyond.com, *.theyond.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 theyond.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
theyond.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
strict-transport-security max-age=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://theyond.com/mcp Verified 200
http (plaintext) http://theyond.com/mcp HTTPS enforced 301 https://theyond.com/mcp
MCP tools · 3 exposed · ~598 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_job ~119

Use after search_jobs or hiring_now when the user picked one job. Pass that job's url from search_jobs or hiring_now (or its slug). Do not use this to search. Plain-text description, cut at 2000 characters when description_truncated is true. Cite hub URLs on the card. No employer apply URL.

NameTypeReqDescription
slugstring–Job slug from search_jobs or hiring_now. Use if you don't have the URL.
urlstring–The theyond.com job URL from search_jobs or hiring_now. Prefer this.

No output schema declared.

No examples provided.

hiring_now ~87

What's new on theyond.com with no keyword. Hiring now companies, plus up to 10 just-added jobs. job_count is how many were just added. Show the theyond.com URLs you were given, including title_hub_url, location_hub_url, or location_title_hub_url when present. Not posted_at, not an employer apply URL. Empty when nothing was just added.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_jobs ~392

Find live jobs when the user has a keyword, place, company, remote, and/or seniority, not a theyond job URL (use get_job for that). Need q, location, company, remote=true, seniority, or new=true. new=true searches just-added jobs on homepage Hiring now (same set as hiring_now), still max 10. Not posted_at. Returns at most 10 theyond.com pages, no pagination, no employer apply URLs. Cite title_hub_url, location_hub_url, or location_title_hub_url when the card includes them. Do not invent a hub slug. theyond_verified_at is when theyond last saw the listing on the employer board, not the posted date. salary is the employer feed wage, or the amount harvested from the JD when the feed had none. People apply from the theyond page.

NameTypeReqDescription
companystring–Employer name, case-insensitive. nvidia matches NVIDIA. Optional if q, location, remote, seniority, or new is set.
locationstring–City, region, or country. Optional if q, company, remote, seniority, or new is set.
newboolean–If true, only just-added jobs on homepage Hiring now (same set as hiring_now). Still max 10. Can be the only filter. Not posted_at.
qstring–Keywords for title, company, or description. Optional if location, company, remote, seniority, or new is set. Do not pass a theyond.com/jobs URL here.
remoteboolean–If true, only remote jobs. The title or location says remote, or the description was read as remote. Combine with q or company.
senioritystring–If set, only jobs at that level: intern, entry, mid, senior, staff_lead, or director.

No output schema declared.

No examples provided.

Install

How do I install the Theyond MCP server?

Theyond is a hosted endpoint at https://theyond.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 · theyond.com

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

What is the Theyond MCP server?

Theyond is an MCP server listed in the public MCP registry as io.github.theyond/jobs. Live jobs from employer career pages. Read-only. Hit Apply on theyond.com. You land on the employer. This page covers its hosted endpoint (https://theyond.com/mcp).

Is the Theyond MCP server safe to use?

Theyond scores 83 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 Theyond MCP server expose?

Theyond exposes 3 tools: search_jobs, hiring_now, get_job. Their descriptions and schemas cost roughly 598 tokens of context every time the server is loaded.

Does the Theyond MCP server require authentication?

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

Is the Theyond MCP server still maintained?

Theyond 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 Theyond MCP server?

VerifyMCP ran 13 checks on Theyond, 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.