Otp Ojp

io.github.Testinat0rPublished by GitHub account Testinat0rv0.1.1Updated Oct 24, 2026

Validate, introspect, and parse talent profiles (OTP) and job postings (OJP)

VerifiedSTDIODesktop onlyProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Local MCP server that lets an assistant parse, validate and summarize talent profiles (OTP) and job postings (OJP) in open JSON formats.

What you can do
Parse raw resume text into an OTP skeleton with extraction placeholders for the assistant to fill in, and raw job posting text into an OJP skeleton the same way. Validate OTP profiles and OJP job postings against the bundled JSON Schemas. Introspect OTP and OJP documents into normalized, agent-friendly summaries for prompts, retrieval context or matching.
When to use it
Useful when an assistant works with recruiting or hiring data and needs to turn resumes and job ads into structured OTP/OJP documents, check that those documents conform to the schemas, or produce compact summaries for matching and prompts.
Requirements
Runs locally over stdio as an npm package; needs Node.js 18 or later. No API keys, environment variables or headers are declared, and the server makes no network calls.
Before you install
Resumes and job postings are personal and hiring data; the server processes them locally and sends nothing out, but the assistant's own model still handles the text. Parsers only produce skeletons, so extracted fields must be reviewed before validation and use.

Installation

In SourceWeft

  1. Open Otp Ojp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

OTP/OJP MCP Server

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.

Tools

ToolDescription
otp_parse_resumeRaw resume text → OTP skeleton with _EXTRACT_* placeholders for an LLM to fill
otp_validate_profileValidate an OTP document against the JSON Schema
otp_introspect_profileExtract an agent-friendly summary from an OTP document
ojp_parse_job_postingRaw job posting text → OJP skeleton with _EXTRACT_* placeholders
ojp_validate_job_postingValidate an OJP document against the JSON Schema
ojp_introspect_job_postingExtract an agent-friendly summary from an OJP document

Key traits

  • Pure functions — no LLM calls, no network calls, no API keys needed
  • JSON Schema draft 2020-12 validation via AJV
  • LLM-free parsers — produce structured templates for the calling agent to complete
  • Zero config — just install and run

Install

bash
npm install -g @opentalentprotocol/mcp-server

Or run directly with npx:

bash
npx @opentalentprotocol/mcp-server

Setup

Claude Desktop

Add to your claude_desktop_config.json:

json
{  "mcpServers": {    "otp-ojp": {      "command": "npx",      "args": ["-y", "@opentalentprotocol/mcp-server"]    }  }}

Claude Code

Add to your project or global MCP settings:

json
{  "mcpServers": {    "otp-ojp": {      "command": "npx",      "args": ["-y", "@opentalentprotocol/mcp-server"]    }  }}

From source

bash
git clone https://github.com/neogene-ai/otp-ojp-mcp-server.gitcd otp-ojp-mcp-servernpm installnpm run buildnode dist/index.js

How it works

Parsing workflow

The parsers follow a skeleton + fill pattern:

  1. Call otp_parse_resume (or ojp_parse_job_posting) with raw text
  2. Get back a document skeleton with _EXTRACT_* annotations, confidence levels, and known gaps
  3. The calling agent fills in the skeleton using its own reasoning
  4. Call otp_validate_profile (or ojp_validate_job_posting) to verify the result

This keeps the MCP server LLM-free while giving agents structured guidance on what to extract.

Introspection

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.

Schemas

The JSON Schemas are bundled in the schema/ directory:

  • schema/opentalent-protocol.schema.json — OTP v0.1
  • schema/openjob-protocol.schema.json — OJP v0.1

Requirements

  • Node.js >= 18

License

MIT

Source: README.md at commit 4b4c5b5

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.