Publish HTML, Markdown, and multi-file sites as shareable URLs instantly via MCP.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://artidrop.ai/mcp4 tools · 166mspublishPublish HTML or Markdown content as a shareable URL. Pass `content` byte-for-byte from the source — do not retype, reformat, minify, summarize, or 'clean up' the input; even one stray character can break inline scripts on the published page. If the content is too large to copy verbatim through the…Publish HTML or Markdown content as a shareable URL. Pass `content` byte-for-byte from the source — do not retype, reformat, minify, summarize, or 'clean up' the input; even one stray character can break inline scripts on the published page. If the content is too large to copy verbatim through the…
| Parameter | Type | Description |
|---|---|---|
| content* | string | The HTML or Markdown content to publish. Copy this verbatim from the source file or buffer — do not modify, reformat, or regenerate it. Whitespace, emojis, com… |
| format* | string | Content format |
| title | string | Artifact title (default: Untitled) |
| visibility | string | Visibility (default: unlisted) |
| images | array | Images referenced in the markdown content. Only used when format is 'markdown'. |
publish_sitePublish a multi-file HTML site from a base64-encoded ZIP file. The ZIP must contain an index.html at its root. For sites larger than ~10MB — or whenever you have the file on disk — prefer the REST API /v1/artifacts/upload endpoint to avoid base64 overhead and to guarantee byte-faithful upload.Publish a multi-file HTML site from a base64-encoded ZIP file. The ZIP must contain an index.html at its root. For sites larger than ~10MB — or whenever you have the file on disk — prefer the REST API /v1/artifacts/upload endpoint to avoid base64 overhead and to guarantee byte-faithful upload.
| Parameter | Type | Description |
|---|---|---|
| zip_base64* | string | Base64-encoded ZIP file containing the site files |
| title | string | Site title (default: Untitled) |
| visibility | string | Visibility (default: unlisted) |
getGet artifact metadata. Set include_content to true to also return the full HTML content.Get artifact metadata. Set include_content to true to also return the full HTML content.
| Parameter | Type | Description |
|---|---|---|
| id* | string | Artifact ID or short ID |
| include_content | boolean | Include the full HTML content in the response (default: false) |
versionsList version history of an artifactList version history of an artifact
| Parameter | Type | Description |
|---|---|---|
| id* | string | Artifact ID |
4 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Publish HTML, Markdown, and multi-file sites as shareable URLs instantly via MCP.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.