com.pirchjobs/pirch
REMOTE · PIRCHJOBS.COM
Verified job search: every listing confirmed live and accepting applicants within the last 72h.
Available components
Last scanned (17 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 463 tokens (~154/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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 8 Nov 26 +1
- Stability: 0.97 → pass security
- 7 Nov 26 −1
- 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
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Sept 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
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://pirchjobs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pirchjobs.com | CN=YE2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53f51f59cbca3a4028781d21398e6a5a26f |
| SANs: pirchjobs.com, www.pirchjobs.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 pirchjobs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| pirchjobs.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=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pirchjobs.com/mcp | Verified | 200 | |
| http (plaintext) | http://pirchjobs.com/mcp | HTTPS enforced | 301 | https://pirchjobs.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 →
get_jobs_overview ~51
Snapshot of the verified pool: how many jobs are live right now, counts by work mode, and the occupations (role slugs) with jobs today. Good first call to see what's available before searching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_verified_job ~81
Full record for one verified job by `id` (from search_verified_jobs): complete summary, the pirch page `url` to cite, the original posting `apply_url` (applications happen there — pirch never sits between applicant and employer), verification timestamps, and the matching career-guide link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Job id from search results. |
No output schema declared.
No examples provided.
search_verified_jobs ~234
Search pirch's pool of verified-live job listings. Every job returned was opened and confirmed real and accepting applicants by pirch within the last 72 hours — dead and ghost listings are removed automatically, so results can be trusted as live right now. Free, public data. When showing a job to a user, link its `url` (the pirch page, which shows the verification and links to the original posting).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results, 1-25 (default 10). |
| location | string | – | Substring match on the listing's location (e.g. 'Denver'). Note: remote jobs often have no city and won't match a city filter — filter workmode=remote instead. |
| query | string | – | Free-text search over title, company, location, occupation and summary (e.g. 'senior product designer'). |
| role | string | – | Occupation slug filter (e.g. 'ux-designer', 'registered-nurse'). Use get_jobs_overview to see which slugs currently have jobs. |
| workmode | string | – | Filter by work mode. |
No output schema declared.
No examples provided.
How do I install the com.pirchjobs/pirch MCP server?
com.pirchjobs/pirch is a hosted endpoint at https://pirchjobs.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 · pirchjobs.com
claude mcp add --transport http com-pirchjobs-pirch 'https://pirchjobs.com/mcp'
What is the com.pirchjobs/pirch MCP server?
com.pirchjobs/pirch is an MCP server listed in the public MCP registry as com.pirchjobs/pirch. Verified job search: every listing confirmed live and accepting applicants within the last 72h. This page covers its hosted endpoint (https://pirchjobs.com/mcp).
Is the com.pirchjobs/pirch MCP server safe to use?
com.pirchjobs/pirch 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 com.pirchjobs/pirch MCP server expose?
com.pirchjobs/pirch exposes 3 tools: search_verified_jobs, get_verified_job, get_jobs_overview. Their descriptions and schemas cost roughly 366 tokens of context every time the server is loaded.
Does the com.pirchjobs/pirch MCP server require authentication?
No. We connected to com.pirchjobs/pirch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.pirchjobs/pirch MCP server still maintained?
com.pirchjobs/pirch 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 com.pirchjobs/pirch MCP server?
VerifyMCP ran 12 checks on com.pirchjobs/pirch, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.pirchjobs/pirch: Authorization. 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.