pnCore (perniemann/pnCore) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 27 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
9 days ago

pnCore

Enables software delivery as a sequence of named, gated workflow steps, from discovery and planning through build, review, and handoff, with verifiable gates and resumable state outside the chat.

→ perniemann/pnCore· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

perniemann

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: PAPERCLIP_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretPAPERCLIP_API_KEY
configPAPERCLIP_API_URL
configPAPERCLIP_ISSUE_ID
configPAPERCLIP_RUN_ID
configPNCORE_CONTENT_PATH
configPNCORE_DEBUG
configPNCORE_FEATURESorchestrator) for subagent routing; omit step for the full per-step table. Resolves PNCORE_FEATURES.modelTierOverrides and tierAliases.
configPNCORE_HUMAN_GATE_SCAN_BYTES
configPNCORE_RUN_EVENTS_PATH
configPNCORE_STRICT_SKEPTIC_GATES
configPNCORE_VERIFY_SANDBOXNo-shell catalog verify; returns a GateReport. Requires disposeVerify. Fail-closed without a jail unless PNCORE_VERIFY_SANDBOX=restricted or the Vitest test backend.
configVITEST_WORKER_ID
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

27/27 tools missing one or more hints — health (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); project_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_workflow_types (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/perniemann/pncore)](https://m8ven.ai/mcp/perniemann/pncore)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 83b5c893ca0fc2bd528f0d1c8bfcbe6b8d1a9977
code hash: 899be2703b00f6ce80cc0f4817964af72d9d83e940da279f4e46cda51f753423
verified: 9/1/2026, 5:21:42 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client