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.

Siteprint examples

REMOTE · SITEPRINT.APP

Website designs as DESIGN.md: real Siteprint exports of Linear, Stripe, Ramp and Cal.com.

Available components

+4 this week 71 Trust /100

Last scanned (21 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 16 Oct 2026.

Category Design and Media

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 Security74
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 167 tokens (~55/item across 3 items; 3 tools + 0 resources), lean.Pass
  • 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
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 9 Oct 26 67

    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 16 Oct 2026 · Probed https://siteprint.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=siteprint.app CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 5373c8a1a8d9616e0ecb9792384866aa
SANs: siteprint.app
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 siteprint.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
siteprint.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://siteprint.app/api/mcp Verified 200
http (plaintext) http://siteprint.app/api/mcp HTTPS enforced 301 https://siteprint.app/api/mcp
MCP tools · 3 exposed · ~127 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
get_example_design ~45

The DESIGN.md Siteprint exported from one example scan: exact colours, type, spacing, corners and layout as a design direction for new UI.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_setup ~44

How to connect Siteprint's local MCP server, which serves the person's own scans, to Claude Code, Cursor, Codex or another client.

NameTypeReqDescription
agentstring––

No output schema declared.

No examples provided.

list_example_designs ~38

Real Siteprint scans of four public sites, each with the original page a coding agent built from it. Returns ids for get_example_design.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Siteprint examples MCP server?

Siteprint examples is a hosted endpoint at https://siteprint.app/api/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 · siteprint.app

# add to Claude Code
claude mcp add --transport http app-siteprint-examples 'https://siteprint.app/api/mcp'
Common questions

What is the Siteprint examples MCP server?

Siteprint examples is an MCP server listed in the public MCP registry as app.siteprint/examples. Website designs as DESIGN.md: real Siteprint exports of Linear, Stripe, Ramp and Cal.com. This page covers its hosted endpoint (https://siteprint.app/api/mcp).

Is the Siteprint examples MCP server safe to use?

Siteprint examples scores 71 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 Siteprint examples MCP server expose?

Siteprint examples exposes 3 tools: list_example_designs, get_example_design, get_setup. Their descriptions and schemas cost roughly 127 tokens of context every time the server is loaded.

Does the Siteprint examples MCP server require authentication?

No. We connected to Siteprint examples without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Siteprint examples MCP server still maintained?

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