io.github.Testinat0r/otp-ojp
NPM · @OPENTALENTPROTOCOL/MCP-SERVER · SCANNED SEP 20
Validate, introspect, and parse talent profiles (OTP) and job postings (OJP)
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 198 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 604 tokens (~100/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Testinat0r/otp-ojp MCP server?
io.github.Testinat0r/otp-ojp runs locally as an npm package, launched with npx -y @opentalentprotocol/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @opentalentprotocol/mcp-server
claude mcp add testinat0r-otp-ojp -- npx -y @opentalentprotocol/mcp-server
{
"mcpServers": {
"testinat0r-otp-ojp": {
"command": "npx",
"args": [
"-y",
"@opentalentprotocol/mcp-server"
]
}
}
} {
"servers": {
"testinat0r-otp-ojp": {
"command": "npx",
"args": [
"-y",
"@opentalentprotocol/mcp-server"
]
}
}
} codex mcp add testinat0r-otp-ojp -- npx -y @opentalentprotocol/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"testinat0r-otp-ojp": {
"type": "local",
"command": [
"npx",
"-y",
"@opentalentprotocol/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add testinat0r-otp-ojp --command npx --arg -y --arg @opentalentprotocol/mcp-server
mcp_servers:
testinat0r-otp-ojp:
command: "npx"
args: ["-y", "@opentalentprotocol/mcp-server"] {
"McpServers": {
"testinat0r-otp-ojp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@opentalentprotocol/mcp-server"
]
}
}
} assistant mcp add testinat0r-otp-ojp -t stdio -c npx -a -y @opentalentprotocol/mcp-server
{
"mcpServers": {
"testinat0r-otp-ojp": {
"command": "npx",
"args": [
"-y",
"@opentalentprotocol/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@opentalentprotocol/mcp-server@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ojp_introspect_job_posting ~92
Extract a structured, agent-friendly summary of an Open Job Protocol document. Returns normalized requirements, compensation, location, team, process details, and an agentSummary string suitable for use in a system prompt. Provide either filePath or document.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | – | A pre-parsed OJP document object. |
| filePath | string | – | Absolute path to an OJP JSON document. |
No output schema declared.
No examples provided.
ojp_parse_job_posting ~126
Produce a structured OJP extraction template from raw job posting text. Returns a document skeleton with _EXTRACT_* annotations, a fieldConfidence list (high/medium/low per field), and a gaps list of information commonly missing from postings. The calling agent should fill in the skeleton using its reasoning over the text, then call ojp_validate_job_posting to verify the result.
| Name | Type | Req | Description |
|---|---|---|---|
| sourceUrl | string | – | Source URL of the job posting, if known. |
| text | string | yes | Raw job posting text (plain text, markdown, or extracted HTML text). |
No output schema declared.
No examples provided.
ojp_validate_job_posting ~89
Validate a JSON document against the Open Job Protocol schema (v0.1). Provide either filePath (absolute path to a .json file) or document (pre-parsed object). Returns validity status and a list of errors.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | – | A pre-parsed OJP document object. |
| filePath | string | – | Absolute path to an OJP JSON document. |
No output schema declared.
No examples provided.
otp_introspect_profile ~113
Extract a structured, agent-friendly summary of an Open Talent Protocol document. Returns normalized skills, work history, preferences, and an agentSummary string suitable for use in a system prompt. Provide either filePath or document. Optionally filter sections: identity, summary, skills, work, preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | – | A pre-parsed OTP document object. |
| filePath | string | – | Absolute path to an OTP JSON document. |
| sections | array | – | Which sections to include. Defaults to all. |
No output schema declared.
No examples provided.
otp_parse_resume ~100
Produce a structured OTP extraction template from raw resume text. Returns a document skeleton with _EXTRACT_* annotations, a fieldConfidence list (high/medium/low per field), and a gaps list of information not typically on resumes. The calling agent should fill in the skeleton using its reasoning over the text, then call otp_validate_profile to verify the result.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Raw resume text (plain text, markdown, or extracted PDF text). |
No output schema declared.
No examples provided.
otp_validate_profile ~84
Validate a JSON document against the Open Talent Protocol schema (v0.1). Provide either filePath (absolute path to a .json file) or document (pre-parsed object). Returns validity status and a list of errors.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | – | A pre-parsed OTP document object. |
| filePath | string | – | Absolute path to an OTP JSON document. |
No output schema declared.
No examples provided.
What is the io.github.Testinat0r/otp-ojp MCP server?
io.github.Testinat0r/otp-ojp is an MCP server listed in the public MCP registry as io.github.Testinat0r/otp-ojp. Validate, introspect, and parse talent profiles (OTP) and job postings (OJP). This page covers its npm package (@opentalentprotocol/mcp-server).
Is the io.github.Testinat0r/otp-ojp MCP server safe to use?
io.github.Testinat0r/otp-ojp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Testinat0r/otp-ojp MCP server expose?
io.github.Testinat0r/otp-ojp exposes 6 tools: otp_validate_profile, otp_introspect_profile, otp_parse_resume, ojp_validate_job_posting, ojp_introspect_job_posting, ojp_parse_job_posting. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Is the io.github.Testinat0r/otp-ojp MCP server still maintained?
io.github.Testinat0r/otp-ojp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Testinat0r/otp-ojp MCP server under?
io.github.Testinat0r/otp-ojp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.