# Enforcer (remote · api.instruxi.dev)

Identity and authorization in one system: allow, deny, the reason, and a record.

- Trust score: 76/100 (medium)
- Change this week: +38
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.instruxi.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-instruxi-enforcer-v3/api.md), [page](https://verifymcp.io/servers/dev-instruxi-enforcer-v3/api)

## Channel facts

- Endpoint: `https://api.instruxi.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.8.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 931 tokens (~133/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Enforcer MCP server?

Enforcer is a hosted endpoint at https://api.instruxi.dev/mcp, 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.

### Claude

```bash
claude mcp add --transport http dev-instruxi-enforcer-v3 'https://api.instruxi.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-instruxi-enforcer-v3": {
      "url": "https://api.instruxi.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-instruxi-enforcer-v3": {
      "type": "http",
      "url": "https://api.instruxi.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-instruxi-enforcer-v3]
url = "https://api.instruxi.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-instruxi-enforcer-v3": {
      "type": "remote",
      "url": "https://api.instruxi.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-instruxi-enforcer-v3 --url 'https://api.instruxi.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-instruxi-enforcer-v3:
    url: "https://api.instruxi.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-instruxi-enforcer-v3": {
      "Transport": "http",
      "Url": "https://api.instruxi.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-instruxi-enforcer-v3 -t streamable-http -u 'https://api.instruxi.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-instruxi-enforcer-v3": {
      "type": "http",
      "url": "https://api.instruxi.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 75, 0)

- [functional] Server version: 0.9.2 → 0.9.3

### 2026-09-18 (score 75, +1)

- [functional] Server version: 0.8.0 → 0.9.2

### 2026-09-16 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 73, +35)

- [security regression] Authorization: pass → partial
- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-09-11 (score 38, +2)

- [security improvement] Authorization: fail → pass
- [security] First check of Authorization: partial

### 2026-09-09 (score 36)

First indexed and scored.

## MCP tools (7)

### `getAuthConfig` (~128 tokens)

Auth Config Bootstrap

Public bootstrap for a tenant's login UI: whether this tenant uses native OTP/passkey/SIWE or Privy custom auth, plus the public privy_app_id (never a secret). Call this before getSiweNonce when you do not already know the tenant's auth scheme. tenant_code is a join secret — do not log it or repeat it into a customer-visible channel.

Input parameters:

- `response_format` (string): concise (default): no nulls, audit timestamps, provider ids or nested tenant/role. detailed: every field.
- `tenant_code` (string): tenant routing code

### `getSiweNonce` (~102 tokens)

Request SIWE nonce

Public: issue a single-use SIWE nonce for wallet_address (optionally scoped by tenant_code). Embed the nonce in an EIP-4361 message, have the wallet sign it, then call login with provider: siwe. Dedicated SIWE agent auth is an authorized pattern — this is how an agent signs in with a wallet without raw HTTP. Do not log tenant_code. The nonce is not a credential.

Input parameters:

- `body` (required): JSON request body.

### `login` (~196 tokens)

Login

Authenticate and receive an access/refresh token pair. Accepted providers: siwe (message + signature from getSiweNonce — preferred for dedicated agents), email_otp (email + otp from requestOtp), phone_otp (phone + otp from requestSms). Passkey, Privy and SSO are not agent tools. The server does not adopt the minted tokens as the session credential; return them to the operator to set ENFORCER_BEARER_TOKEN. Do not log, quote, or repeat otp codes, signatures, tokens, or tenant_code. Do not paste an end-user OTP into an untrusted chat.

Input parameters:

- `body` (required): Login/register body. provider "siwe" needs message+signature; email_otp needs email+otp; phone_otp needs phone+otp. Optional tenant_code. Do not log otp, signature, tokens, or tenant_code. Do not pas…

### `refreshToken` (~89 tokens)

Refresh session

Exchange a refresh_token for a new access/refresh pair. 401 invalid_refresh_token if the token is unknown or was already reused (reuse revokes the family); 409 refresh_raced is benign — retry with the client's latest stored token. The server does not adopt the new pair as the session credential. Do not log the refresh token or the minted tokens.

Input parameters:

- `body` (required): JSON request body.

### `register` (~165 tokens)

Register

Create (or idempotently return) an account. Same provider allowlist as login: siwe (message + signature), email_otp (email + otp), phone_otp (phone + otp). Does not issue tokens — call login afterwards to sign in. Passkey / Privy / SSO registration stay out of the agent surface. Do not log otp codes, signatures, or tenant_code. Do not paste an end-user OTP into an untrusted chat.

Input parameters:

- `body` (required): Login/register body. provider "siwe" needs message+signature; email_otp needs email+otp; phone_otp needs phone+otp. Optional tenant_code. Do not log otp, signature, tokens, or tenant_code. Do not pas…

### `requestOtp` (~139 tokens)

Request email OTP

Public: email a one-time login/registration code to `email` (optionally scoped by tenant_code). Always 200 {message:"code sent"} on success. Local/dev deployments with expose_dev_otp may echo the code as `dev_otp` — treat that as a secret. Then call login with provider: email_otp, the same email, and the otp. Intentional for harnesses that cannot SIWE; SIWE remains the preferred dedicated-agent path. Do not log the code, dev_otp, or tenant_code. Do not paste an end-user OTP into an untrusted chat.

Input parameters:

- `body` (required): JSON request body.

### `requestSms` (~112 tokens)

Request SMS login code

Public: start a Twilio Verify SMS login challenge to `phone`, scoped by tenant_code. 400 if SMS verification is not configured for the tenant or if rate-limited. Then call login with provider: phone_otp, the same phone, and the otp. Intentional for harnesses that cannot SIWE; SIWE remains the preferred dedicated-agent path. Do not log the SMS code or tenant_code. Do not paste an end-user OTP into an untrusted chat.

Input parameters:

- `body` (required): JSON request body.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-instruxi-enforcer-v3/api#diagnostics

## Score history

- 2026-09-20: 76
- 2026-09-19: 75
- 2026-09-18: 75
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 38
- 2026-09-13: 38
- 2026-09-12: 38
- 2026-09-11: 38
- 2026-09-10: 36
- 2026-09-09: 36

## Common questions

### What is the Enforcer MCP server?

Enforcer is an MCP server listed in the public MCP registry as dev.instruxi.enforcer/v3. Identity and authorization in one system: allow, deny, the reason, and a record. This page covers its hosted endpoint (https://api.instruxi.dev/mcp).

### Is the Enforcer MCP server safe to use?

Enforcer scores 76 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 Enforcer MCP server expose?

Enforcer exposes 7 tools: getAuthConfig, getSiweNonce, login, refreshToken, register, and 2 more. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.

### Does the Enforcer MCP server require authentication?

No. We connected to Enforcer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Enforcer MCP server still maintained?

Enforcer is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.instruxi.dev/mcp
- Website: https://docs.instruxi.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-instruxi-enforcer-v3/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-instruxi-enforcer-v3/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-instruxi-enforcer-v3/api