mcp-registry/io.sunaivacore/gate · v2.5.3+2026-07-25
As of 2026-10-26 00:57 UTC, the Sunaivacore Gate MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution.
Claude Code
claude mcp add --transport http sunaivacore-gate-mcp-server https://mcp.sunaivacore.io
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"sunaivacore-gate-mcp-server": {
"type": "http",
"url": "https://mcp.sunaivacore.io"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
16 of 16 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 →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
4 parameter(s) across 1 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. How to fix →
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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.sunaivacore%2Fgate/fixes
{
"name": "add_custom_rule",
"description": "Create a custom detection rule in the backend. Requires API key (Pro+).",
"inputSchema": {
"type": "object",
"required": [
"name",
"description",
"detection_pattern",
"severity"
],
"properties": {
"name": {
"type": "string",
"description": "Rule name"
},
"tier": {
"type": "string",
"description": "Optional tier restriction"
},
"severity": {
"enum": [
"block",
"warn"
],
"type": "string",
"description": "Severity on match"
},
"description": {
"type": "string",
"description": "Rule description (required — the backend 400s on a missing/empty description)"
},
"detection_pattern": {
"type": "string",
"description": "Compiled regex detection pattern (required — the backend 400s on a missing/empty detection_pattern). There is no 'pattern' field: 'detection_pattern' is the only field name the evaluator reads; the backend explicitly rejects 'pattern'."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_custom_rule",
"description": "Delete a custom rule. Requires API key (Pro+).",
"inputSchema": {
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "Rule ID to delete"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "get_audit_log",
"description": "View recent gate decisions — blocks, warnings, passes, and bypasses.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "number",
"description": "Max entries to return (default 50)"
},
"rule_id": {
"type": "string",
"description": "Accepted for forward-compatibility but NOT applied server-side — the backend only honors limit/cursor. Filter the returned entries client-side."
}
}
},
"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/io.sunaivacore/gate"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.sunaivacore/gate"}) over MCP.
add_custom_rule ~236 tokensship_confidence_check ~170 tokensupdate_custom_rule ~153 tokensupdate_rules ~137 tokensset_rule_mode ~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%2Fio.sunaivacore%2Fgate?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.sunaivacore%2Fgate?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.sunaivacore%2Fgate.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.sunaivacore%2Fgate.svg :target: https://glimind.com/server/mcp-registry%2Fio.sunaivacore%2Fgate?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:a33330499bfeb5ec…, first seen 2026-10-17, included at leaf 2910 of 69,763. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other 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-26 00:57 UTC, the Sunaivacore Gate MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Sunaivacore Gate MCP server advertises 16 tools, including add_custom_rule, apply_preset, audit_verify, delete_custom_rule, get_audit_log.
Point your MCP client at this streamable-http endpoint: https://mcp.sunaivacore.io
Glimind scanned all 16 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.