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

Search and pull production-ready React + Tailwind sections and elements from a growing library

Available components

0 this week 89 Trust /100

Last scanned (15 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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 Security80
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2127 tokens (~141/item across 15 items; 13 tools + 2 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 15 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 15 Nov 26 0
    • Tool “list_recipes” rewrote its description, which is the text the model reads security
  • 12 Nov 26 +1
    • Tool “list_images” rewrote its description, which is the text the model reads security
    • Tool “search_images” rewrote its description, which is the text the model reads security
    • Schema quality: 1754 → 2127 ▼ functional
    • The server now declares the “prompts” capability functional
    • The server now declares the “resources” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “build_landing_page” functional
    • New prompt “find_section” functional
    • New prompt “restyle_component” functional
    • New resource “categories” functional
    • New resource “recipes” functional
    • “list_images” added an optional parameter “color” cosmetic
    • “list_images” added an optional parameter “people” cosmetic
    • “list_images” added an optional parameter “text_space” cosmetic
    • “list_images” added an optional parameter “tone” cosmetic
    • “list_images” added an optional parameter “use” cosmetic
    • “search_images” added an optional parameter “color” cosmetic
    • “search_images” added an optional parameter “people” cosmetic
    • “search_images” added an optional parameter “text_space” cosmetic
    • “search_images” added an optional parameter “tone” cosmetic
    • “search_images” added an optional parameter “use” cosmetic
    • “search_images” reworded the description of “query” cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Tool “get_component” rewrote its description, which is the text the model reads security
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 29 Oct 26 +7
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_component” rewrote its description, which is the text the model reads security
    • Tool “get_recipe” rewrote its description, which is the text the model reads security
    • Tool “list_components” rewrote its description, which is the text the model reads security
    • Tool “get_component” changed its title: Get component source cosmetic
    • Tool “get_component_styled” changed its title: Get component in a brand style cosmetic
    • Tool “get_post” changed its title: Get post template cosmetic
    • Tool “get_recipe” changed its title: Get page recipe cosmetic
    • Tool “get_style” changed its title: Get brand style cosmetic
    • Tool “list_categories” changed its title: List categories cosmetic
    • Tool “list_components” changed its title: List components cosmetic
    • Tool “list_images” changed its title: List images cosmetic
    • Tool “list_posts” changed its title: List post templates cosmetic
    • Tool “list_recipes” changed its title: List page recipes cosmetic
    • Tool “list_styles” changed its title: List brand styles cosmetic
    • Tool “search_components” changed its title: Search components cosmetic
    • Tool “search_images” changed its title: Search images cosmetic
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 21 Nov 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 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 64256bd2d65bb04a0eca84258fb65370
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. DS published 1547 8 Verified
systra.tools. No DS 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 · ~2,009 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 ~171

Returns the complete, copy-ready React/TSX source of one component as designed, plus notes on its images and any extra files it needs. Components use Tailwind CSS classes and import react, framer-motion and lucide-react; a few also need gsap or three, which the response names with the install command. Use it once you know the exact name; use get_component_styled instead when the component should take on an extracted brand style. Without a premium key, source comes back for the free components, the first six of every category, which list_components and search_components mark as "free"; other names return a notice on how to get a key.

NameTypeReqDescription
namestringyesComponent name as listed by list_components or search_components, e.g. 'OrbitGalleryHero'. Matching ignores case.

No output schema declared.

No examples provided.

get_component_styled ~124

Returns one component's source together with the tokens of a brand style, step-by-step instructions for mapping the component's colours, fonts and radii onto that style, and the colour values the component uses today. Use it instead of get_component when the result should match a specific brand. The server does not rewrite the code; you apply the mapping. Same premium rule as get_component.

NameTypeReqDescription
namestringyesComponent name as listed by list_components, e.g. 'GradientHeroSection'.
stylestringyesStyle slug exactly as listed by list_styles.

No output schema declared.

No examples provided.

get_post ~91

Returns one post template as working instructions: the full HTML file, an export script to render it locally as PNG or video, and the rules on what may be changed. The server renders nothing; you edit and export the file. Use it after list_posts.

NameTypeReqDescription
langstring–Language of the instructions (optional, English by default).
slugstringyesTemplate slug as listed by list_posts.

No output schema declared.

No examples provided.

get_recipe ~128

Returns one page recipe: the ordered sections with the purpose of each, a composition file where available, and the full source of every section. Pass style to add brand tokens and adaptation instructions. Without a premium key, sections that are not free are named but their source is held back. The answer is long because it contains several complete components.

NameTypeReqDescription
namestringyesRecipe slug as listed by list_recipes, e.g. 'saas-produkt' or 'hotel-stay'.
stylestring–Style slug from list_styles (optional), to adapt the page to a brand.

No output schema declared.

No examples provided.

get_style ~91

Returns every design token of one extracted brand style: colours, font families and sizes, spacing, radii, CSS variables and the generated DESIGN.md (up to 4000 characters). Use it to theme your own code or set up a design system; use get_component_styled when you want one specific component already paired with the style.

NameTypeReqDescription
slugstringyesStyle slug exactly as listed by list_styles.

No output schema declared.

No examples provided.

list_categories ~71

Lists every component category of the Systra Tools library with its slug, its title and how many components it holds. Start here when the user names a kind of page part (hero, pricing, footer) instead of a component, then pass the slug to list_components. No parameters, works without a key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_components ~125

Lists component names, optionally limited to one category, one line each with the name and the category slug. Use it to browse a category before choosing; use search_components instead when you already have a keyword. Returns names only, no source: fetch the code with get_component. Works without a key; without one, the components whose source is free are marked "free".

NameTypeReqDescription
categorystring–Category slug from list_categories, e.g. 'heroes', 'cta', 'pricing', 'forms', 'footer'. Omit it to list every component (more than 600).

No output schema declared.

No examples provided.

list_images ~343

Lists images and a few videos from the Systra Tools media library (all AI-generated), each with a permanent URL to use directly as src, plus title, album, format and, where available, a one-sentence description, dominant colours, brightness, where there is room for text and what the image suits. Filter by album, format, tone, text_space, use, color and people, 100 per page. Use it to browse; use search_images to find a motif by words. Without a premium key only the free images are returned, three per album.

NameTypeReqDescription
albumstring–Album key (optional, German): verlaeufe, abstrakt, surreal, objekte, freisteller, natur, interior, essen, portraet, beauty, hochzeit, menschen, arbeitsplatz, business, industrie, gesundheit, sport, a…
colorstring–A dominant colour by name, e.g. 'blue', 'sage', 'orange' (optional).
formatstring–Image format to filter by (optional).
pageinteger–Page of the result, 100 images per page (optional, default 1).
peoplestring–How many people are visible (optional).
text_spacestring–Where a calm area leaves room for a headline (optional). E.g. 'left' for a hero with the text on the left.
tonestring–Overall brightness of the image (optional).
usestring–What the image is good for on a website (optional).

No output schema declared.

No examples provided.

list_posts ~149

Lists the Instagram post templates (1080 x 1350) with slug, name, family and whether they need your own imagery. Each template is a single HTML file that can be rebuilt and exported as an image or a video. Pass query to search by name or purpose, for example 'quote' or 'statistic'. Use it to pick a slug for get_post.

NameTypeReqDescription
familystring–Family to filter by (optional): 'klar' are calm informational posts, 'editorial' lives on the image and a serif face.
querystring–Search term (optional). Every word must appear in the slug, name, purpose or family. Can be combined with family.

No output schema declared.

No examples provided.

list_recipes ~116

Lists curated page recipes: proven section sequences for complete landing pages (for example an agency, coaching or a hotel), each with its number of sections and a short purpose. Pass query to search by industry, purpose or section, for example 'hotel' or 'pricing'. Use it when the user wants a whole page rather than one section, then call get_recipe.

NameTypeReqDescription
querystring–Search term (optional). Every word must appear in the slug, title, description or section names. Without it, every recipe is listed.

No output schema declared.

No examples provided.

list_styles ~123

Lists the brand styles extracted from real websites with the Systra style extractor: slug, site name, primary and accent colour and heading font. Pass query to search by site name, domain, colour or font, for example 'bakery' or 'Inter'. Use it to find a slug for get_style, get_component_styled or get_recipe. Works without a key.

NameTypeReqDescription
querystring–Search term (optional). Every word must appear in the slug, site name, domain, colours or fonts. Without it, the 30 newest styles are listed.

No output schema declared.

No examples provided.

search_components ~132

Finds components whose name or category contains the search term (one term, case-insensitive substring match) and returns their names with the category slug. Use it when you know roughly what you need, such as 'pricing', 'marquee', 'testimonial' or 'countdown'; use list_components to see a whole category. Names are English PascalCase, so short English words match best. Follow up with get_component for the source.

NameTypeReqDescription
querystringyesOne keyword or name fragment, e.g. 'hero', 'gallery', 'bento'. Matched against component names and category slugs and titles.

No output schema declared.

No examples provided.

search_images ~345

Finds images in the media library (all AI-generated) by what they show: the query is matched against a description of each image written by a vision model, its tags, title, colours and album, and the best matches come first. Returns permanent URLs, 100 per page, each with its description, dominant colours, brightness and where there is room for text, so you can pick the image that fits the layout. Use it for a motif ('red dress', 'laptop on a desk', 'misty forest') and narrow it with tone, text_space, use, color or people, e.g. query 'architecture' with text_space 'left' and tone 'dark' for a hero with white text on the left. Without a premium key only the free images are included.

NameTypeReqDescription
colorstring–A dominant colour by name, e.g. 'blue', 'sage', 'orange' (optional).
pageinteger–Page of the result, 100 images per page (optional, default 1).
peoplestring–How many people are visible (optional).
querystringyesOne or more English words describing the motif. Images matching every word rank first; if none do, close matches follow. E.g. 'gradient', 'laptop desk', 'woman red dress'.
text_spacestring–Where a calm area leaves room for a headline (optional). E.g. 'left' for a hero with the text on the left.
tonestring–Overall brightness of the image (optional).
usestring–What the image is good for on a website (optional).

No output schema declared.

No examples provided.

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'
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 production-ready React + Tailwind sections and elements from a growing library. This page covers its hosted endpoint (https://systra.tools/api/mcp).

Is the Systra Tools MCP server safe to use?

Systra Tools scores 89 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 2,009 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Systra Tools MCP server?

VerifyMCP ran 13 checks on Systra Tools, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.