MCP servers › ai.iceshore › iceshore

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

ai.iceshore/iceshore

Make your AI better at system maintenance. Prompts your AI to organize use cases behind each system. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: cloud-and-devops · AI-classifiedversion 1.0.0streamable HTTP16 tools

Summary

ai.iceshore/iceshore is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 16 tools, 20 resources and 2 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

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

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

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

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 16
Described as changing data: 8 of 16 toolsAI-classified
Mainly works on: files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic: cloud-and-devopsAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 8 tools whose name or declaration suggests they change data (create_content, save_content, request_upload_url, batch_request_upload_url, commit_uploaded_codes and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

8 tools are described as changing something (create_content, save_content, request_upload_url, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

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: 1.0.0, published 2026-10-05 (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)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22
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 1.0.0 (published 2026-10-05).

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

16tools

20resources

2prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

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

auth_checkon 1 other serverreads or searches
“IceShore への接続と認証の状態を返す。入力: なし。出力: 認証成功なら userId と所属組織一覧（organizations: workspace_id / name / role）、失敗（トークンの無効・失効など）なら error を含む文字列。 organizations[].workspace_id は、create_content / commit_uploaded_c…”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
list_projectson 157 other serversreads or searches
“ユーザが閲覧権限を持つプロジェクト（ADL 構成図）の一覧を返す（ログインが必要）。用途: 作業対象のプロジェクトの特定。業務影響・規模・依存関係を分析するときに、get_content で ADL を取る前の起点になる。ページング: 既定は page=0 / itemperpage=24。続きは page=1, 2, …。itemperpage の最大は 100。サンプルとの関係: ra…”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs
- rangestring“取得スコープのフィルタ。"related" (省略時の既定) = 自分が role を持つ構成図 + 自分の組織の構成図。誰でも見える公開構成図（公式サンプル）は足さない。"" = related に加えて公開構成図も含める（サンプルは list_samples を使うこと）。"bookmark" = bookmar…”
- pageinteger“0 起点のページ番号 (default 0)。default の itemperpage=24 件単位でページング。”
- itemperpageinteger“1 ページあたりの件数 (default 24、最大 100)。”
- workspace_idstring“特定の組織(ワークスペース)に絞り込む。auth_check が返す organizations[].workspace_id をそのまま渡す。複数組織に所属するユーザでも、指定した 1 組織が所有する案件のみが返るため、組織を跨いだ取りこぼし・混入を防げる。省略時は全所属組織の構成図が混在する。”
list_sampleson 6 other serversreads or searches
“【認証不要】匿名（未ログイン）でも使える。公式サンプルワークスペースの公開構成図の一覧を返す（ログイン時も公式サンプルワークスペースに固定）。用途: 新しい設計の参考事例、サンプルを土台にした作成。 list_projects との違い: list_projects は自分が閲覧権限を持つプロジェクト（サンプルを含まない）、本ツールは公式サンプルだけ。ページング: 既定は page=0 / …”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- pageinteger“0 起点のページ番号 (default 0)。default の itemperpage=24 件単位でページング。”
- itemperpageinteger“1 ページあたりの件数 (default 24、最大 100)。”
get_guideon 117 other serversreads or searches
“【認証不要】匿名（未ログイン）でも使える。IceShore のガイド文書（ADL の書き方・登録手順・分析の進め方など）を名前で返す。 MCP リソースに対応していないクライアント向けの取得手段で、対応クライアントは resources/read でも同じ内容を読める。主な名前: "analysis"（業務影響・依存・外部波及の分析）/ "registration"（システム登録）/ "fix…”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- namestringrequired“ガイド名。短縮名（例 "analysis" / "registration" / "fix" / "adl" / "saving-publishing"）または URI パス（例 "guide/analysis" / "skill/adl-validator"）。”
get_contenton 11 other serversreads or searches
“【認証不要（公式サンプルの公開コンテンツのみ）】匿名では公式サンプルだけを返し、それ以外はログインが必要（401）。IceShore プロジェクト 1 件の ADL と添付ファイルを返す。用途: 既存プロジェクトの参照、保存・更新の結果の確認（get_content(mode='detail') の戻りが保存後の実際の状態の正典）。 id は list_projects または list_sa…”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
- idstringrequired“IceShore プロジェクト ID（"d" で始まる内部ID。list_projects / create_content が返す id。例: d9289696c392a29e188.13397864。URL スラグの "I…" 形式は使用不可）”
- localestring“表示ロケール (en/ja 等)。省略時は en”
- modestring“取得モード。 - "meta" (速い・推奨デフォルト): 重い codes blob を S3 から読まない。overview/role 等のメタ情報のみ。10 秒以上短縮可。 - "root" (中): codes を adlRoot 1 件に絞る。ADL 構造だけ欲しい時。 - "detail" (既定値、重い…”
create_contenton 1 other servercreates or changes datadescribed as changing data
“新しい IceShore プロジェクトを作る（ADL と添付ファイルを登録する。ログインが必要）。既存プロジェクトの更新は save_content が扱う。 codes の形: 配列のうち 1 件が ADL 本体（id="adlRoot", isRoot=true, lang="adl", fmt="json", data=ADL を JSON.stringify した文字列）。残りはプロビジ…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
- codesarrayrequired“【必須形状】配列の中に必ず 1 件 id="adlRoot" isRoot=true lang="adl" fmt="json" のエントリを含めること。adlRoot.data は ADL 構造（reindeer/self/info/actors/resources/useCases/components）を JS…”
- overviewstringrequired“プロジェクト概要メタ。titles/descriptions（複数形・locale-keyed map）、version、type（visibility: "private"|"public"）、security（取扱情報種別: "publicHandling"|"confidentialHandling"|"pri…”
- workspace_idstring“登録先ワークスペース。"personal"（個人）または組織UUID（auth_check の organizations[].workspace_id）。【必須運用】依頼文（プロンプト）に登録先ワークスペースの指定があればその値を使う。指定が無い場合は auth_check で組織一覧を取得し、**必ずユーザーに登…”
save_contenton 2 other serverscreates or changes datadescribed as changing data
“既存の IceShore プロジェクトの ADL と添付ファイルを更新する（ログインが必要・所有者または admin / editor 権限）。新規作成は create_content が扱う。全置換（full-replace）: codes に渡したものがすべてになり、未指定の既存ファイルは削除される（allow_code_deletion を付けたときだけ削除を受け付ける）。既存ファイルを…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
5 inputs, 3 required
- idstringrequired“既存プロジェクトの id（"d" で始まる内部ID。list_projects / create_content が返す id）”
- codesarrayrequired“【必須形状】配列の中に必ず 1 件 id="adlRoot" isRoot=true lang="adl" のエントリを含める。adlRoot.data は ADL 構造を JSON.stringify した文字列。”
- overviewstringrequired“更新後のメタ情報。titles/descriptions（複数形・locale-keyed map）、security（取扱情報種別: "publicHandling"|"confidentialHandling"|"privacyHandling"）等を含む。type（公開設定）は private 固定。versi…”
- notesarray“AIが生成した変更サマリー。**配列**であること（文字列を渡すと引数エラーで拒否される）。例: [{ at: 1717200000, content: "S3バケット resource_storage を追加" }]。ここに入れた内容だけが構成図の「履歴」タブに変更サマリーとして残る（他に書き込む経路は無い）。”
- allow_code_deletionboolean“full-replace で未指定の既存コードを削除することを明示的に許可する。通常は不要（既存プロビジョニングを保持するには全 codes を送る）。”
request_upload_urlcreates or changes datadescribed as changing data
“プロビジョニングファイル 1 件分の、S3 への presigned PUT URL を発行する（ログインが必要）。ファイルが複数なら batch_request_upload_url が 1 回で N 件を発行する。返る upload_url は HTTP PUT でファイル本体を受け付ける（有効期限 10 分）。シェルを実行できるクライアントでの例: curl --silent --sho…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 3 required
- project_idstring“既存プロジェクトに追記する場合のみ指定。新規作成では未指定で呼び出すと、サーバが project_id を採番して返す。同じセッションの 2 回目以降は返ってきた project_id を渡す。”
- code_idstringrequired“プロビジョニングファイルのファイル名 (例 "main.tf" / "serverless.yml" / "template.yaml")。S3 のキーに直接使うので [A-Za-z0-9._-] のみ・最大 200 文字。”
- langstringrequired“カテゴリ。acf=CFn / tfm=Terraform / slf=Serverless / arm=ARM / gdm=GDM / cim=CIM / aro=ROS / oth=その他。【最頻出ミス】拡張子と取り違えるな。yaml/json は fmt フィールドに入れる”
- fmtstringrequired“ファイル形式 (json / yaml / hcl の 3 値のみ。.tf/.tfvars/.hcl→hcl、.yml→yaml)。”
batch_request_upload_urlcreates or changes datadescribed as changing data
“複数のプロビジョニングファイルの presigned PUT URL を、1 回の呼び出しで N 件（最大 100）発行する（ログインが必要）。各 upload_url は HTTP PUT でファイル本体を受け付ける（有効期限 10 分・並列可）。シェルを実行できるクライアントでの例: curl --silent --show-error --fail -X PUT --upload-fil…”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
2 inputs, 1 required
- project_idstring“既存プロジェクトに追記する場合のみ指定。新規作成では未指定で呼び出すと、サーバが project_id を採番して返す。”
- filesarrayrequired“アップロード対象のファイルメタ情報。同じ project_id に紐付く N 件をまとめて発行する。”
commit_uploaded_codescreates or changes datadescribed as changing data
“request_upload_url / batch_request_upload_url の URL へ PUT したファイルを、IceShore プロジェクトの codes に取り込む（ログインが必要）。新規プロジェクトはこの呼び出しで作られ、既存プロジェクトにはマージ（MERGE）で追記・更新し、指定しなかった既存ファイルは温存する。マージのルール: code_id が一致すれば上書き、…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
6 inputs, 2 required
- project_idstringrequired“request_upload_url で得た project_id を必ず渡す”
- adl_rootstring“ADL 構造を JSON.stringify した文字列。新規登録 (= request_upload_url で project_id を新規採番した最初の commit) では **必須**。既存プロジェクトの更新で構造を変えないなら省略可（既存値が保持される）。（旧称 cloud_design_root は後方…”
- cloud_design_rootstring“非推奨。adl_root の旧称。後方互換のため受け付ける。新規コードでは adl_root を使うこと。”
- code_entriesarrayrequired“curl PUT で staging に置いた各ファイルのメタデータ。**ファイル中身 (data) は含めない**（サーバが S3 staging から読む）。差分アップロードでは「変更したファイルだけ」を列挙する。空配列は cloud_design_root / overview 単体の更新時に許容。”
- overviewstring“プロジェクト概要メタ (titles / descriptions / version / security 等。titles/descriptions は複数形・locale-keyed map。security は取扱情報種別 "publicHandling"|"confidentialHandling"|"pr…”
- workspace_idstring“登録先ワークスペース（新規登録時のみ有効）。"personal"（個人）または組織UUID（auth_check の organizations[].workspace_id）。【必須運用】依頼文（プロンプト）に登録先ワークスペースの指定があればその値を使う。指定が無い場合は auth_check で組織一覧を取得し…”
list_codes_metareads or searches
“既存プロジェクトの codes 配列のメタデータ一覧を返す（ファイル中身 data は含まない）。差分アップロードの判定に使う。各エントリの sha256 は、data フィールド（文字列）を SHA-256 にかけた値。テキストファイルなら、ローカルの shasum -a 256 <file> の結果と一致する。 sha256 が一致するファイルは変更なしで、不一致または一覧に無いファイルだ…”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- project_idstringrequired“対象プロジェクトの id（"d" で始まる内部ID。list_projects が返す id）”
delete_codedeletesdescribed as changing data
“プロジェクトの codes から 1 件のファイルを削除する（ログインが必要）。ADL 本体（adlRoot）は削除できない（必要なら save_content の全置換）。 1 ファイル分の読み書きだけで済み、全 codes を送り直す save_content より速い。構成図は保存時にサーバ側で作り直される。入力: project_id, code_id（どちらも必須）。出力: { o…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- project_idstringrequired“IceShore プロジェクト ID”
- code_idstringrequired“削除するファイルの code_id (例 "old.tf")。adlRoot は不可。”

Show 4 more tools

get_noteson 4 other serversreads or searches
“プロジェクトの humanNote（人が ADL のノードに残した規範的な注意点）を返す（ログインが必要）。1 ノード（ref_path）につき有効なノートは最大 1 件。用途: 既存プロジェクトを編集するときの確認、人が編集した形跡（_meta.d が "h:" で始まる）のあるノードの参照、特定ノードについての質問への回答。 refs（任意・配列）: 取得するノードの ref_path。省…”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
- idstringrequired“IceShore プロジェクト ID（"d" で始まる内部ID。list_projects / create_content が返す id。例: d9289696c392a29e188.13397864。URL スラグの "I…" 形式は使用不可）”
- refsarray“対象ノードの ref_path 配列（例: ["#/actors/customer", "#/useCases/uc1/traffics/t1"]）。省略時は全件（500 件まで）”
add_noteon 22 other serverscreates or changes datadescribed as changing data
“ADL のノードに、規範的な注意点（humanNote）を保存する（ログインが必要・editor または admin 権限）。同じ ref_path への保存は上書き（UPSERT）で、1 ノードに有効なノートは最大 1 件。 text: 200 字以内。「〜のため〜にする」「〜なので〜禁止」の規範の形。固有名詞は書ける。1 ノードの複数の観点は 1 文にまとめて書く。 ref_path はサー…”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs, 4 required
- content_idstringrequired“IceShore プロジェクト ID（"d" で始まる内部ID。list_projects が返す id。"I…" 形式は使用不可）”
- ref_pathstringrequired“対象ノードの ref_path（例: "#/actors/customer", "#/useCases/uc1/traffics/t1"）。ADL 内に実在するノードを指すこと（サーバが照合し、外れると reason="ref_path_not_found" と candidates を返す）。`contexts` …”
- textstringrequired“規範形の注意点（200 文字以内）。"〜のため〜にする" / "〜なので〜禁止" の形式。事後報告や抽象表現は禁止”
- langstringrequired“ISO 639-1 言語コード（例: "en", "ja"）”
delete_noteon 8 other serversdeletesdescribed as changing data
“ADL ノードの humanNote を論理削除する（is_deleted=1・ログインが必要・editor または admin 権限）。行は消さないので、同じ ref_path に add_note すると復活する。入力: content_id, ref_path（どちらも必須）。出力: { ok, mode: "deleted"|"not_found" }。”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
- content_idstringrequired“IceShore プロジェクト ID（"d" で始まる内部ID。list_projects が返す id。"I…" 形式は使用不可）”
- ref_pathstringrequired“対象ノードの ref_path”
find_content_by_sourcereads or searches
“git の origin URL（またはローカルの絶対パス）から、IceShore のプロジェクト（ADL）を探す（ログインが必要）。用途: IaC のインポート前に、同じリポジトリがインポート済みかを調べる（済みなら更新 = save_content、未なら新規 = create_content の対象になる）。手順は iceshore://guide/iac-import に書いてある。 …”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- origin_urlstringrequired“リポジトリのgit remote origin URL。例: "git@github.com:org/repo.git" または "https://github.com/org/repo.git"。git remoteがない場合はリポジトリの絶対パスを使用。”

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 16 tools
Says what it returns: 63% of 16 tools
States limits, defaults or errors: 13% of 16 tools
Says when to use it: 100% of 9 tools
Items covered per tool: 2.4 of 4 on average

Counted from the listing

Parameters with a description: 100% of 42
Tools with a description: 100% of 16
Typical description length: 526 characters

The tool set

Counted from the listing

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

AI reading: easy to mix up

No pair found.

The AI items cover 16 of 16 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 remote endpoint (Streamable HTTP)

We connected to this URL 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.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.iceshore.ai/mcp

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

{
  "mcpServers": {
    "iceshore": {
      "url": "https://mcp.iceshore.ai/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "iceshore": {
      "type": "http",
      "url": "https://mcp.iceshore.ai/mcp"
    }
  }
}

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

code --add-mcp '{"name":"iceshore","type":"http","url":"https://mcp.iceshore.ai/mcp"}'

Claude Code

claude mcp add --transport http iceshore https://mcp.iceshore.ai/mcp

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

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.iceshore.ai/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
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.

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
Remote endpoint mcp.iceshore.ai/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. 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 ai.iceshore/iceshore

Answered from the data above

Is ai.iceshore/iceshore safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 8 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.

Does ai.iceshore/iceshore need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has ai.iceshore/iceshore been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can ai.iceshore/iceshore do?

It lists 16 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 delete. We did not call any tool, so this describes the text, not the behaviour.

Can ai.iceshore/iceshore change or delete data?

8 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.

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.Higangssh/homebutleralso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.Dave-London/pare-dockeralso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.vmware-skills/vmware-aiopsVMware AIopsalso has tools that creates or changes data, deletes, reads or searchescompare with this one
dev.uptimepage/uptimepageUptimepagealso has tools that creates or changes data, deletes, reads or searchescompare with this one
com.porkbun/mcpPorkbun (official)also has tools that creates or changes data, deletes, reads or searchescompare with this one
com.mcparmory/datadogalso has tools that creates or changes data, deletes, reads or searchescompare with this one

Active servers whose topic is also “cloud-and-devops” 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

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. 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 run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

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

Exercised · 5

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
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 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 a read-only session with the server's remote endpoint
2,099 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 16 tools, 20 resources, 2 prompts.
14,981 msFinished: 5 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

cloud-and-devops

AI-classified · 2026-10-23

Pricing modelAI-classified

not known (our limit)

The website shows almost no text without JavaScript, and we did not re-read it in a browser. This is our limit.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

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. “ai.iceshore/iceshore: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/ai.iceshore/iceshore

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/ai.iceshore/iceshore)](https://protocolprobe.com/mcp/servers/ai.iceshore/iceshore)

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