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.

Systra Tools

REMOTE · SYSTRA.TOOLS · SCANNED SEP 25

Search and pull 500+ production-ready React + Tailwind sections and elements

Available components

+3 this week 76 Trust /100
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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 855 tokens (~65/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
Install

How do I install the Systra Tools MCP server?

Systra Tools is a hosted endpoint at https://systra.tools/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 · systra.tools

# add to Claude Code
claude mcp add --transport http tools-systra-systra-tools 'https://systra.tools/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "tools-systra-systra-tools": {
      "url": "https://systra.tools/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tools-systra-systra-tools": {
      "type": "http",
      "url": "https://systra.tools/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.tools-systra-systra-tools]
url = "https://systra.tools/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tools-systra-systra-tools": {
      "type": "remote",
      "url": "https://systra.tools/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add tools-systra-systra-tools --url 'https://systra.tools/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tools-systra-systra-tools:
    url: "https://systra.tools/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tools-systra-systra-tools": {
      "Transport": "http",
      "Url": "https://systra.tools/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add tools-systra-systra-tools -t streamable-http -u 'https://systra.tools/api/mcp'
// mcp.json
{
  "mcpServers": {
    "tools-systra-systra-tools": {
      "type": "http",
      "url": "https://systra.tools/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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 +1

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 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.

  • 14 Sept 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.

  • 12 Sept 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.

  • 10 Sept 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.

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 25 Sept 2026 · Probed https://systra.tools/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=systra.tools CN=WE1,O=Google Trust Services,C=US 22 Aug 2026 20 Nov 2026 ECDSA 256 ECDSA-SHA256 11d4ef2b4dba07710ec3b9f3f8b32da1
SANs: systra.tools
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 systra.tools. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
tools. present 13831 8 Verified
systra.tools. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'self'; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://systra.tools/api/mcp Verified 200
http (plaintext) http://systra.tools/api/mcp HTTPS enforced 301 https://systra.tools/api/mcp
MCP tools · 13 exposed · ~778 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_component ~52

Gibt den vollständigen, kopierfertigen React/TSX-Quellcode einer Komponente anhand ihres Namens zurück.

NameTypeReqDescription
namestringyesKomponentenname, z. B. 'OrbitGalleryHero'.

No output schema declared.

No examples provided.

get_component_styled ~78

Gibt eine Komponente zusammen mit den Design-Tokens eines Marken-Stils und einer präzisen Anpassungs-Anleitung zurück. Damit landet die Komponente direkt im Look der eigenen Marke.

NameTypeReqDescription
namestringyesKomponentenname, z. B. 'GradientHeroSection'.
stylestringyesStyle-Slug aus list_styles.

No output schema declared.

No examples provided.

get_post ~82

Gibt eine Post-Vorlage als komplette Arbeitsanweisung zurück: die HTML-Datei, das Export-Skript und die Regeln, was geändert werden darf. Damit lässt sich der Post direkt umbauen und rendern.

NameTypeReqDescription
langstring–Sprache der Anweisung. Ohne Angabe Deutsch.
slugstringyesSlug der Vorlage, siehe list_posts.

No output schema declared.

No examples provided.

get_recipe ~80

Gibt ein Seiten-Rezept zurück: die Section-Abfolge mit Zweck je Abschnitt und dem vollständigen Quellcode aller Sections. Optional im Look eines Marken-Stils.

NameTypeReqDescription
namestringyesRezept-Slug aus list_recipes, z. B. 'saas-landing'.
stylestring–Optionaler Style-Slug aus list_styles.

No output schema declared.

No examples provided.

get_style ~52

Gibt alle Design-Tokens eines extrahierten Marken-Stils zurück: Farben, Typografie, CSS-Variablen und die generierte DESIGN.md.

NameTypeReqDescription
slugstringyesStyle-Slug aus list_styles.

No output schema declared.

No examples provided.

list_categories ~25

Listet alle Kategorien von Systra Tools mit der Anzahl der enthaltenen Komponenten.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_components ~52

Listet Komponenten der Library. Optional nach Kategorie-Slug gefiltert (z. B. 'heros', 'forms', 'cta').

NameTypeReqDescription
categorystring–Kategorie-Slug zum Filtern (optional).

No output schema declared.

No examples provided.

list_images ~95

Listet die Bilder der Medienbibliothek von Systra Tools mit fertigen, dauerhaft gültigen URLs zum direkten Einsetzen. Optional nach Album und Format gefiltert.

NameTypeReqDescription
albumstring–Album-Schlüssel zum Filtern (optional), z. B. 'natur', 'business', 'abstrakt'. Ohne Angabe kommen alle Alben.
formatstring–Bildformat zum Filtern (optional).

No output schema declared.

No examples provided.

list_posts ~86

Listet die Instagram-Post-Vorlagen von Systra Tools (1080 x 1350). Jede Vorlage ist eine einzelne HTML-Datei, die sich umbauen und als Bild oder Video exportieren lässt.

NameTypeReqDescription
familystring–Familie zum Filtern (optional): 'klar' sind ruhige Informationsposts, 'editorial' lebt von Motiv und Serifenschrift.

No output schema declared.

No examples provided.

list_recipes ~42

Listet kuratierte Seiten-Rezepte: sinnvolle Abfolgen von Sections für komplette Landingpages (z. B. SaaS, Coaching, Hotel).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_styles ~39

Listet die mit dem Style Extractor extrahierten Marken-Stile (Farben und Schriften echter Websites), die sich auf Komponenten anwenden lassen.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_components ~37

Sucht Komponenten anhand eines Stichworts im Namen oder in der Kategorie und gibt Treffer zurück.

NameTypeReqDescription
querystringyesSuchbegriff.

No output schema declared.

No examples provided.

search_images ~58

Sucht Bilder der Medienbibliothek anhand eines Stichworts in Titel, Dateiname oder Album und gibt fertige URLs zurück.

NameTypeReqDescription
querystringyesSuchbegriff, z. B. 'gradient', 'laptop', 'wald'.

No output schema declared.

No examples provided.

Common questions

What is the Systra Tools MCP server?

Systra Tools is an MCP server listed in the public MCP registry as tools.systra/systra-tools. Search and pull 500+ production-ready React + Tailwind sections and elements. This page covers its hosted endpoint (https://systra.tools/api/mcp).

Is the Systra Tools MCP server safe to use?

Systra Tools scores 76 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 Systra Tools MCP server expose?

Systra Tools exposes 13 tools: list_categories, list_components, search_components, get_component, list_styles, and 8 more. Their descriptions and schemas cost roughly 778 tokens of context every time the server is loaded.

Does the Systra Tools MCP server require authentication?

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

Is the Systra Tools MCP server still maintained?

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