Pkagentic MCP Server

@pkagentic/mcp npm v1.9.4

Published by @pkagentic — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 8

high Tool "save_script" exposes command/code executionMTC-CAP-001

Tool "save_script" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool save_script

high Tool "create_script" exposes command/code executionMTC-CAP-001

Tool "create_script" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool create_script

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([get_file, get_files_batch, download_image, cdn_download_library]) co-exist with external-action tools ([save_script, create_script]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_file, get_files_batch, download_image, cdn_download_library] → sinks [save_script, create_script]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow get_file → save_script

medium Unconstrained URL/host parameter "url" on "download_image"MTC-CAP-007

Tool "download_image" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool download_image · inputSchema.properties.url

medium Unconstrained command parameter "script_mode" on "save_script"MTC-CAP-006

Tool "save_script" takes a command-shaped parameter "script_mode" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool save_script · inputSchema.properties.script_mode

medium Unconstrained command parameter "script_mode" on "create_script"MTC-CAP-006

Tool "create_script" takes a command-shaped parameter "script_mode" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool create_script · inputSchema.properties.script_mode

low Mutating tool "save_script" declares no destructiveHintMTC-CAP-005

Tool "save_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool save_script

low Mutating tool "create_script" declares no destructiveHintMTC-CAP-005

Tool "create_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool create_script

Tools 85

Each tool and what it can reach — statically extracted from the published source.

  • cdn_download_libraryingests untrusted input
  • create_scriptruns code / shell
  • download_imageingests untrusted input
  • get_fileingests untrusted input
  • get_files_batchingests untrusted input
  • save_scriptruns code / shell
  • add_menu_itemno sensitive capability
  • add_post_taxonomyno sensitive capability
  • assign_menu_locationno sensitive capability
  • create_blog_postno sensitive capability
Show 75 more tools ↓
  • create_contentno sensitive capability
  • create_libraryno sensitive capability
  • create_nav_menuno sensitive capability
  • create_taxonomyno sensitive capability
  • create_templateno sensitive capability
  • delete_libraryno sensitive capability
  • delete_menu_itemno sensitive capability
  • delete_nav_menuno sensitive capability
  • delete_scriptno sensitive capability
  • delete_templateno sensitive capability
  • draft_blog_postno sensitive capability
  • generate_imageno sensitive capability
  • get_agent_guideno sensitive capability
  • get_blog_postno sensitive capability
  • get_content_infono sensitive capability
  • get_image_srcsetno sensitive capability
  • get_libraryno sensitive capability
  • get_nav_menuno sensitive capability
  • get_rolesno sensitive capability
  • get_script_infono sensitive capability
  • get_script_revisionsno sensitive capability
  • get_seo_datano sensitive capability
  • get_site_infono sensitive capability
  • get_tailwind_configno sensitive capability
  • get_template_infono sensitive capability
  • get_template_revisionsno sensitive capability
  • init_projectno sensitive capability
  • list_blog_postsno sensitive capability
  • list_librariesno sensitive capability
  • list_menu_locationsno sensitive capability
  • list_nav_menusno sensitive capability
  • list_taxonomyno sensitive capability
  • mark_content_editno sensitive capability
  • optimize_imageno sensitive capability
  • publish_blog_postno sensitive capability
  • publish_contentno sensitive capability
  • publish_scriptno sensitive capability
  • publish_templateno sensitive capability
  • read_web_pageno sensitive capability
  • remove_post_taxonomyno sensitive capability
  • restore_library_backupno sensitive capability
  • restore_script_revisionno sensitive capability
  • restore_template_revisionno sensitive capability
  • save_blog_postno sensitive capability
  • save_contentno sensitive capability
  • save_library_filesno sensitive capability
  • save_templateno sensitive capability
  • schedule_blog_postno sensitive capability
  • search_blog_postsno sensitive capability
  • search_contentsno sensitive capability
  • search_librariesno sensitive capability
  • search_mediano sensitive capability
  • search_taxonomyno sensitive capability
  • set_feature_imageno sensitive capability
  • syncno sensitive capability
  • tailwind_optimizeno sensitive capability
  • toggle_libraryno sensitive capability
  • toggle_library_lockno sensitive capability
  • toggle_scriptno sensitive capability
  • toggle_templateno sensitive capability
  • unassign_menu_locationno sensitive capability
  • update_agent_guideno sensitive capability
  • update_contentno sensitive capability
  • update_libraryno sensitive capability
  • update_library_conditionsno sensitive capability
  • update_menu_itemno sensitive capability
  • update_nav_menuno sensitive capability
  • update_post_excerptno sensitive capability
  • update_scriptno sensitive capability
  • update_script_conditionsno sensitive capability
  • update_seo_datano sensitive capability
  • update_tailwind_configno sensitive capability
  • update_templateno sensitive capability
  • update_template_conditionsno sensitive capability
  • upload_mediano sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.9.4 latest A 92/100 8 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pkagentic-mcp/badge.svg)](https://mcptrustchecker.com/registry/pkagentic-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pkagentic-mcp"><img src="https://mcptrustchecker.com/registry/pkagentic-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pkagentic-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @pkagentic/mcp --online

Use the free API → How scoring works

More in Developer Tools