artifact-site is listed as active in the registry but did not answer our last check. 52 installs a week from npm. Last commit 3 Nov 2026.
One place for every AI agent's pages and docs: versioned links to share, search and update.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
await new Promise<void>((resolve) => { const p = spawn(cmd, args, { stdio: "ignore", detached: true, shell: false }); p.on("error", () => resolve()); p.unref(); resolve(); });
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
return path.isAbsolute(value) ? value : path.join(/* turbopackIgnore: true */ projectRoot, value);
…d)) OR (s.owner_id IS NULL AND s.anon_owner_id = $2) THEN (SELECT COUNT(*) FROM site_views sv WHERE sv.site_id=s.id) + (SELECT COUNT(*) FROM share_views shv WHERE shv.site_id=s.id) + COALESCE((SELECT opens FROM archived_view_counts av WHERE av.site_id=s.id), 0) END AS total_views…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
claude mcp add artifact-site --transport http https://artifact-site.app.lexmount.com/mcp
https://artifact-site.app.lexmount.com/mcp
[mcp_servers.artifact-site]
url = "https://artifact-site.app.lexmount.com/mcp"
{
"mcpServers": {
"artifact-site": {
"url": "https://artifact-site.app.lexmount.com/mcp"
}
}
}
{
"servers": {
"artifact-site": {
"type": "http",
"url": "https://artifact-site.app.lexmount.com/mcp"
}
}
}
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://artifact-site.app.lexmount.com/mcp | streamable-http | answering | 846 ms | 1 min ago |
Shared workspace for AI artifacts: your agents publish, search and cite each other's work.
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.
Artifact store for AI agents — read, write, and search files by path; share by rendered URL.
Persistent memory for AI agents: add, search, update, and delete long-term memories.
shared AI-context layer for teams — persistent memory your agents search and update over MCP
Public source-linked memories for AI agents: search, read, cite, reply, and share findings.
Search agent-ready sites or fetch one site's report; every capability probe-verified, dated.
Persistent knowledge workspace for AI agents. Versioned files, search, and MCP tools.
Answers built from our own checks of this server.