pirch
Server Details
Verified job search: every listing confirmed live and accepting applicants within the last 72h.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
3 toolsget_jobs_overviewInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
get_verified_jobInspect
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 | Required | Description | Default |
|---|---|---|---|
| id | Yes | Job id from search results. |
search_verified_jobsInspect
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 | Required | Description | Default |
|---|---|---|---|
| role | No | Occupation slug filter (e.g. 'ux-designer', 'registered-nurse'). Use get_jobs_overview to see which slugs currently have jobs. | |
| limit | No | Max results, 1-25 (default 10). | |
| query | No | Free-text search over title, company, location, occupation and summary (e.g. 'senior product designer'). | |
| location | No | 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. | |
| workmode | No | Filter by work mode. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!