Validate, introspect, and parse talent profiles (OTP) and job postings (OJP)
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"otp-ojp": {
"args": [
"-y",
"@opentalentprotocol/mcp-server"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server for the Open Talent Protocol (OTP) and Open Job Protocol (OJP) — open standards for structuring candidate profiles and job postings for AI agent reasoning.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@opentalentprotocol/mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @opentalentprotocol/mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Autonomous spec-to-product coding-agent CLI with an MCP server exposing 34 tools over stdio.
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
App framework, testing framework, and inspector for MCP Apps.
MCP Security Weekly
Get CVE alerts and security updates for io.github.Testinat0r/otp-ojp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP server for the Open Talent Protocol (OTP) and Open Job Protocol (OJP) — open standards for structuring candidate profiles and job postings for AI agent reasoning.
| Tool | Description |
|---|---|
otp_parse_resume | Raw resume text → OTP skeleton with _EXTRACT_* placeholders for an LLM to fill |
otp_validate_profile | Validate an OTP document against the JSON Schema |
otp_introspect_profile | Extract an agent-friendly summary from an OTP document |
ojp_parse_job_posting | Raw job posting text → OJP skeleton with _EXTRACT_* placeholders |
ojp_validate_job_posting | Validate an OJP document against the JSON Schema |
ojp_introspect_job_posting | Extract an agent-friendly summary from an OJP document |
npm install -g @opentalentprotocol/mcp-server
Or run directly with npx:
npx @opentalentprotocol/mcp-server
Add to your claude_desktop_config.json:
{
"mcpServers": {
"otp-ojp": {
"command": "npx",
"args": ["-y", "@opentalentprotocol/mcp-server"]
}
}
}
Add to your project or global MCP settings:
{
"mcpServers": {
"otp-ojp": {
"command": "npx",
"args": ["-y", "@opentalentprotocol/mcp-server"]
}
}
}
git clone https://github.com/neogene-ai/otp-ojp-mcp-server.git
cd otp-ojp-mcp-server
npm install
npm run build
node dist/index.js
The parsers follow a skeleton + fill pattern:
otp_parse_resume (or ojp_parse_job_posting) with raw text_EXTRACT_* annotations, confidence levels, and known gapsotp_validate_profile (or ojp_validate_job_posting) to verify the resultThis keeps the MCP server LLM-free while giving agents structured guidance on what to extract.
The introspect tools flatten an OTP/OJP document into a normalized, agent-friendly object with an agentSummary string — ready for system prompts, retrieval-augmented context, or matching logic.
The JSON Schemas are bundled in the schema/ directory:
schema/opentalent-protocol.schema.json — OTP v0.1schema/openjob-protocol.schema.json — OJP v0.1MIT