Is the Sunaivacore Gate MCP server down?

mcp-registry/io.sunaivacore/gate · v2.5.3+2026-07-25

healthy
Last checked 2026-10-26 00:57 UTC · handshake 388ms

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.

uptime (30d checks)
100%
checks observed
4,785
outages (90d)
0
tools
16

MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution.

Install Sunaivacore Gate MCP server

Add to Cursor Add to VS Code

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.

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 16 tool(s); ~1,726 tokens of tool definitions.
Scores higher than 14% of 15,723 MCP servers Glimind has audited.
Its tool list costs an agent ~1,726 tokens per session — lighter than 60% of servers.
76 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions86
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

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 →

Tools: add_custom_rule, apply_preset, audit_verify, delete_custom_rule, get_audit_log and 11 more

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 →

Tools: delete_custom_rule, set_rule_mode, update_custom_rule, update_rules

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 →

Tools: update_custom_rule

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 →

Auto-fix: 13 corrected tool definitions

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

add_custom_rule 1 change
{
  "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
  }
}
delete_custom_rule 1 change
{
  "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
  }
}
get_audit_log 1 change
{
  "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 alerted

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.

Passed

Largest tool definitions

Static 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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.sunaivacore%2Fgate.svg)](https://glimind.com/server/mcp-registry%2Fio.sunaivacore%2Fgate?ref=badge)
HTML
<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>
reStructuredText
.. 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

Tool-definition log

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.

Tools (16)

Compare: most reliable security servers · most reliable other servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Sunaivacore Gate MCP server down right now?

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.

How many tools does Sunaivacore Gate MCP server provide?

Sunaivacore Gate MCP server advertises 16 tools, including add_custom_rule, apply_preset, audit_verify, delete_custom_rule, get_audit_log.

How do I install Sunaivacore Gate MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.sunaivacore.io

Is the Sunaivacore Gate MCP server safe to connect to an AI agent?

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.

Operator of Sunaivacore Gate MCP server?

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.

Feedback
Help us improve