Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Artifact Publisher

REMOTE · APP.ARTIFACTPUBLISHER.COM

Agents publish self-contained HTML to a stable review link, with page-level feedback and revoke.

70 Trust /100

Last scanned (17 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 22 Oct 2026.

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1541 tokens (~128/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 21 Oct 26 +1
    • Tool “configure_workspace” rewrote its description, which is the text the model reads security
    • Tool “get_artifact_state” rewrote its description, which is the text the model reads security
    • Tool “get_authoring_guide” rewrote its description, which is the text the model reads security
    • Tool “get_feedback” rewrote its description, which is the text the model reads security
    • Tool “publish_artifact” rewrote its description, which is the text the model reads security
    • Tool “reply_to_feedback” rewrote its description, which is the text the model reads security
    • Tool “reset_artifact_state” rewrote its description, which is the text the model reads security
    • Tool “revoke_artifact” rewrote its description, which is the text the model reads security
    • Tool “set_artifact_access” rewrote its description, which is the text the model reads security
    • Tool “set_artifact_state” rewrote its description, which is the text the model reads security
    • Tool “update_artifact” rewrote its description, which is the text the model reads security
    • Tool “configure_workspace” is now declared destructive security
    • Tool “set_artifact_access” is now declared destructive security
    • Tool “set_artifact_state” is now declared destructive security
    • Tool “update_artifact” is now declared destructive security
    • “publish_artifact” reworded the description of “visibility” cosmetic
  • 20 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Oct 26 69

    First indexed and scored.

Diagnostics

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 22 Oct 2026 · Probed https://app.artifactpublisher.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=artifactpublisher.com CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 7db9a5e129163bfd0efa75ef6ecaf3d1
SANs: artifactpublisher.com, app.artifactpublisher.com, *.app.artifactpublisher.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.artifactpublisher.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
artifactpublisher.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="Artifact Publisher MCP"

Bearer realm="Artifact Publisher MCP"
Header Value
content-security-policy default-src 'none'; script-src 'sha256-dKLlXsJpkEXIZvA76HxDxzawXsF8VBbjXCJxJjdz+Eo=' https://static.cloudflareinsights.com; style-src 'sha256-EaD6Qeac+LOObD1iS/cYnCSWGK6NDbrgxPxRTQV+ePg='; img-src 'self' data:; connect-src 'self' https://cloudflareinsights.com; frame-src https://artifacts.artifactpublisher.com; form-action 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.artifactpublisher.com/mcp Verified 200
http (plaintext) http://app.artifactpublisher.com/mcp HTTPS enforced 301 https://app.artifactpublisher.com/mcp
MCP tools · 12 exposed · ~1,366 tokens

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 →

Tool Tokens
configure_workspace ~112

Read or update workspace defaults (comments_enabled, default_expiry_seconds, default_artifact_title); pass empty settings to read. Platform guardrails are refused with an error: max_artifact_bytes, storage_bytes_limit, monthly_versions_limit, rate_limits, comment_rate_limit, publish_rate_limit, isolation, origins, artifact_origin, control_origin, storage_key_prefix, object_key_prefix, security_headers, content_security_policy. Not available in every workspace.

NameTypeReqDescription
settingsobjectyes–
workspace_idstring––

No output schema declared.

No examples provided.

get_artifact_state ~86

Read an artifact's state. Shared JSON key/value state, synced to viewers across versions (page JS: ArtifactRelayState). Last write wins per key. Limits: 200 keys, 16 KiB per value, 64 KiB total. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
artifact_idstringyes–
workspace_idstring––

No output schema declared.

No examples provided.

get_authoring_guide ~76

Read before writing HTML or a routine: themes, ap-* layout classes, an example page, the snippet, size, sandbox and routine rules. Optional theme (firn, firn@1) is validated and returned as selected.

NameTypeReqDescription
themestring–Validate one theme (firn, firn@1).

No output schema declared.

No examples provided.

get_feedback ~132

Read reviewer comments on an artifact, oldest first; use after sharing or to poll. Filters: unresolved_only, since; version (default current) picks the version anchor_status is checked against. Page with limit and cursor. Returns comments, unresolved_count, next_cursor. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
artifact_idstringyes–
cursorstring–Pass next_cursor.
limitinteger–Page size; default 50.
sincestring––
unresolved_onlyboolean––
versioninteger––
workspace_idstring––

No output schema declared.

No examples provided.

list_artifacts ~60

List artifacts in this key's workspace, newest first, with unresolved comment counts. Pass `next_cursor` back as `cursor` to page.

NameTypeReqDescription
cursorstring––
limitinteger––
workspace_idstring––

No output schema declared.

No examples provided.

publish_artifact ~260

Publish self-contained HTML as version 1; return a share link. Optional Idempotency-Key HTTP header. Limit 10 MiB UTF-8; larger on some paid plans. No network in sandbox; inline assets. Free: 5 active artifacts, 50 versions. For styling, add <meta name="ap-theme" content="firn"> to <head>; call get_authoring_guide for themes and layout classes.

NameTypeReqDescription
allowed_emailsarray–Required for allowlist; omit otherwise.
comments_enabledboolean–Defaults to the workspace setting.
expires_at––ISO 8601 UTC, 60 s to 365 days ahead; null = never; omit = workspace default.
htmlstringyes–
summarystring––
titlestring––
visibilitystring–public = anyone with link, no sign-in, not listed or searchable (alias: unlisted); private = owner only; allowlist = listed primary emails, account required. Default: public. `team` (some workspaces)…
workspace_idstring––

No output schema declared.

No examples provided.

reply_to_feedback ~83

Reply once to a comment (a second reply fails with conflict); resolve: true also marks it resolved. Anyone who can open the artifact can read the reply. Refused on revoked or expired artifacts. Returns the comment.

NameTypeReqDescription
comment_idstringyes–
messagestringyes–
resolveboolean––
workspace_idstring––

No output schema declared.

No examples provided.

reset_artifact_state ~92

Clear all state, including board values; HTML is unchanged. Shared JSON key/value state, synced to viewers across versions (page JS: ArtifactRelayState). Last write wins per key. Limits: 200 keys, 16 KiB per value, 64 KiB total. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
artifact_idstringyes–
workspace_idstring––

No output schema declared.

No examples provided.

revoke_artifact ~57

Stop serving this artifact (410 Gone). Cannot undo; viewed copies exist. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
artifact_idstringyes–
reasonstring––
workspace_idstring––

No output schema declared.

No examples provided.

set_artifact_access ~88

Change an artifact's access mode without a new version. For accountless coworkers use public, not allowlist. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
allowed_emailsarray–Required for allowlist; omit otherwise.
artifact_idstringyes–
visibilitystringyesModes as in publish_artifact.visibility.
workspace_idstring––

No output schema declared.

No examples provided.

set_artifact_state ~157

Set the given keys atomically; other keys stay. Null is stored, not deleted. Shared JSON key/value state, synced to viewers across versions (page JS: ArtifactRelayState). Last write wins per key. Limits: 200 keys, 16 KiB per value, 64 KiB total. Page JS: ArtifactRelayState.subscribe(fn)/set(k,v)/patch(obj); callbacks get {revision, values, resetAt}; set/patch reject on failure; whole-value writes, no increments or nested merges. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
artifact_idstringyes–
valuesobjectyesKeys to JSON values; depth max 16.
workspace_idstring––

No output schema declared.

No examples provided.

update_artifact ~163

Append a new immutable version to an existing artifact. `expected_version` must equal the current version; the share link moves to the new version; earlier versions stay readable at their pinned URL. Optional `title` renames; with no `html` only the title changes. Each version counts toward the free 50 version cap. For styling, add <meta name="ap-theme" content="firn"> to <head>; call get_authoring_guide for themes and layout classes. artifact_id: id, slug or viewer URL.

NameTypeReqDescription
artifact_idstringyes–
expected_versionintegeryes–
htmlstring––
release_notestring––
titlestring––
workspace_idstring––

No output schema declared.

No examples provided.

Install

How do I install the Artifact Publisher MCP server?

Artifact Publisher is a hosted endpoint at https://app.artifactpublisher.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.artifactpublisher.com

# add to Claude Code
claude mcp add --transport http com-artifactpublisher-mcp 'https://app.artifactpublisher.com/mcp'
Common questions

What is the Artifact Publisher MCP server?

Artifact Publisher is an MCP server listed in the public MCP registry as com.artifactpublisher/mcp. Agents publish self-contained HTML to a stable review link, with page-level feedback and revoke. This page covers its hosted endpoint (https://app.artifactpublisher.com/mcp).

Is the Artifact Publisher MCP server safe to use?

Artifact Publisher scores 70 out of 100 on VerifyMCP. 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 Artifact Publisher MCP server expose?

Artifact Publisher exposes 12 tools: publish_artifact, update_artifact, set_artifact_access, get_feedback, reply_to_feedback, and 7 more. Their descriptions and schemas cost roughly 1,366 tokens of context every time the server is loaded.

Does the Artifact Publisher MCP server require authentication?

Yes. Artifact Publisher asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Artifact Publisher MCP server still maintained?

Artifact Publisher is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.