Seeker
REMOTE · WWW.SEEKERSCORE.COM
Match a résumé to live job postings: the top 5 open roles with fit labels and links.
Available components
Last scanned (14 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 375 tokens (~187/item across 2 items; 2 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 Management47
- Stability observed for 14 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 →
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
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 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.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_resume_against_job” rewrote its description, which is the text the model reads security
- Tool “match_resume” rewrote its description, which is the text the model reads security
- Schema quality: 214 → 187 ▲ functional
- Stability: unverified → 0.03 ▲ functional
- 7 Nov 26 73
First indexed and scored.
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://www.seekerscore.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.seekerscore.com | CN=YR1,O=Let's Encrypt,C=US | 11 Oct 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 5619caec4d161917b234a0f020e3b1679da |
| SANs: www.seekerscore.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.seekerscore.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| seekerscore.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; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.seekerscore.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.seekerscore.com/mcp | HTTPS enforced | 308 | https://www.seekerscore.com/mcp |
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 →
check_resume_against_job Check résumé against a job posting ~161
Use when the user shares their résumé text AND one job description and asks how well they fit that job or what is missing. Sends both texts to Seeker (seekerscore.com), which compares the skills in each and returns the skill overlap percentage, the matched skills, the required and preferred skills the résumé does not show, and whether the experience level looks under, at or over the posting. It is a skills comparison, not a prediction of interviews or hiring.
| Name | Type | Req | Description |
|---|---|---|---|
| job_description | string | yes | The full text of the job posting, 200 to 20000 characters. |
| resume_text | string | yes | The full plain text of the user's résumé, 200 to 50000 characters. Phone number and home address can be left out. |
| Name | Type | Req | Description |
|---|---|---|---|
| checker_url | string | yes | – |
| level_fit | string | yes | – |
| matched_skills | array | yes | – |
| missing_preferred | array | yes | – |
| missing_required | array | yes | – |
| overlap_pct | number | yes | – |
| resume_years | number|null | – | – |
| years_required | number|null | – | – |
No examples provided.
match_resume Match résumé to live jobs ~153
Use when the user shares their résumé (or CV) text and wants to see real, currently open jobs that fit it. Sends the résumé text to Seeker (seekerscore.com), which compares it with its live job postings and returns the top 5 matches with title, company, location, a fit label, a short reason and the posting link, plus a link to see all matches on Seeker. Fit labels describe how well the résumé matches each posting; they are not predictions of interviews or hiring. Matching can take up to a minute.
| Name | Type | Req | Description |
|---|---|---|---|
| resume_text | string | yes | The full plain text of the user's résumé, 200 to 50000 characters. Phone number and home address can be left out. |
| Name | Type | Req | Description |
|---|---|---|---|
| matches | array | yes | – |
| see_all_url | string | yes | – |
No examples provided.
How do I install the Seeker MCP server?
Seeker is a hosted endpoint at https://www.seekerscore.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 · www.seekerscore.com
claude mcp add --transport http com-seekerscore-seeker 'https://www.seekerscore.com/mcp'
What is the Seeker MCP server?
Seeker is an MCP server listed in the public MCP registry as com.seekerscore/seeker. Match a résumé to live job postings: the top 5 open roles with fit labels and links. This page covers its hosted endpoint (https://www.seekerscore.com/mcp).
Is the Seeker MCP server safe to use?
Seeker scores 80 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 Seeker MCP server expose?
Seeker exposes 2 tools: match_resume, check_resume_against_job. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.
Does the Seeker MCP server require authentication?
No. We connected to Seeker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Seeker MCP server still maintained?
Seeker 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 Seeker MCP server?
VerifyMCP ran 13 checks on Seeker, 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.