blink artifact (no account)
REMOTE · ARTIFACT.BLINKBROSAI.COM
Publish a temporary HTML page from your agent with no account or token; public link, 7 days.
Available components
Last scanned (5 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 303 tokens (~151/item across 2 items; 2 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 70
First indexed and scored.
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 5 Nov 2026 · Probed https://artifact.blinkbrosai.com/try/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blinkbrosai.com | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 45bb39f2601f1fc21341ac336b0a35a5 |
| SANs: blinkbrosai.com, artifact.blinkbrosai.com, *.artifact.blinkbrosai.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 secure
Validation of artifact.blinkbrosai.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| blinkbrosai.com. | present | 2371 | 13 | Verified |
| artifact.blinkbrosai.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://artifact.blinkbrosai.com/try/mcp | Verified | 200 | |
| http (plaintext) | http://artifact.blinkbrosai.com/try/mcp | HTTPS enforced | 301 | https://artifact.blinkbrosai.com/try/mcp |
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 →
publish_html Publish HTML ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | – |
No output schema declared.
No examples provided.
update_html Update HTML ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | – |
| id | string | yes | – |
| key | string | yes | – |
No output schema declared.
No examples provided.
How do I install the blink artifact (no account) MCP server?
blink artifact (no account) is a hosted endpoint at https://artifact.blinkbrosai.com/try/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 · artifact.blinkbrosai.com
claude mcp add --transport http com-blinkbrosai-artifact-try 'https://artifact.blinkbrosai.com/try/mcp'
What is the blink artifact (no account) MCP server?
blink artifact (no account) is an MCP server listed in the public MCP registry as com.blinkbrosai/artifact-try. Publish a temporary HTML page from your agent with no account or token; public link, 7 days. This page covers its hosted endpoint (https://artifact.blinkbrosai.com/try/mcp).
Is the blink artifact (no account) MCP server safe to use?
blink artifact (no account) scores 73 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 blink artifact (no account) MCP server expose?
blink artifact (no account) exposes 2 tools: publish_html, update_html. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.
Does the blink artifact (no account) MCP server require authentication?
No. We connected to blink artifact (no account) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the blink artifact (no account) MCP server still maintained?
blink artifact (no account) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.