Sunaiva Gate — Agent Rule Enforcement
REMOTE · MCP.SUNAIVACORE.IO · 2 COMPONENTS · SCANNED SEP 22
MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution.
Available components
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1003 tokens (~62/item across 16 items; 16 tools + 0 resources), lean.Pass
- 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "reset_rule_mode" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 16 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
How do I install the Sunaiva Gate — Agent Rule Enforcement MCP server?
Sunaiva Gate — Agent Rule Enforcement is a hosted endpoint at https://mcp.sunaivacore.io/, 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 · mcp.sunaivacore.io
claude mcp add --transport http io-sunaivacore-gate 'https://mcp.sunaivacore.io/'
{
"mcpServers": {
"io-sunaivacore-gate": {
"url": "https://mcp.sunaivacore.io/"
}
}
} {
"servers": {
"io-sunaivacore-gate": {
"type": "http",
"url": "https://mcp.sunaivacore.io/"
}
}
} [mcp_servers.io-sunaivacore-gate] url = "https://mcp.sunaivacore.io/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-sunaivacore-gate": {
"type": "remote",
"url": "https://mcp.sunaivacore.io/",
"enabled": true
}
}
} openclaw mcp add io-sunaivacore-gate --url 'https://mcp.sunaivacore.io/' --transport streamable-http
mcp_servers:
io-sunaivacore-gate:
url: "https://mcp.sunaivacore.io/" {
"McpServers": {
"io-sunaivacore-gate": {
"Transport": "http",
"Url": "https://mcp.sunaivacore.io/"
}
}
} assistant mcp add io-sunaivacore-gate -t streamable-http -u 'https://mcp.sunaivacore.io/'
{
"mcpServers": {
"io-sunaivacore-gate": {
"type": "http",
"url": "https://mcp.sunaivacore.io/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 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
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 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
- 26 Jul 26 0
First indexed and scored.
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 22 Sept 2026 · Probed https://mcp.sunaivacore.io
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sunaivacore.io | CN=WE1,O=Google Trust Services,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 4ab7af68081b731413cb4b9012aa2b3c |
| SANs: sunaivacore.io, *.sunaivacore.io | ||||||
| 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 mcp.sunaivacore.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| sunaivacore.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sunaivacore.io | Verified | 200 | |
| http (plaintext) | http://mcp.sunaivacore.io | Served over HTTP | 200 |
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 →
add_custom_rule ~134
Create a custom detection rule in the backend. Requires API key (Pro+).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Rule description (required — the backend 400s on a missing/empty description) |
| detection_pattern | string | yes | 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 b… |
| name | string | yes | Rule name |
| severity | string | yes | Severity on match |
| tier | string | – | Optional tier restriction |
No output schema declared.
No examples provided.
apply_preset ~41
Apply a preset bundle, activating all its included rules. Requires API key (Pro+).
| Name | Type | Req | Description |
|---|---|---|---|
| preset_id | string | yes | ID of the preset to apply |
No output schema declared.
No examples provided.
audit_verify ~44
[Planned — not yet implemented on the remote endpoint, returns NOT_IMPLEMENTED] Forward-linked hash-chain / ed25519 audit-log verification is not yet built in this backend.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_custom_rule ~32
Delete a custom rule. Requires API key (Pro+).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Rule ID to delete |
No output schema declared.
No examples provided.
get_audit_log ~74
View recent gate decisions — blocks, warnings, passes, and bypasses.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max entries to return (default 50) |
| rule_id | string | – | Accepted for forward-compatibility but NOT applied server-side — the backend only honors limit/cursor. Filter the returned entries client-side. |
No output schema declared.
No examples provided.
get_rule_modes ~27
List all enforcement-mode overrides configured for the authenticated customer. Requires an account (Dev+).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rules ~75
List active validation rules — the customer's TRUE enforced set (constitutional + recommended-default metadata on dev tier, all 69 premium rules on pro+). `category`/`preset` filter args are accepted but not applied server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| preset | string | – | Filter by preset name |
No output schema declared.
No examples provided.
list_custom_rules ~25
List all custom rules for the authenticated customer. Requires API key (Pro+).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_presets ~22
List available rule preset bundles. Requires API key (Dev+).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_bypass ~48
Record an intentional rule bypass with justification. Cannot bypass constitutional rules.
| Name | Type | Req | Description |
|---|---|---|---|
| reason | string | yes | Justification for the bypass |
| rule_id | string | yes | ID of the rule to bypass |
No output schema declared.
No examples provided.
reset_rule_mode ~46
Remove a mode override for a rule, reverting it to its default enforcement mode. Requires API key (Pro+).
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | Rule ID whose override to remove |
No output schema declared.
No examples provided.
set_rule_mode ~70
Set enforcement mode (shadow/advisory/enforce) for a specific rule. Requires API key (Pro+).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Optional: scope override to a specific agent ID |
| mode | string | yes | Enforcement mode |
| rule_id | string | yes | Rule ID to configure |
No output schema declared.
No examples provided.
ship_confidence_check ~111
[Planned — not yet implemented on the remote endpoint, returns NOT_IMPLEMENTED] Ship Confidence Gate (Rule 42) dual-tier authorization is not yet built in this backend.
| Name | Type | Req | Description |
|---|---|---|---|
| artifact_id | string | yes | The artifact being shipped (e.g. '@sunaiva/gate@1.1.0') |
| command_preview | string | – | First 300 chars of the command that triggered the check (optional) |
| label | string | – | Human-readable label of the publish action (optional) |
No output schema declared.
No examples provided.
update_custom_rule ~97
Update an existing custom rule. Requires API key (Pro+).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| detection_pattern | string | – | There is no 'pattern' field — 'detection_pattern' is the only field name the evaluator reads; the backend explicitly rejects 'pattern'. |
| id | string | yes | Rule ID to update |
| name | string | – | – |
| severity | string | – | – |
| tier | string | – | – |
No output schema declared.
No examples provided.
update_rules ~89
[Planned — not yet implemented on the remote endpoint, returns NOT_IMPLEMENTED] Enable/disable is not backed by any route in this API; use set_rule_mode (shadow/advisory/enforce) instead, or the local `npx @sunaiva/gate` package.
| Name | Type | Req | Description |
|---|---|---|---|
| disable | array | – | Rule IDs to disable |
| enable | array | – | Rule IDs to enable |
No output schema declared.
No examples provided.
validate_action ~68
Check if a proposed action passes all active validation rules. Returns allowed/blocked with rule violations.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | The action to validate |
| context | string | – | Optional additional context, appended to `action` before rule matching — it can change which rules match and therefore the verdict. |
No output schema declared.
No examples provided.
What is the Sunaiva Gate — Agent Rule Enforcement MCP server?
Sunaiva Gate — Agent Rule Enforcement is an MCP server listed in the public MCP registry as io.sunaivacore/gate. MCP enforcement layer that intercepts AI agent actions and blocks rule violations before execution. This page covers its hosted endpoint (https://mcp.sunaivacore.io).
Is the Sunaiva Gate — Agent Rule Enforcement MCP server safe to use?
Sunaiva Gate — Agent Rule Enforcement scores 82 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 Sunaiva Gate — Agent Rule Enforcement MCP server expose?
Sunaiva Gate — Agent Rule Enforcement exposes 16 tools: validate_action, log_bypass, get_rules, update_rules, get_audit_log, and 11 more. Their descriptions and schemas cost roughly 1,003 tokens of context every time the server is loaded.
Does the Sunaiva Gate — Agent Rule Enforcement MCP server require authentication?
Yes. Sunaiva Gate — Agent Rule Enforcement asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Sunaiva Gate — Agent Rule Enforcement MCP server still maintained?
Sunaiva Gate — Agent Rule Enforcement is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.