Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.UncleTIM-GZ/oprocess

PYPI · OPROCESS

AI-native process classification. 2436 processes + 3284 KPIs from APQC, ITIL, SCOR.

Available components

−15 this week 66 Trust /100

Last scanned (12 hours ago)

Scores higher than 58% of PyPI servers

Category Project Management

Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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 113 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 767 tokens (~69/item across 11 items; 8 tools + 3 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 15 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 7 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
Diagnostics

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 21 Nov 2026 · Analysed pypi/oprocess@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~625 tokens

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 →

Tool Tokens
compare_processes ~66

Compare two or more process nodes side-by-side across all attributes. Accepts comma-separated process IDs. Returns differences in name, description, domain, level, KPI count, and hierarchy path for each node.

NameTypeReqDescription
process_idsstringyesComma-separated process IDs (2+)
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

export_responsibility_doc ~76

Export a complete role responsibility document. Generates Markdown with provenance appendix. Accepts one or more process IDs. Sections: role overview, responsibilities, KPIs, provenance.

NameTypeReqDescription
langstring–Language
process_idsstringyesComma-separated process IDs (1+)
role_name––Role name
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

get_kpi_suggestions ~69

Retrieve KPI metrics for a process node. Queries the 3284-entry KPI database. Returns process info, KPI list with name/unit/category, count, and provenance.

NameTypeReqDescription
process_idstringyesProcess ID (e.g. '1.0', '8.5.3')
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

get_process_tree ~105

Retrieve a process node and its full subtree. Returns hierarchical JSON with id, name, description, and nested children up to max_depth levels. Large trees are truncated at max_nodes with a warning. Use to explore the 5-level process taxonomy.

NameTypeReqDescription
max_depthinteger–Max depth
max_nodesinteger–Max nodes in response
process_idstringyesProcess ID (e.g. '1.0', '8.5.3')
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

get_responsibilities ~85

Generate role responsibilities for a process node. Includes full hierarchy context: ancestor chain, sub-processes, and domain. Supports JSON or Markdown output. Has provenance.

NameTypeReqDescription
langstring–Language
output_formatstring–Output format
process_idstringyesProcess ID (e.g. '1.0', '8.5.3')
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

health_check ~41

Health check for the O'Process MCP server. Returns JSON with status, server name, process/KPI counts, sqlite-vec availability, and semantic search readiness.

Input schema present but exposes no named parameters.

NameTypeReqDescription
semantic_search_availablebooleanyes–
serverstringyes–
statusstringyes–
total_kpisintegeryes–
total_processesintegeryes–
vec_availablebooleanyes–

No examples provided.

map_role_to_processes ~80

Map a job role to relevant process nodes. Uses semantic search to find matching processes. Returns ranked list with confidence scores. Optionally filter by industry tag. Low-confidence triggers BoundaryResponse.

NameTypeReqDescription
industry––Industry tag
langstring–Language
limitinteger–Max matches
role_descriptionstringyes–
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

search_process ~103

Search the O'Process framework (2436 nodes). Covers APQC PCF 8.0 + ITIL V5 + SCOR DS 14.0. Supports semantic vector search with cosine similarity. Returns matching nodes with id, name, description, score. Low-confidence queries trigger BoundaryResponse.

NameTypeReqDescription
langstring–Language
level––Level 1-5
limitinteger–Max results
querystringyes–
NameTypeReqDescription
provenance_chainarray––
response_msinteger––
result–yes–
session_id–––

No examples provided.

Install

How do I install the io.github.UncleTIM-GZ/oprocess MCP server?

io.github.UncleTIM-GZ/oprocess runs locally as a PyPI package, launched with uvx oprocess. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · oprocess

# add to Claude Code
claude mcp add uncletim-gz-oprocess -- uvx oprocess
Common questions

What is the io.github.UncleTIM-GZ/oprocess MCP server?

io.github.UncleTIM-GZ/oprocess is an MCP server listed in the public MCP registry as io.github.UncleTIM-GZ/oprocess. AI-native process classification. 2436 processes + 3284 KPIs from APQC, ITIL, SCOR. This page covers its PyPI package (oprocess).

Is the io.github.UncleTIM-GZ/oprocess MCP server safe to use?

io.github.UncleTIM-GZ/oprocess scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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.UncleTIM-GZ/oprocess MCP server expose?

io.github.UncleTIM-GZ/oprocess exposes 8 tools: search_process, map_role_to_processes, get_process_tree, get_kpi_suggestions, compare_processes, and 3 more. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.

Is the io.github.UncleTIM-GZ/oprocess MCP server still maintained?

io.github.UncleTIM-GZ/oprocess is still listed as active in the MCP registry. We last reached this channel on 21 November 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.UncleTIM-GZ/oprocess MCP server under?

io.github.UncleTIM-GZ/oprocess declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.UncleTIM-GZ/oprocess MCP server?

VerifyMCP ran 14 checks on io.github.UncleTIM-GZ/oprocess, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.UncleTIM-GZ/oprocess: Malware scan and Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.