mcp-registry/tools.systra/systra-tools · v1.0.0
As of 2026-10-27 07:02 UTC, the Systra Tools MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Search and pull 500+ production-ready React + Tailwind sections and elements
Point your MCP client at this streamable-http endpoint: https://systra.tools/api/mcp
13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~2,646 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 12 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Ftools.systra%2Fsystra-tools/fixes
{
"name": "get_component",
"description": "Returns the complete, copy-ready React/TSX source of a component by its name.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Component name, e.g. 'OrbitGalleryHero'."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_component_styled",
"description": "Returns a component together with the design tokens of a brand style and precise instructions for adapting it, so the component lands directly in your own brand look.",
"inputSchema": {
"type": "object",
"required": [
"name",
"style"
],
"properties": {
"name": {
"type": "string",
"description": "Component name, e.g. 'GradientHeroSection'."
},
"style": {
"type": "string",
"description": "Style slug from list_styles."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_post",
"description": "Returns a post template as a complete set of working instructions: the HTML file, the export script and the rules on what may be changed. With it the post can be rebuilt and rendered directly.",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"lang": {
"enum": [
"de",
"en"
],
"type": "string",
"description": "Language of the instructions. English without one."
},
"slug": {
"type": "string",
"description": "Slug of the template, see list_posts."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/tools.systra/systra-tools"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/tools.systra/systra-tools"}) over MCP.
list_images ~191 tokensget_post ~143 tokenssearch_images ~139 tokensget_component_styled ~132 tokensget_recipe ~130 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Ftools.systra%2Fsystra-tools?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Ftools.systra%2Fsystra-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ftools.systra%2Fsystra-tools.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ftools.systra%2Fsystra-tools.svg :target: https://glimind.com/server/mcp-registry%2Ftools.systra%2Fsystra-tools?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f8ef53e737056246…, first seen 2026-10-18, included at leaf 22631 of 77,980. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable media servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 07:02 UTC, the Systra Tools MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 7 minutes.
Systra Tools MCP server advertises 13 tools, including get_component, get_component_styled, get_post, get_recipe, get_style.
Point your MCP client at this streamable-http endpoint: https://systra.tools/api/mcp
Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.