Sunaiva Core MCP server

• Registry nameio.sunaivacore/gateverified in the MCP registry

The registry name sits under sunaivacore.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-26
• Tools16
• Server calls itselfsunaiva-gate
• Server version2.5.3+2026-07-25
• Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 112 ms.

• Its tools do block coding agent actions that break rules before they run; enforce custom rules on agent behaviour, but not keep signed audit logs of agent decisions.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• What an agent can do with it2 of 3 use cases
• Use17 npm downloads a week
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer102 ms
• Space in an agent's context≈ 1,555 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 82 of 100
• Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 1 of 16
• Not saying whether it only reads or can destroy: 16 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• validate_action

  Check if a proposed action passes all active validation rules. Returns allowed/blocked with rule violations.

• log_bypass

  Record an intentional rule bypass with justification. Cannot bypass constitutional rules.

• get_rules

  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.

• update_rules

  [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.

• get_audit_log

  View recent gate decisions — blocks, warnings, passes, and bypasses.

• ship_confidence_check

  [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.

• audit_verify

  [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.

• set_rule_mode

  Set enforcement mode (shadow/advisory/enforce) for a specific rule. Requires API key (Pro+).

• get_rule_modes

  List all enforcement-mode overrides configured for the authenticated customer. Requires an account (Dev+).

• reset_rule_mode

  Remove a mode override for a rule, reverting it to its default enforcement mode. Requires API key (Pro+).

• add_custom_rule

  Create a custom detection rule in the backend. Requires API key (Pro+).

• update_custom_rule

  Update an existing custom rule. Requires API key (Pro+).

• delete_custom_rule

  Delete a custom rule. Requires API key (Pro+).

• list_custom_rules

  List all custom rules for the authenticated customer. Requires API key (Pro+).

• list_presets

  List available rule preset bundles. Requires API key (Dev+).

• apply_preset

  Apply a preset bundle, activating all its included rules. Requires API key (Pro+).