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.

Find your role first

REMOTE · FINDYOURROLEFIRST.CLICK

Jobs from 15,000+ company career sites, newest first. Agents can search, save, track and set alerts.

0 this week 36 Trust /100

Last scanned (14 hours ago)

Scores higher than 19% 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 Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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.

  • 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
  • 10 Oct 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Authorization: partial → pass ▲ security
    • First check of Authorization: partial security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 7 Oct 26 0
    • Schema quality: 255 → 206 ▲ functional
    • New tool “get_apply_kit” functional
    • New tool “get_my_profile” functional
    • New tool “get_new_for_me” functional
  • 2 Oct 26 0
    • Tool “search_jobs” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “count_jobs” reworded the description of “experience” cosmetic
    • “search_jobs” reworded the description of “experience” cosmetic
  • 1 Oct 26 0
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Authorization: fail → partial ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • First check of Tool coverage: 100 functional
  • 29 Sept 26 0

    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://findyourrolefirst.click/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=findyourrolefirst.click CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 69f61d4f7df820eb13c675fd79f24fc1
SANs: findyourrolefirst.click, roles.findyourrolefirst.click, *.roles.findyourrolefirst.click
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 findyourrolefirst.click. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
click. DS published 65517 13 Verified
findyourrolefirst.click. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On connection
HTTP status 401

WWW-Authenticate challenge Bearer resource_metadata="https://findyourrolefirst.click/.well-known/oauth-protected-resource", scope="jobs"

Bearer resource_metadata="https://findyourrolefirst.click/.well-known/oauth-protected-resource", scope="jobs"
Header Value
www-authenticate Bearer resource_metadata="https://findyourrolefirst.click/.well-known/oauth-protected-resource", scope="jobs"

Protected resource metadata

Document https://findyourrolefirst.click/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://findyourrolefirst.click/mcp
Authorisation server https://findyourrolefirst.click

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://findyourrolefirst.click/mcp Auth required 401
http (plaintext) http://findyourrolefirst.click/mcp HTTPS enforced 301 https://findyourrolefirst.click/mcp
MCP tools · 9 exposed · ~1,699 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
count_jobs ~385

Count the roles a search_jobs call would match, up to 1,000. Free: no jobs returned, no credits used. Use it to narrow a search (add a location, exclude words, posted_within_hours) before paying for results.

NameTypeReqDescription
excludestring–Leave out titles containing any of these words, e.g. "senior staff intern".
experiencearray–Years of experience the posting asks for; any of "0-1", "1-3", "3-5", "5-8", "8+", "not_stated" (we read the posting and it names none) and "unchecked" (not read yet, or no text to read: many big-com…
familystring–"product_adjacent" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it.
locationstring–One country ("United States", "UK", "India"), or a city or state as written. Empty for anywhere.
locationsarray–Several places at once, matching any, e.g. ["United States", "London", "Remote"]. Up to 8.
posted_within_hoursinteger–Only roles posted within this many hours; 0 for any time.
querystring–Whole words matched in the title or company, e.g. "product manager" or "quant". Empty for any.
remoteboolean–Only remote roles.
rolesarray–Several titles at once, matching any, e.g. ["Product Manager", "Software Engineer"]. Up to 40.
sourcestring–Only roles from one source (gh is Greenhouse), or "any".

Structured output declared, but exposes no named fields.

No examples provided.

get_apply_kit ~130

Everything needed to help the person apply to one role themselves: the apply link, the application form's questions when the careers site publishes them (every Greenhouse role does), what we know about the role (experience asked for, level, pay, place, dates) and a short checklist. Draft answers and tailor the résumé with the person; they submit. This service never submits applications. Uses a credit like get_job if not unlocked.

NameTypeReqDescription
job_idstringyesA job id from search results, e.g. "gh:stripe:1234567".

Structured output declared, but exposes no named fields.

No examples provided.

get_changes ~93

Get new, updated, reopened, and closed jobs. Save next_cursor for the next check. Excludes baseline imports. History lasts 90 days; expired cursors need a fresh search.

NameTypeReqDescription
cursorinteger–next_cursor from your last get_changes call; 0 starts from the beginning of the 90-day history.
limitinteger–How many to return, 1 to 20.

Structured output declared, but exposes no named fields.

No examples provided.

get_job ~92

Get a job's metadata, original posting and application URLs, and latest known status. No job description is returned. Search already includes these fields; use this to refresh one record. Check closed_at and last_checked before applying. Reading the source page needs a separate web tool.

NameTypeReqDescription
job_idstringyesA job id from search results, e.g. "gh:stripe:1234567".

Structured output declared, but exposes no named fields.

No examples provided.

get_my_profile ~68

What this person told Find your role first they want: name, where they live, the roles (whole fields like "Software engineering" or titles), places, remote-only, experience, and what their résumés suggested. Use it to search on their behalf. Free.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_new_for_me ~127

Roles matching this person's saved preferences that were found since `since` (ISO time), newest found first. Leave since empty for the last 24 hours. Save checked_at from the reply and pass it as since next time: a daily or hourly check then never repeats a role. Uses credits like search_jobs for roles not unlocked this month.

NameTypeReqDescription
limitinteger–Results per page, 1 to 20.
sincestring–ISO date or time: only roles we first found on or after it, excluding baseline imports. Empty for any.

Structured output declared, but exposes no named fields.

No examples provided.

get_usage ~22

Check your remaining monthly allowance. This tool doesn't use your data allowance.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_my_jobs ~62

List roles this account already unlocked, newest first. Free, and doesn't use credits.

NameTypeReqDescription
limitinteger–How many to return, 1 to 100.
offsetinteger–Skip this many results; pass next_offset from the previous page.

Structured output declared, but exposes no named fields.

No examples provided.

search_jobs ~720

Find open jobs checked within 24 hours. Up to 20 results, newest posted first. query matches whole words in the title or company (e.g. "product manager", "quant", "ml engineer"). location takes a country ("United States", "UK", "India") or a city or state as written. exclude drops titles containing any of these words ("senior staff intern"). remote=true keeps remote roles only. posted_within_hours keeps recent postings. Call count_jobs first (free) to size a search before spending credits. Use published_since for source dates and discovered_since for new discoveries excluding baselines. Follow next_offset to paginate. No JD text is returned. experience keeps roles whose posting asks for these years of experience: any of "0-1", "1-3", "3-5", "5-8", "8+", "not_stated" (read, names none), "unchecked" (not read, or no text). Read from each posting; include not_stated and unchecked unless you mean to drop those roles. family="product_adjacent" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it. roles takes several titles at once (["Product Manager", "Software Engineer"]) and matches any; locations likewise (["United States", "London", "Remote"]).

NameTypeReqDescription
discovered_sincestring–ISO date or time: only roles we first found on or after it, excluding baseline imports. Empty for any.
excludestring–Leave out titles containing any of these words, e.g. "senior staff intern".
experiencearray–Years of experience the posting asks for; any of "0-1", "1-3", "3-5", "5-8", "8+", "not_stated" (we read the posting and it names none) and "unchecked" (not read yet, or no text to read: many big-com…
familystring–"product_adjacent" finds product, product marketing, growth, customer success, forward deployed and business operations titles in one search; query narrows within it.
limitinteger–Results per page, 1 to 20.
locationstring–One country ("United States", "UK", "India"), or a city or state as written. Empty for anywhere.
locationsarray–Several places at once, matching any, e.g. ["United States", "London", "Remote"]. Up to 8.
offsetinteger–Skip this many results; pass next_offset from the previous page.
posted_within_hoursinteger–Only roles posted within this many hours; 0 for any time.
published_sincestring–ISO date or time: only roles the company dated on or after it. Empty for any.
querystring–Whole words matched in the title or company, e.g. "product manager" or "quant". Empty for any.
remoteboolean–Only remote roles.
rolesarray–Several titles at once, matching any, e.g. ["Product Manager", "Software Engineer"]. Up to 40.
sourcestring–Only roles from one source (gh is Greenhouse), or "any".

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Find your role first MCP server?

Find your role first is a hosted endpoint at https://findyourrolefirst.click/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 · findyourrolefirst.click

# add to Claude Code
claude mcp add --transport http click-findyourrolefirst-jobfeed 'https://findyourrolefirst.click/mcp'
Common questions

What is the Find your role first MCP server?

Find your role first is an MCP server listed in the public MCP registry as click.findyourrolefirst/jobfeed. Jobs from 15,000+ company career sites, newest first. Agents can search, save, track and set alerts. This page covers its hosted endpoint (https://findyourrolefirst.click/mcp).

Is the Find your role first MCP server safe to use?

Find your role first scores 36 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 Find your role first MCP server expose?

Find your role first exposes 9 tools: search_jobs, get_job, get_changes, count_jobs, list_my_jobs, and 4 more. Their descriptions and schemas cost roughly 1,699 tokens of context every time the server is loaded.

Does the Find your role first MCP server require authentication?

Yes. Find your role first asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Find your role first MCP server still maintained?

Find your role first 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 Find your role first MCP server?

VerifyMCP ran 5 checks on Find your role first, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Find your role first: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.