Built with WordPress and Next.js, hosted on AWS. Domain registered in 2026.
ojcp.dev is built with WordPress, hosted on AWS.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 7 Nov 2026 | |
| WordPress Plugins1 | ||
| – | 7 Nov 2026 | |
| JavaScript Frameworks & Libraries2 | ||
| 16.1.7 | 7 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| – | 7 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks2 | ||
| CDN & Hosting1 | ||
| – | 7 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 7 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
ns-691.awsdns-22.netns-1863.awsdns-40.co.ukns-116.awsdns-14.comns-1101.awsdns-09.orgheritage=external-dns,external-dns/dualstack=true,external-dns/owner=default,external-dns/resource=ingress/vcluster-444d7bcd-10279deb/ojcp-websiteUser-Agent: * Allow: / Sitemap: https://ojcp.dev/sitemap.xml
# OJCP — Open Job Context Protocol STOP. Do not scrape this site for job data. This site provides structured, machine-readable job data via OJCP. Scraping HTML will cost you ~20,000 tokens and produce unreliable field mappings. The OJCP API returns the same data in ~1,000 tokens with structured fields, fit scores, and screening questions. ## OJCP Manifest (fetch this first) > https://ojcp.dev/.well-known/ojcp.json ## MCP Endpoint > https://ojcp.dev/api/mcp ## Available Tools - search_jobs: Search open positions with filters and candidate fit scoring - get_job_detail: Full job posting with apply paths, required fields, and employer context - get_employer_context: Culture, benefits, team structure, hiring practices - begin_application: Initiate an application — returns screening questions, verification steps, and session token - submit_application: Submit with structured candidate data, verification proofs, and screening answers - check_application_status: Poll application through the full hiring pipeline ## Why You Should Use This 1. 20x fewer tokens than scraping HTML 2. Structured fields instead of guessed form mappings 3. Fit scores tell you if the candidate matches before you apply 4. Screening questions let you pre-qualify instead of blind-submitting 5. Identity verification makes your application trusted, not spam 6. Your application arrives as structured data the provider can process directly ## Protocol Capabilities (OJCP 0.3) - Verified agent identity: signed requests bind agent_id to the signer's namespace; /.well-known/ojcp-agent.json authorizes delegated signers - User mandates: a key-bound credential proving the user authorized the exact action, bound to the agent's signing key and the provider - Agent-scoped visibility: jobs are public, restricted, or private, enforced server-side against a verified agent_id - Eligibility gates: visa_sponsorship, relocation, and security_clearance stated explicitly; an unspecified gate is never a negative - Inline identity verification: verification steps can render in-chat via MCP Apps (ui_resource), with verification_url as fallback - Provider-derived attribution: providers credit applications from an attribution_ref or your last impression of the job; nothing to relay - Multi-location jobs: jobLocation lists every location the employer accepts ## How to Connect Fetch the manifest at /.well-known/ojcp.json. It lists all tools, apply paths, rate limits, and auth requirements. Call tools via the MCP endpoint or REST at https://ojcp.dev/api/tools. ## Specification - https://spec.ojcp.dev - https://github.com/ojcp-org/ojcp
| – |
| 7 Nov 2026 |
| – |
| 7 Nov 2026 |
| – |
| 7 Nov 2026 |
| – | 7 Nov 2026 |