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.ChloePark85/picright

NPM · PICRIGHT-MCP

License-aware images for markdown: CC/stock search, screenshots, Mermaid diagrams, provenance

Available components

0 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 56% of npm servers

Category Documents and Files

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 Security96
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known low-severity CVE affects katex 0.16.47, reached via mermaid > katex. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 72 of 206 dependencies flagged as unhealthy. View diagnostics → Partial
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 81 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • 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
  • Context-footprint check failed: tool/resource definitions use about 1226 tokens (~136/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 41% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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 (15)

  • Malware scan
  • 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 (1)

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.

  • 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 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 0
    • Stability: pass → 0.97 functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 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.

  • 11 Nov 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.

  • 9 Nov 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.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 +1
    • Dependency health: 0.76 → 0.84 ▲ functional
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 npm/picright-mcp@0.1.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-238p-pmpm-9mq7 CVE-2026-103923 low yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 206 packages
Packages resolved 206
Stale 72
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,226 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
analyze_document ~76

Parse a markdown file into blocks (headings, paragraphs, code, quotes, lists, existing images) with indices. Use this to decide where images belong, then call insert_image with after_block. Blocks of type code/quote/list/image are usually poor anchors.

NameTypeReqDescription
target_filestringyesAbsolute path to a .md file

No output schema declared.

No examples provided.

get_license ~113

Return the normalized license, caveats, risk level and attribution text for an image id returned by search_images.

NameTypeReqDescription
image_idstringyes–
need_modificationboolean–Exclude ND licenses (you may crop/resize/overlay)
no_attribution_onlyboolean–Only return images that need no attribution (CC0/PD/Pixabay/Pexels)
no_share_alikeboolean–Exclude SA licenses
usagestring–commercial excludes CC NC licenses

No output schema declared.

No examples provided.

insert_image ~176

Downloads the image next to the document (images/ by default), inserts a markdown image + credit after the given block, and appends a provenance.json ledger entry recording the license as verified at insert time. Refuses to omit credit when the license requires attribution.

NameTypeReqDescription
after_blockintegeryesBlock index from analyze_document; -1 = top of document
altstring–Alt text; defaults to image title
captionstring–Optional italic caption under the image
credit_stylestring––
file_namestring–Base file name without extension; defaults to slug of alt/title
image_idstringyesid from search_images
images_dirstring–Relative to the document's folder
target_filestringyesAbsolute path to the .md file

No output schema declared.

No examples provided.

list_ledger ~56

List every image recorded in provenance.json for a document's images folder, with license and attribution as verified at insert time.

NameTypeReqDescription
images_dirstring––
target_filestringyesAbsolute path to the .md file

No output schema declared.

No examples provided.

render_diagram ~185

Turn the article's own ideas into a diagram (flowchart, sequence, mindmap, timeline, pie, quadrant…) — best for structure/process/comparison paragraphs where a stock photo would be off-topic. Copyright-clean (basis=original). Give valid Mermaid code; Korean labels are fine. If target_file is given the PNG is inserted after after_block.

NameTypeReqDescription
after_blockinteger––
altstring––
backgroundstring––
captionstring––
credit_stylestring––
file_namestring––
images_dirstring––
mermaidstringyesMermaid source, e.g. 'flowchart LR\n A[글 작성] --> B[이미지 MCP]'
target_filestring––
themestring––
widthinteger––

No output schema declared.

No examples provided.

render_snippet ~81

For remote clients that cannot write files: return markdown/HTML for an image candidate with the correct credit line, plus the direct image URL and a ledger-style provenance record the caller can store. Does not download anything.

NameTypeReqDescription
altstring––
captionstring––
formatstring––
image_idstringyes–

No output schema declared.

No examples provided.

replace_image ~109

Swap an image previously inserted by insert_image (identified by its relative path in the markdown) for a new candidate id. Updates the file and the ledger.

NameTypeReqDescription
altstring––
captionstring––
credit_stylestring––
current_rel_pathstringyese.g. images/agents-office.jpg as written in the markdown
delete_old_fileboolean––
new_image_idstringyes–
target_filestringyes–

No output schema declared.

No examples provided.

screenshot_url ~224

Capture a URL (or a CSS-selected region) with a headless browser. Use ONLY when the text discusses that page/product/article — the capture is recorded with basis=quotation, not a license, and the credit shows source URL + capture date. Prefer selector/crop over full pages. If target_file is given the PNG is inserted after after_block; otherwise the PNG is written next to nothing and returned as an image.

NameTypeReqDescription
after_blockinteger––
altstring––
captionstring––
credit_stylestring––
file_namestring––
full_pageboolean––
heightinteger––
hidearray–Extra CSS selectors to hide (popups, banners)
images_dirstring––
selectorstring–CSS selector to capture just one region (recommended)
target_filestring–Absolute .md path to insert into
urlstringyes–
wait_msinteger––
widthinteger––

No output schema declared.

No examples provided.

search_images ~206

Search Openverse (CC/PD), Pixabay and Pexels for images whose license passes the policy. Returns ranked candidates with normalized license info, risk level (people/logos) and a ready-made attribution line. Use short English queries (2-5 concrete nouns) for best results.

NameTypeReqDescription
avoid_peopleboolean–Drop candidates whose tags mention people/faces/logos
limitinteger––
need_modificationboolean–Exclude ND licenses (you may crop/resize/overlay)
no_attribution_onlyboolean–Only return images that need no attribution (CC0/PD/Pixabay/Pexels)
no_share_alikeboolean–Exclude SA licenses
orientationstring––
providersarray–Defaults to every provider with a configured key
querystringyesEnglish search query, e.g. 'robot office teamwork'
usagestring–commercial excludes CC NC licenses

No output schema declared.

No examples provided.

Install

How do I install the io.github.ChloePark85/picright MCP server?

io.github.ChloePark85/picright runs locally as an npm package, launched with npx -y picright-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · picright-mcp

# add to Claude Code
claude mcp add chloepark85-picright -- npx -y picright-mcp
Common questions

What is the io.github.ChloePark85/picright MCP server?

io.github.ChloePark85/picright is an MCP server listed in the public MCP registry as io.github.ChloePark85/picright. License-aware images for markdown: CC/stock search, screenshots, Mermaid diagrams, provenance. This page covers its npm package (picright-mcp).

Is the io.github.ChloePark85/picright MCP server safe to use?

io.github.ChloePark85/picright scores 77 out of 100 on VerifyMCP. We recorded 1 known advisory against 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.ChloePark85/picright MCP server expose?

io.github.ChloePark85/picright exposes 9 tools: search_images, get_license, analyze_document, insert_image, replace_image, and 4 more. Their descriptions and schemas cost roughly 1,226 tokens of context every time the server is loaded.

Is the io.github.ChloePark85/picright MCP server still maintained?

io.github.ChloePark85/picright 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.ChloePark85/picright MCP server under?

io.github.ChloePark85/picright 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.ChloePark85/picright MCP server?

VerifyMCP ran 15 checks on io.github.ChloePark85/picright, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.ChloePark85/picright: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.