Skip to content

blink artifact (no account) MCP server

com.blinkbrosai/artifact-tryblinkbrosai.comstreamable-httpv1.0.0Scanned

Publish a temporary HTML page from your agent with no account or token; public link, 7 days.

2 tools: 1 do something that can't be undone and 1 change things.

Tools: 0 delete, 1 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the blink artifact (no account) MCP server can do

The blink artifact (no account) MCP server is published by blinkbrosai.com, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_html) and create or change data (1 tool: update_html), but cannot delete data. None of its tools only reads.

1 tool can send data out of your system (publish_html).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 10, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Can't be undone 1Claude Code: ask
  • publish_htmlPublish a single self-contained HTML page (up to 512 KiB) without an account.Can send data outNo findings

    Why it is in this group

    • The name "publish_html" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "publish_html" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish a single self-contained HTML page (up to 512 KiB) without an account. It is public to anyone with the link and expires after 7 days. Returns { id, url, expiresAt (unix seconds), key, claimUrl }. Show the user url and claimUrl; keep key secret.

    Annotations the server declares

    • title: Publish HTML
    • readOnlyHint: false
    • destructiveHint: false
Changes things 1Claude Code: ask
  • update_htmlReplace the HTML of a page you published earlier with publish_html, using its id and key.No findings

    Why it is in this group

    • The name "update_html" says "update": a word for a change.
    Description, as the server wrote it
    Replace the HTML of a page you published earlier with publish_html, using its id and key. The link and expiry stay the same. Fails with not_found for a wrong key and gone when the page expired, was removed or was claimed. Returns { id, url, expiresAt (unix seconds), key, claimUrl }. Show the user url and claimUrl; keep key secret.

    Annotations the server declares

    • title: Update HTML
    • readOnlyHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 20, 2026, 18:23 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
410
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://artifact.blinkbrosai.com/.well-known/oauth-protected-resource
Authorization servers
https://artifact.blinkbrosai.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

The probe stopped: initialize answered HTTP 410.

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 200 to 410
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 410
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http artifact-try https://artifact.blinkbrosai.com/try/mcp
claude mcp add --transport http artifact-try https://artifact.blinkbrosai.com/try/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__artifact-try__publish_html",
      "mcp__artifact-try__update_html"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as artifact-try. Review it before you use it.

Capability tags behind 1 rule
  • mcp__artifact-try__publish_html outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.blinkbrosai/artifact-try/verify?hash=8c85bb4c08decbc0175d6dd95cfe13552f67aa416b6307b6ee7141b8db951acc" | jq -e '.changed == false'

Pinned hash 8c85bb4c08de, from Nov 10, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.blinkbrosai/artifact-try/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.blinkbrosai/artifact-try
[![Anlyon Radar](https://radar.anlyon.com/badge/com.blinkbrosai/artifact-try.svg)](https://radar.anlyon.com/servers/com.blinkbrosai/artifact-try)

Source: MCP Registry. Synced Oct 29, 2026, 11:17 UTC.

blink artifact (no account) MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the blink artifact (no account) MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the blink artifact (no account) MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the blink artifact (no account) MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_html.

What tools does the blink artifact (no account) MCP server have?

2 tools: 1 irreversible, 1 write. publish_html and update_html.

Does the blink artifact (no account) MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the blink artifact (no account) MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_html.

Has the blink artifact (no account) MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.