mcp-registry/com.stagenix/site · v1.0.0
As of 2026-10-17 16:36 UTC, the Stagenix Site MCP server is up with a Glimind reliability score of 59/100 (grade D). Over the last 30 days it answered 94% of Glimind's liveness checks. It had 325 outages in 90 days, with a median recovery of 7 minutes.
Stagenix: the site's own MCP server — dataset; every answer cites the site.
Claude Code
claude mcp add --transport http stagenix-site-mcp-server https://stagenix.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"stagenix-site-mcp-server": {
"type": "http",
"url": "https://stagenix.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Reachable 94.0% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
7 of 7 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.
8 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~2,491 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.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.stagenix%2Fsite/fixes
{
"name": "dataset_compare",
"description": "The rows of the Stagenix dataset whose column is any of the given values, in the order given — for \"X vs Y\" questions.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"column",
"values"
],
"properties": {
"column": {
"type": "string",
"minLength": 1
},
"values": {
"type": "array",
"items": {
"type": "string",
"minLength": 1
},
"maxItems": 10,
"minItems": 2
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Compare rows side by side"
}{
"name": "dataset_search",
"description": "Rows of the Stagenix dataset whose cells contain the query (case-insensitive), up to 50.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1
},
"query": {
"type": "string",
"minLength": 1,
"description": "text to look for in any cell"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Search the dataset"
}{
"name": "dataset_stats",
"description": "count, min, max, mean, median and sum of a numeric column of the Stagenix dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"column"
],
"properties": {
"column": {
"type": "string",
"minLength": 1
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Summary statistics for a numeric column"
}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/com.stagenix/site"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.stagenix/site"}) over MCP.
dataset_top ~135 tokensdataset_compare ~127 tokensdataset_search ~116 tokensdataset_stats ~112 tokensdataset_row ~103 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%2Fcom.stagenix%2Fsite?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.stagenix%2Fsite?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.stagenix%2Fsite.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.stagenix%2Fsite.svg :target: https://glimind.com/server/mcp-registry%2Fcom.stagenix%2Fsite?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:171a5ffa1473dba9…, first seen 2026-10-17, included at leaf 6718 of 17,907. Version history · verify what your client received.
Compare: most reliable data 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-17 16:36 UTC, the Stagenix Site MCP server is up with a Glimind reliability score of 59/100 (grade D). Over the last 30 days it answered 94% of Glimind's liveness checks. It had 325 outages in 90 days, with a median recovery of 7 minutes.
Stagenix Site MCP server advertises 7 tools, including dataset_columns, dataset_compare, dataset_provenance, dataset_row, dataset_search.
Point your MCP client at this streamable-http endpoint: https://stagenix.com/mcp
Glimind scanned all 7 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.