io.github.Whitemarmot/markly
NPM · MARKLY-MCP-SERVER · SCANNED SEP 20
Add text or logo watermarks to images via the Markly.cloud API. Batch supported.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 199 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 487 tokens (~121/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the io.github.Whitemarmot/markly MCP server?
io.github.Whitemarmot/markly runs locally as an npm package, launched with npx -y markly-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · markly-mcp-server
claude mcp add whitemarmot-markly -- npx -y markly-mcp-server
{
"mcpServers": {
"whitemarmot-markly": {
"command": "npx",
"args": [
"-y",
"markly-mcp-server"
]
}
}
} {
"servers": {
"whitemarmot-markly": {
"command": "npx",
"args": [
"-y",
"markly-mcp-server"
]
}
}
} codex mcp add whitemarmot-markly -- npx -y markly-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"whitemarmot-markly": {
"type": "local",
"command": [
"npx",
"-y",
"markly-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add whitemarmot-markly --command npx --arg -y --arg markly-mcp-server
mcp_servers:
whitemarmot-markly:
command: "npx"
args: ["-y", "markly-mcp-server"] {
"McpServers": {
"whitemarmot-markly": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"markly-mcp-server"
]
}
}
} assistant mcp add whitemarmot-markly -t stdio -c npx -a -y markly-mcp-server
{
"mcpServers": {
"whitemarmot-markly": {
"command": "npx",
"args": [
"-y",
"markly-mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.77 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 10 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 8 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/markly-mcp-server@1.2.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 →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
markly_batch_watermark ~144
Watermark multiple images at once. Upload image URLs, apply text watermark, get a ZIP. Supports up to 20 images.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Hex color (e.g. #ffffff) |
| image_urls | array | yes | Array of image URLs to watermark (max 20) |
| opacity | number | – | Opacity percentage (5-100, default 50) |
| position | string | – | Watermark position |
| size | number | – | Font size in pixels (12-200, default 48) |
| text | string | yes | Watermark text to apply to all images |
| tile | boolean | – | Tile watermark across all images |
No output schema declared.
No examples provided.
markly_check_usage ~32
Check your Markly API usage and quota. Shows plan, daily requests, limits, and total images processed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
markly_watermark_logo ~124
Add a logo/image watermark to an image. Provide image and logo URLs. Returns a download URL (valid 30 min).
| Name | Type | Req | Description |
|---|---|---|---|
| image_url | string | yes | URL of the image to watermark |
| logo_url | string | yes | URL of the logo to use as watermark (PNG or WebP recommended) |
| opacity | number | – | Opacity percentage (5-100, default 50) |
| position | string | – | Logo position (default center) |
| scale | number | – | Logo scale as % of image width (5-80, default 20) |
No output schema declared.
No examples provided.
markly_watermark_text ~187
Add a text watermark to an image. Provide an image URL and watermark text. Returns a download URL (valid 30 min).
| Name | Type | Req | Description |
|---|---|---|---|
| angle | number | – | Rotation angle in degrees (-180 to 180, default -30) |
| color | string | – | Hex color (e.g. #ffffff, default white) |
| font | string | – | Font (default inter) |
| image_url | string | yes | URL of the image to watermark (must be publicly accessible) |
| opacity | number | – | Opacity percentage (5-100, default 50) |
| position | string | – | Watermark position (default center) |
| size | number | – | Font size in pixels (12-200, default 48) |
| text | string | yes | Watermark text (max 200 characters) |
| tile | boolean | – | Tile the watermark across the entire image (default false) |
No output schema declared.
No examples provided.
What is the io.github.Whitemarmot/markly MCP server?
io.github.Whitemarmot/markly is an MCP server listed in the public MCP registry as io.github.Whitemarmot/markly. Add text or logo watermarks to images via the Markly.cloud API. Batch supported. This page covers its npm package (markly-mcp-server).
Is the io.github.Whitemarmot/markly MCP server safe to use?
io.github.Whitemarmot/markly scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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.Whitemarmot/markly MCP server expose?
io.github.Whitemarmot/markly exposes 4 tools: markly_watermark_text, markly_watermark_logo, markly_batch_watermark, markly_check_usage. Their descriptions and schemas cost roughly 487 tokens of context every time the server is loaded.
Is the io.github.Whitemarmot/markly MCP server still maintained?
io.github.Whitemarmot/markly is still listed as active in the MCP registry. We last reached this channel on 20 September 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.Whitemarmot/markly MCP server under?
io.github.Whitemarmot/markly declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.