Imagerelay MCP Server

imagerelay-mcp-server npm v2.0.4

Published by oliverames — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
B
89/100
Last scanned get badge →
Trust
B · 89/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
Critical
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.
B Why this grade threat 100 − adoption risk = 89/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 − 11 = 89. 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
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 15

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: ir_create_folder_link → ir_get_collection_files ⇒ ir_create_webhook. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow ir_create_folder_link → ir_get_collection_files → ir_create_webhook

high Shell/command execution in server code (dist/op-fallback.js)MTC-SRC-002

In the server's implementation (`dist/op-fallback.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ecFileSync } from "node:child_process"; /** * If the given env var is empty, attempt to resolve it from 1Password CLI.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/op-fallback.js

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

Tool "ir_upload_file_from_url" 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 ir_upload_file_from_url · inputSchema.properties.url

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

Tool "ir_create_webhook" 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 ir_create_webhook · inputSchema.properties.url

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

Tool "ir_update_webhook" 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 ir_update_webhook · inputSchema.properties.url

medium Tool "ir_move_file" can modify the filesystemMTC-CAP-002

Tool "ir_move_file" can write, overwrite or delete files (keyword "move_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool ir_move_file

medium Tool "ir_delete_file" can modify the filesystemMTC-CAP-002

Tool "ir_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool ir_delete_file

medium Tool "ir_create_file_version" can modify the filesystemMTC-CAP-002

Tool "ir_create_file_version" can write, overwrite or delete files (keyword "create_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool ir_create_file_version

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

Tool "ir_move_file" 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 ir_move_file

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

Tool "ir_delete_file" 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 ir_delete_file

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

Tool "ir_create_file_version" 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 ir_create_file_version

low Unconstrained path parameter "file_type_id" on "ir_get_files"MTC-CAP-008

Tool "ir_get_files" takes a path parameter "file_type_id" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool ir_get_files · inputSchema.properties.file_type_id

low Unconstrained path parameter "file_id" on "ir_move_file"MTC-CAP-008

Tool "ir_move_file" takes a path parameter "file_id" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool ir_move_file · inputSchema.properties.file_id

low Unconstrained path parameter "file_id" on "ir_delete_file"MTC-CAP-008

Tool "ir_delete_file" takes a path parameter "file_id" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool ir_delete_file · inputSchema.properties.file_id

low Unconstrained path parameter "file_id" on "ir_create_file_version"MTC-CAP-008

Tool "ir_create_file_version" takes a path parameter "file_id" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool ir_create_file_version · inputSchema.properties.file_id

Tools 102

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

  • ir_upload_file_from_urlingests untrusted inputnetwork egress
  • ir_create_file_versionwrites files
  • ir_create_folder_linkingests untrusted input
  • ir_create_quick_linkingests untrusted input
  • ir_create_webhooknetwork egress
  • ir_delete_filewrites files
  • ir_delete_webhooknetwork egress
  • ir_get_collection_filesreads sensitive data
  • ir_get_filesreads sensitive data
  • ir_get_supported_webhooksnetwork egress
Show 92 more tools ↓
  • ir_get_upload_linksnetwork egress
  • ir_get_webhooknetwork egress
  • ir_move_filewrites files
  • ir_update_webhooknetwork egress
  • ir_add_dimension_optionno sensitive capability
  • ir_auth_statusno sensitive capability
  • ir_check_upload_job_statusno sensitive capability
  • ir_complete_file_versionno sensitive capability
  • ir_create_catalogno sensitive capability
  • ir_create_collectionno sensitive capability
  • ir_create_custom_attributeno sensitive capability
  • ir_create_dimensionno sensitive capability
  • ir_create_folderno sensitive capability
  • ir_create_keywordno sensitive capability
  • ir_create_keyword_setno sensitive capability
  • ir_create_productno sensitive capability
  • ir_create_sso_userno sensitive capability
  • ir_create_synced_fileno sensitive capability
  • ir_create_templateno sensitive capability
  • ir_create_upload_jobno sensitive capability
  • ir_create_upload_linkno sensitive capability
  • ir_create_variantno sensitive capability
  • ir_delete_catalogno sensitive capability
  • ir_delete_collectionno sensitive capability
  • ir_delete_folderno sensitive capability
  • ir_delete_folder_linkno sensitive capability
  • ir_delete_invited_userno sensitive capability
  • ir_delete_keywordno sensitive capability
  • ir_delete_productno sensitive capability
  • ir_delete_quick_linkno sensitive capability
  • ir_delete_upload_linkno sensitive capability
  • ir_delete_variantno sensitive capability
  • ir_duplicate_fileno sensitive capability
  • ir_get_catalogno sensitive capability
  • ir_get_catalog_productsno sensitive capability
  • ir_get_catalogsno sensitive capability
  • ir_get_categoriesno sensitive capability
  • ir_get_categoryno sensitive capability
  • ir_get_channel_template_mappingsno sensitive capability
  • ir_get_child_foldersno sensitive capability
  • ir_get_collectionno sensitive capability
  • ir_get_collectionsno sensitive capability
  • ir_get_custom_attributeno sensitive capability
  • ir_get_custom_attributesno sensitive capability
  • ir_get_dimensionno sensitive capability
  • ir_get_dimensionsno sensitive capability
  • ir_get_fileno sensitive capability
  • ir_get_file_typeno sensitive capability
  • ir_get_file_typesno sensitive capability
  • ir_get_folderno sensitive capability
  • ir_get_folder_linkno sensitive capability
  • ir_get_folder_linksno sensitive capability
  • ir_get_foldersno sensitive capability
  • ir_get_invited_userno sensitive capability
  • ir_get_invited_usersno sensitive capability
  • ir_get_keywordno sensitive capability
  • ir_get_keyword_setno sensitive capability
  • ir_get_keyword_setsno sensitive capability
  • ir_get_keywordsno sensitive capability
  • ir_get_meno sensitive capability
  • ir_get_permissionno sensitive capability
  • ir_get_permissionsno sensitive capability
  • ir_get_productno sensitive capability
  • ir_get_product_catalogno sensitive capability
  • ir_get_product_variantno sensitive capability
  • ir_get_product_variantsno sensitive capability
  • ir_get_productsno sensitive capability
  • ir_get_quick_linkno sensitive capability
  • ir_get_quick_linksno sensitive capability
  • ir_get_root_folderno sensitive capability
  • ir_get_templateno sensitive capability
  • ir_get_templatesno sensitive capability
  • ir_get_upload_linkno sensitive capability
  • ir_get_userno sensitive capability
  • ir_get_user_quick_linksno sensitive capability
  • ir_get_usersno sensitive capability
  • ir_get_webhooksno sensitive capability
  • ir_invite_userno sensitive capability
  • ir_search_usersno sensitive capability
  • ir_update_catalogno sensitive capability
  • ir_update_collectionno sensitive capability
  • ir_update_custom_attributeno sensitive capability
  • ir_update_dimensionno sensitive capability
  • ir_update_file_metadatano sensitive capability
  • ir_update_file_tagsno sensitive capability
  • ir_update_folderno sensitive capability
  • ir_update_keywordno sensitive capability
  • ir_update_keyword_setno sensitive capability
  • ir_update_productno sensitive capability
  • ir_update_templateno sensitive capability
  • ir_update_user_permissionno sensitive capability
  • ir_update_variantno 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
v2.0.4 latest B 89/100 15 1.9.0 2026-07-24

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: B · 89/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/imagerelay-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/imagerelay-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/imagerelay-mcp-server"><img src="https://mcptrustchecker.com/registry/imagerelay-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/imagerelay-mcp-server/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 imagerelay-mcp-server --online

Use the free API → How scoring works

More in Developer Tools