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

Skew

REMOTE · SKEW.SITE · SCANNED AUG 3

Authored design service: one-of-one landing pages, pitch decks, and research-grounded briefs.

Available components

+8 this week 79 Trust /100
Trust breakdown (6 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 →

Endpoint Security97
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 268 tokens (~67/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · skew.site

# add to Claude Code
claude mcp add --transport http site-skew-skew https://skew.site/api/mcp
# ~/.codex/config.toml
[mcp_servers.site-skew-skew]
url = "https://skew.site/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-skew-skew": {
      "type": "remote",
      "url": "https://skew.site/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add site-skew-skew --url https://skew.site/api/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  site-skew-skew:
    url: "https://skew.site/api/mcp"
// mcp.json
{
  "mcpServers": {
    "site-skew-skew": {
      "type": "http",
      "url": "https://skew.site/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 3 Aug 26 +1

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

  • 31 Jul 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 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.

  • 28 Jul 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.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 71

    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 3 Aug 2026 · Probed https://skew.site/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=skew.site CN=YR2,O=Let's Encrypt,C=US 22 Jun 2026 20 Sept 2026 RSA 2048 SHA256-RSA 5166c71cde6f3415f21a6b6e93c744065a8
SANs: skew.site
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of skew.site. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
site. present 31826 13 Verified
skew.site. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://skew.site/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://skew.site/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy accelerometer=(), camera=(), geolocation=(), microphone=(), payment=(), usb=()

Protected resource metadata

Document https://skew.site/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://skew.site
Authorisation server https://boss-hermit-56.clerk.accounts.dev
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://skew.site/api/mcp Verified 200
http (plaintext) http://skew.site/api/mcp HTTPS enforced 308 https://skew.site/api/mcp
MCP tools — 4 exposed · ~268 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.

Tool Tokens
fetch_artifact ~47

Retrieve a previously generated artifact (landing, deck, or brief) by slug. Returns HTML.

NameTypeReqDescription
slugstringyesThe artifact slug.
typestringyesArtifact type.

No output schema declared.

No examples provided.

generate_brief ~68

Generate a research-grounded brief from a topic and optional source URLs. Persists on stream close at /b/{slug}.

NameTypeReqDescription
personastringOptional persona override.
researchUrlsarrayOptional sources to anchor the brief.
topicstringyesThe brief subject.

No output schema declared.

No examples provided.

generate_deck ~72

Generate a one-of-one pitch deck from a brief and slide count. Persists on stream close at /d/{slug}.

NameTypeReqDescription
briefstringyesThe one-paragraph deck brief.
personastringOptional persona override.
slideCountintegerNumber of slides (default 10).

No output schema declared.

No examples provided.

generate_landing ~81

Stream a one-of-one landing page from a one-paragraph brief. Persists on stream close at /p/{slug}.

NameTypeReqDescription
briefstringyesThe one-paragraph design brief.
personastringOptional persona override. Auto-routes if omitted.
referenceImageUrlsarrayOptional reference images for source-anchored generation.

No output schema declared.

No examples provided.