MCP servers › io.github.pei-jz › jh-presentation

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.pei-jz/jh-presentation

AI-built HTML presentations: single-file decks with live diagrams, charts, editing and PDF export. — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: productivity-and-docs · AI-classifiedversion 0.8.0JavaScriptMITstandard input/output24 tools

Summary

io.github.pei-jz/jh-presentation is a local MCP server listed in the official MCP registry at version 0.8.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 24 tools, 1 resource and 5 prompts.

Record checks

9 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#3,665 of 15,112 packages by monthly downloads, tied with 5 others
Not ranked by stars: 0 stars (ranked from 10)
#540 of 1,074 packages meeting all 9 record checks, by downloads

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 24
Described as changing data: 13 of 24 toolsAI-classified
Mainly works on: files and code on the machine it runs onAI-classified
Topic: productivity-and-docsAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

13 tools are described as changing something (open_theme_gallery, create_theme, create_deck, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.8.0, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-05 (earliest version still in the registry; older removed versions would be earlier)

Version history

4 versions listed, 2026-10-05 to 2026-10-19; 4 in the 90 days before the 2026-10-23 snapshot.

Most recent 4 versions

0.8.0 · 2026-10-19
0.7.0 · 2026-10-08
0.6.0 · 2026-10-07
0.5.2 · 2026-10-05

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.8.0 (published 2026-10-19).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

24tools

1resources

5prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

13 of 24 tools are described as changing something (creating, editing, deleting, sending or running).

get_guideon 117 other serversreads or searches
“プレゼンテーション資料 (スライド・発表資料) の書き方・部品カタログ・良い例・デザイン原則・作業手順。スライドを書く前に必ず読むこと。”
Publisher declares: read-only yes
Takes no inputs.
list_themeson 18 other serversreads or searches
“利用できるデザインテーマ (同梱 + 自作。名前・表示名・雰囲気の説明・タグ)。内容や聞き手に合うテーマを選ぶときに使う。”
Publisher declares: read-only yes
Takes no inputs.
open_theme_gallerycontrols a browser or desktopdescribed as changing data
“全テーマの見本スライドを並べたページを生成し、ユーザーのブラウザで開く。ユーザーが「テーマを見たい」「どんなデザインがある?」と言ったときに使う (実際に動く見本を見て選べる)。”
Takes no inputs.
preview_themesreads or searches
“各テーマの見本スライドを画像で返す (AI がテーマを見比べる用。テーマ作成後の確認にも使う)。slide: 1=表紙 2=セクション扉 3=カード 4=数値 5=コード 6=結び”
Publisher declares: read-only yes
2 inputs
- themesarray“対象のテーマ名 (省略時は全テーマ)”
- slidesarray“見本スライドの番号 (既定 [1])”
get_theme_guidereads or searches
“新しいテーマを作るためのガイド (変数の一覧・装飾の上書き方法・確認手順)。create_theme の前に読む。”
Publisher declares: read-only yes
Takes no inputs.
create_themeon 3 other serverscreates or changes datadescribed as changing data
“自作テーマを保存する (同名の自作テーマは上書き)。css は default テーマに重ねる CSS (:root の変数上書き + 必要な装飾)。保存後は preview_themes で全見本スライドを確認して調整すること。get_theme_guide を先に読む。”
5 inputs, 4 required
- namestringrequired“テーマ名 (英小文字・数字・ハイフン。例: acme-blue)”
- labelstringrequired“表示名 (例: ACME ブルー)”
- descriptionstringrequired“雰囲気と向いている発表 (1 文)”
- tagsarray“タグ (例: ["落ち着いた", "フォーマル"])”
- cssstringrequired“テーマの CSS”
list_templateson 111 other serversreads or searches
“用意されている依頼文テンプレート (技術解説・LT・進捗報告など) の一覧と本文。クライアントのプロンプトメニューを使えない場合や、ユーザーが「どんな型がある?」と聞いたときに使い、選ばれたテンプレートの本文に沿って作成を進める。”
Publisher declares: read-only yes
Takes no inputs.
list_deckson 7 other serversreads or searches
“作成済みのプレゼンテーション資料 (スライド・デッキ) とマップ文書の一覧 (新しい順)。保存先のフォルダも返す。”
Publisher declares: read-only yes
1 input
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
create_deckon 11 other serverscreates or changes datadescribed as changing data
“プレゼンテーション資料 (スライド・発表資料・LT・報告資料) を新しく作る。1 ファイルの HTML (デッキ) で、名前は YYYY-MM-DD-<name>。表紙 1 枚だけの状態で作られるので、続けて write_deck で中身を書く。”
7 inputs, 2 required
- namestringrequired“英数字・ハイフンの短い名前 (例: git-branch-strategy)”
- titlestringrequired“発表タイトル (日本語可)”
- themestring“テーマ名 (既定: default)。同梱: default (汎用) / dark (技術系) / corporate (報告・提案) / pop (LT・カジュアル) / mono (メッセージ重視)。自作テーマを含む一覧は list_themes”
- transitionstring“スライド切り替え効果”
- brandstring“ブランド枠 (名前・ロゴ): none / header (上) / footer (下) / both (上下)”
- autoFullscreenboolean“発表モード: 開いた後の最初の → キー・クリックで全画面にする (既定 false)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
read_deckon 2 other serversreads or searches
“プレゼンテーション資料 (スライド・デッキ) の編集可能な部分 (スライド HTML・デッキ専用 CSS / JS・設定・埋め込み画像名) と revision を返す。修正前に必ず読むこと。write_deck / replace_slide に revision を渡すと、読んだ後に他で変更されていた場合に上書きを防げる。”
Publisher declares: read-only yes
2 inputs, 1 required
- namestringrequired“デッキ名 (list_decks / create_deck が返す name。.html は不要)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
write_deckon 1 other servercreates or changes datadescribed as changing data
“プレゼンテーション資料 (デッキ) のスライドを書き込む。指定した項目だけ置き換え、省略した項目はそのまま残る。slides は <section class="slide">...</section> の並び (全スライド分。id の重複やスライド外の要素はエラー)。埋め込まれたエンジン・テーマ・ブランドは変わらない (theme を変えた場合はテーマだけ入れ替わる。最新化は upgrade_…”
11 inputs, 1 required
- namestringrequired“デッキ名 (list_decks / create_deck が返す name。.html は不要)”
- slidesstring“全スライドの HTML (<section class="slide"> の並び)”
- cssstring“デッキ専用 CSS の全内容”
- jsstring“デッキ専用 JS の全内容 (Deck.onSlide など)”
- titlestring“タイトル”
- themestring“テーマ名”
- transitionstring“スライド切り替え効果”
- brandstring“ブランド枠 (名前・ロゴ): none / header (上) / footer (下) / both (上下)”
- autoFullscreenboolean“発表モード: 開いた後の最初の → キー・クリックで全画面にする (既定 false)”
- revisionstring“read_deck が返した revision (指定すると、他で変更されていた場合は保存しない)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
replace_slideon 1 other servercreates or changes datadescribed as changing data
“プレゼンテーション資料 (デッキ) のスライドを 1 枚だけ置き換える。target は 1 始まりの番号、またはスライドの id (id での指定を推奨)。書き込み後に自動でレイアウトを検査し、結果を audit に返す。”
5 inputs, 3 required
- namestringrequired“デッキ名 (list_decks / create_deck が返す name。.html は不要)”
- targetinteger or stringrequired“スライド番号 (1 始まり) または id”
- slidestringrequired“新しい <section class="slide">...</section> (1 枚分)”
- revisionstring“read_deck が返した revision (指定すると、他で変更されていた場合は保存しない)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”

Show 12 more tools

add_asseton 1 other servercreates or changes datadescribed as changing data
“ローカルの画像・動画ファイルをデッキに埋め込む (png / jpg / gif / webp / svg / mp4 / webm)。スライドからは <img data-asset="返された名前" alt="..."> で参照する (src は書かない)。”
4 inputs, 2 required
- namestringrequired“デッキ名 (list_decks / create_deck が返す name。.html は不要)”
- filestringrequired“埋め込むファイルの絶対パス”
- asstring“参照名 (省略時はファイル名)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
create_mapon 10 other serverscreates or changes datadescribed as changing data
“マップ文書を新しく作る: スライドではなく、大きなシステムの関連図・説明書を「全体 → 細部」とたどって読む 1 ファイルの HTML 資料 (目次・検索・データでの絞り込み・URL での共有・階層ごとの印刷付き)。名前は YYYY-MM-DD-<name>。map を省略すると、書き方の見本を兼ねた最初のマップが入るので、続けて write_map で中身を書く。”
6 inputs, 2 required
- namestringrequired“英数字・ハイフンの短い名前 (例: order-system)”
- titlestringrequired“資料のタイトル (日本語可)”
- themestring“テーマ名 (既定: default)。一覧は list_themes”
- brandstring“ブランド枠 (名前・ロゴ): none / header (上) / footer (下) / both (上下)”
- mapstring or object“マップのデータ (JSON のオブジェクトか文字列)。書き方はガイドの「階層マップ」と同じ: { title, direction, nodes: [{ id, label, sub, kind, accent, detail (HTML), tags, children: { nodes, edges } }], …”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
read_mapon 1 other serverreads or searches
“マップ文書の編集可能な部分 (マップのデータ (JSON)・専用 CSS / JS・設定) と revision を返す。修正前に必ず読むこと。write_map に revision を渡すと、読んだ後に他で変更されていた場合に上書きを防げる。大きなマップ (ノードが数十を超える) は、outline: true で目次 (id・名前・種類・中の数) だけを読み、node に箱の id を渡し…”
Publisher declares: read-only yes
4 inputs, 1 required
- namestringrequired“マップ文書の名前 (list_decks の maps / create_map が返す name。.html は不要)”
- outlineboolean“true: マップのデータの代わりに目次だけを返す”
- nodestring“このノード (children ごと) だけを返す”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
write_mapcreates or changes datadescribed as changing data
“マップ文書のデータを書き込む。指定した項目だけ置き換え、省略した項目はそのまま残る。map は全体を渡す。大きなマップの一部だけを直すときは、map の代わりに node (箱の id) と part (その箱の JSON 全体。children ごと。id は同じ) を渡す。埋め込まれたビューア・テーマ・ブランドは変わらない (最新化は upgrade_deck)。保存前の内容は履歴に残る (…”
11 inputs, 1 required
- namestringrequired“マップ文書の名前 (list_decks の maps / create_map が返す name。.html は不要)”
- mapstring or object“マップのデータ (JSON のオブジェクトか文字列)。書き方はガイドの「階層マップ」と同じ: { title, direction, nodes: [{ id, label, sub, kind, accent, detail (HTML), tags, children: { nodes, edges } }], …”
- nodestring“一部だけ置き換えるときの箱の id (part と一緒に渡す)”
- partstring or object“node の箱の JSON 全体 (children・その中の edges / relations ごと)”
- cssstring“専用 CSS の全内容”
- jsstring“専用 JS の全内容”
- titlestring“タイトル”
- themestring“テーマ名”
- brandstring“ブランド枠 (名前・ロゴ): none / header (上) / footer (下) / both (上下)”
- revisionstring“read_deck が返した revision (指定すると、他で変更されていた場合は保存しない)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
upgrade_deckon 1 other servercreates or changes datadescribed as changing data
“デッキ・マップ文書に埋め込まれたエンジン・テーマ・ブランド設定を最新にする (内容は変わらないが、見た目が変わる場合がある)。ユーザーが最新化を求めたとき、またはブランド設定 (brand.json) を変えたときだけ使う。name 省略時は全デッキ・全マップ文書。”
2 inputs
- namestring“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
list_historyon 9 other serversreads or searches
“デッキ・マップ文書の保存履歴 (書き込み前の版。新しい順、最大 20 件)。”
Publisher declares: read-only yes
2 inputs, 1 required
- namestringrequired“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
restore_historycreates or changes datadescribed as changing data
“保存履歴の版にデッキ・マップ文書を戻す (戻す前の内容も履歴に残るので、やり直しできる)。”
3 inputs, 2 required
- namestringrequired“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- idstringrequired“list_history の id”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
audit_deckreads or searches
“ヘッドレスブラウザでプレゼンテーション資料 (スライド・デッキ) を開き、次の項目を検査する: はみ出し・切れ (overflow)、文字の重なり (overlap)、コントラスト不足 (contrast)、画像の欠落・読み込み失敗 (images)、小さすぎる文字 (smallText)、JS エラー (errors)、エンジンの警告 (warnings)、外部への通信 (externalRe…”
Publisher declares: read-only yes
2 inputs, 1 required
- namestringrequired“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
screenshot_deckreads or searches
“プレゼンテーション資料のスライドの見た目を画像で返す。slides 省略時は全スライド (枚数が多い場合は数枚ずつ指定するとよい)。step 省略時は全ステップ表示・アニメーション完了後の最終状態。数値を指定するとそのステップ数まで表示した状態。マップ文書は階層ごとに撮る (levels にノード id の配列。'' は全体。省略時は全階層 (最大 12)。select でその部品を選んで詳細パ…”
Publisher declares: read-only yes
7 inputs, 1 required
- namestringrequired“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- slidesarray“スライド番号 (1 始まり) の配列。最大 12 枚”
- stepinteger“表示するステップ数 (省略時は最終状態)”
- levelsarray“マップ文書: 撮る階層 (中身のあるノードの id。'' は全体)”
- selectstring“マップ文書: 選んで詳細パネルを開く部品の id”
- scalenumber“画像の縮尺 (既定: デッキ 0.5 = 960x540、マップ文書 0.75 = 960x600)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
open_deckcontrols a browser or desktopdescribed as changing data
“ユーザーの既定のブラウザでプレゼンテーション資料 (スライド・デッキ) を開く (発表・確認用。完成したら開いて見せる)。ローカルサーバー経由で開くので、ユーザーは E キーで文字を直して Ctrl+S で元のファイルに直接保存できる。fullscreen: true にすると Chrome / Edge を全画面 (タブ・アドレスバーなし) で起動する。ユーザーが「発表する」「全画面で開いて」…”
4 inputs, 1 required
- namestringrequired“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- levelstring“マップ文書: 開く階層・部品のノード id”
- fullscreenboolean“全画面の専用ウィンドウで開く (発表用。F11 / Esc で解除)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
repair_deckcreates or changes datadescribed as changing data
“ブラウザの「名前を付けて保存」で表示中の状態のまま保存されて壊れたデッキを、元の形式に復旧する (list_decks で broken と出るもの)。壊れたファイルは履歴に残る。復旧後は audit_deck と screenshot_deck で確認する。”
2 inputs, 1 required
- namestringrequired“デッキ名 (list_decks / create_deck が返す name。.html は不要)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”
export_deckon 3 other serverscreates or changes datadescribed as changing data
“デッキを 16:9 の PDF に出力する (アニメーションなし、全ステップ表示)。ユーザーが PDF を求めたときだけ使う (HTML のデッキファイル自体がそのまま配布・発表できるので、頼まれていなければ作らない)。マップ文書は階層ごとに 1 ページ (図 + その階層の部品の説明。A4 横)。”
2 inputs, 1 required
- namestringrequired“デッキかマップ文書の名前 (list_decks が返す name。.html は不要)”
- dirstring“デッキのフォルダ (省略時: AI クライアントの作業フォルダの decks/、作業フォルダがなければ既定のワークスペース)。作業フォルダからの相対パスか絶対パス。ユーザーが保存先を指定したときだけ渡す”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 24 tools
Says what it returns: 43% of 21 tools
States limits, defaults or errors: 0% of 24 tools
Says when to use it: 100% of 11 tools
Items covered per tool: 2.2 of 4 on average

Counted from the listing

Parameters with a description: 100% of 82
Tools with a description: 100% of 24
Typical description length: 154 characters

The tool set

Counted from the listing

Tools: 24
Size of the list: about 4,460 tokens for an agent to load (characters ÷ 4)
Naming: 24 of 24 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 24 of 24 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package jh-presentation

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "jh-presentation": {
      "command": "npx",
      "args": [
        "-y",
        "jh-presentation@0.8.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "jh-presentation": {
      "command": "npx",
      "args": [
        "-y",
        "jh-presentation@0.8.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "jh-presentation": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "jh-presentation@0.8.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"jh-presentation","type":"stdio","command":"npx","args":["-y","jh-presentation@0.8.0"]}'

Claude Code

claude mcp add --transport stdio jh-presentation -- npx -y jh-presentation@0.8.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y jh-presentation@0.8.0

Optional settings the entry also lists (left out above): JH_PRESENTATION_HOME, JH_PRESENTATION_DECKS_DIR, JH_PRESENTATION_MAPS_DIR, JH_PRESENTATION_ROOTS, CHROME_PATH.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.8.0
Latest stable: 0.8.0
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-1n/1zNtRqZihVChZp…
Signature: signed and attested
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 730 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.8.0 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/pei-jz/jh-presentation	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.pei-jz
GitHub owner: a personal account (pei-jz)
Build record: signed and attested

Repository: github.com/pei-jz/jh-presentation
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

#3,665 of 15,112 packages by monthly downloads, tied with 5 others
Not ranked by stars: 0 stars (ranked from 10)
#540 of 1,074 packages meeting all 9 record checks, by downloads

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.pei-jz/jh-presentation

Answered from the data above

Is io.github.pei-jz/jh-presentation safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 13 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.pei-jz/jh-presentation been security tested?

Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.pei-jz/jh-presentation do?

It lists 24 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and control a browser or desktop. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.pei-jz/jh-presentation change or delete data?

13 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.pei-jz/jh-presentation publish a security policy?

Yes: its repository has a public security policy (github.com/pei-jz/jh-presentation/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.8.0, the latest stable release on npm.

Where is the source code of io.github.pei-jz/jh-presentation?

In github.com/pei-jz/jh-presentation, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.raullenchai/vnshalso has tools that controls a browser or desktop, creates or changes data, reads or searchescompare with this one
io.github.MrGo2/icloud-mcpiCloud MCPalso has tools that controls a browser or desktop, creates or changes data, reads or searchescompare with this one
io.github.JonathanRReed/apple-tools-mcpApple Tools (Unified)also has tools that controls a browser or desktop, creates or changes data, reads or searchescompare with this one
io.github.Shuffzord/roadravenRoadRavenalso has tools that controls a browser or desktop, creates or changes data, reads or searchescompare with this one
com.xenition.api/xenitionXenitionalso has tools that controls a browser or desktop, creates or changes data, reads or searchescompare with this one
io.github.YashShelar007/rednote-gaterednote-gatealso has tools that controls a browser or desktop, creates or changes data, reads or searchescompare with this one

Active servers whose topic is also “productivity-and-docs” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

4 exercised9 not run (reason given)5 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 9

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against

Does not apply to this server · 5

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
5,813 msConnected after 0 redirects.
Read the inventory: 24 tools, 1 resource, 5 prompts.
6,645 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

productivity-and-docs

AI-classified (Gemini + Claude agreed) · 2026-10-23

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

730 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.pei-jz/jh-presentation: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.pei-jz/jh-presentation

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.pei-jz/jh-presentation)](https://protocolprobe.com/mcp/servers/io.github.pei-jz/jh-presentation)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology