pirch MCP server
com.pirchjobs/pirchpirchjobs.comstreamable-httpv1.0.0Scanned
Verified job search: every listing confirmed live and accepting applicants within the last 72h.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the pirch MCP server can do
The pirch MCP server is published by pirchjobs.com, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (get_verified_job).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
get_jobs_overviewSnapshot of the verified pool: how many jobs are live right now, counts by work mode, and the occupations (role slugs) with jobs today.No findings
Why it is in this group
- The name "get_jobs_overview" says "get": a word for reading.
Description, as the server wrote it 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.
get_verified_jobFull 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 — …Reads text others writeNo findings
Why it is in this group
- The name "get_verified_job" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
search_verified_jobsSearch pirch's pool of verified-live job listings.No findings
Why it is in this group
- The name "search_verified_jobs" says "search": a word for reading.
Description, as the server wrote it 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).
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:44 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pirch https://pirchjobs.com/mcpclaude mcp add --transport http pirch https://pirchjobs.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pirch__search_verified_jobs",
"mcp__pirch__get_verified_job",
"mcp__pirch__get_jobs_overview"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pirch. Review it before you use it.
Capability tags behind 1 rule
- mcp__pirch__get_verified_job untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.pirchjobs/pirch/verify?hash=d687745438b84a0423f0dfcdd91995cd542b02a60a741a0cc21dd8b6aaf28517" | jq -e '.changed == false'Pinned hash d687745438b8, from Nov 14, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.pirchjobs/pirch/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.pirchjobs/pirch)Source: MCP Registry. Synced Oct 21, 2026, 18:00 UTC.
pirch MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the pirch MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the pirch MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the pirch MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the pirch MCP server have?
- 3 tools: 3 read. search_verified_jobs, get_verified_job and get_jobs_overview.
Does the pirch MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the pirch MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the pirch MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.