ai.artidrop/artidrop
ai.artidrop/artidrop · 1.1.0
Publish HTML, Markdown, and multi-file sites as shareable URLs instantly via MCP.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 20 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://artidrop.ai/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- artidrop 1.0.0
- Handshake time
- 179 ms
- HTTP status
- 200
The tools it lists (4, as of 10 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
publishPublish 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 model, use the REST endpoint `POST /v1/artifacts` (or `/v1/artifacts/upload` for ZIPs) instead. For Markdown, optionally include images as base64-encoded data.
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.
getGet artifact metadata. Set include_content to true to also return the full HTML content.
versionsList version history of an artifact
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.artidrop/artidrop, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 176 days ago. The registry entry