AgenticRail Gate - sequence enforcement and verifiable audit receipts for AI agent compliance
REMOTE · MCP.AGENTICRAIL.NZ · SCANNED SEP 22
Deterministic runtime enforcement of step order for AI agents: ALLOW/DENY before a step runs.
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1282 tokens (~641/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 AgenticRail Gate - sequence enforcement and verifiable… MCP server?
AgenticRail Gate - sequence enforcement and verifiable… is a hosted endpoint at https://mcp.agenticrail.nz/, 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.agenticrail.nz
claude mcp add --transport http nz-agenticrail-gate 'https://mcp.agenticrail.nz/'
{
"mcpServers": {
"nz-agenticrail-gate": {
"url": "https://mcp.agenticrail.nz/"
}
}
} {
"servers": {
"nz-agenticrail-gate": {
"type": "http",
"url": "https://mcp.agenticrail.nz/"
}
}
} [mcp_servers.nz-agenticrail-gate] url = "https://mcp.agenticrail.nz/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nz-agenticrail-gate": {
"type": "remote",
"url": "https://mcp.agenticrail.nz/",
"enabled": true
}
}
} openclaw mcp add nz-agenticrail-gate --url 'https://mcp.agenticrail.nz/' --transport streamable-http
mcp_servers:
nz-agenticrail-gate:
url: "https://mcp.agenticrail.nz/" {
"McpServers": {
"nz-agenticrail-gate": {
"Transport": "http",
"Url": "https://mcp.agenticrail.nz/"
}
}
} assistant mcp add nz-agenticrail-gate -t streamable-http -u 'https://mcp.agenticrail.nz/'
{
"mcpServers": {
"nz-agenticrail-gate": {
"type": "http",
"url": "https://mcp.agenticrail.nz/"
}
}
} 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.
- 22 Sept 26 0
- Tool “evaluate_step” rewrote its description, which is the text the model reads security
- 7 Sept 26 +1
- Tool “evaluate_step” rewrote its description, which is the text the model reads security
- Schema quality: 488 → 605 ▼ functional
- “evaluate_step” reworded the description of “action_type” cosmetic
- “evaluate_step” reworded the description of “step” cosmetic
- 31 Aug 26 −1
- “evaluate_step” reworded the description of “sequence_id” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 27 Aug 26 0
- Server version: 1.0.0 → 1.2.0 functional
- 26 Aug 26 0
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- Schema quality: 331 → 468 ▼ functional
- First check of Destructive annotations: pass functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- “evaluate_step” reworded the description of “step_order” cosmetic
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 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
- 7 Aug 26 0
- Tool “evaluate_step” rewrote its description, which is the text the model reads security
- Schema quality: 270 → 331 ▼ functional
- Schema quality: good → excellent functional
- “evaluate_step” reworded the description of “sequence_id” cosmetic
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.agenticrail.nz/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenticrail.nz | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d2536cb7de3eb8500eeeaa637aa29213 |
| SANs: agenticrail.nz, mcp.agenticrail.nz, *.mcp.agenticrail.nz | ||||||
| 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 secure
Validation of mcp.agenticrail.nz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| nz. | present | 38240, 62081 | 8, 8 | Verified |
| agenticrail.nz. | present | 2371 | 13 | Verified |
| mcp.agenticrail.nz. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=0 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.agenticrail.nz/ | Verified | 200 | |
| http (plaintext) | http://mcp.agenticrail.nz/ | HTTPS enforced | 301 | https://mcp.agenticrail.nz/ |
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 →
evaluate_step ~1,061
Ask the AgenticRail gate to ALLOW or DENY a single step of an agent sequence BEFORE it runs. A denied step must not be executed. You walk away holding a signed, hash-chained record of the run that you can hand to anyone, and they can verify it offline - no callback to us and no account with us. The gate is deterministic (same state+request -> same verdict) and enforces step order, replay protection, timestamp freshness and sealing. START HERE - send this, changing only CHANGE-ME to any unique string of your own, and it will be ALLOWED: {"sequence_id":"CHANGE-ME","step":"intake","action_type":"CHECK_STATE","step_order":["intake","settle"]}. Then send the same call with step 'settle' to close and seal it. Use the demo key by sending no Authorization header, or send Authorization: Bearer <your-key>. NOTE: an anonymous call has its sequence_id rewritten to 'demo-mcp-<your id>'. This is intended, not a leak: it scopes the run to the public demo lane and is how anonymous MCP traffic is identified. Always reuse the sequence_id RETURNED in the response for later steps and for verify_receipt -- the id you sent will not resolve. Typical use is gating the order of a regulated workflow the caller already runs: customer and third-party due diligence, verification of identity before a payment or business relationship, company registry, beneficial-ownership and sanctions screening, supplier and contractor onboarding. This tool performs none of those checks and holds no registry or watchlist data. It decides only whether the step you are about to run is allowed at this point in the order you declared.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Optional human-readable label for the action. |
| action_type | string | yes | The action class for this step. The whole vocabulary is exactly these eight and nothing else is accepted: CHECK_STATE, CLARIFY_NEXT_STEP, SELECT_NEXT_STEP, RECORD_RESULT, WAIT_FOR_SIGNAL, VALIDATE_IN… |
| function | string | – | Defaults to `step`. The rule step === function always holds. |
| inputs | object | – | Optional free-form inputs recorded with the decision. |
| nonce | string | – | Optional unique-per-step UUID for replay protection. Generated automatically if omitted. |
| sequence_id | string | yes | Stable identifier for this run of the sequence. Reuse it across every step of the same sequence. An anonymous call is rewritten to 'demo-mcp-<your id>' and an authenticated demo call to 'demo-<your i… |
| step | string | yes | The step being attempted, e.g. 'intake' or 'review_and_sign'. This is a NAME, not a description. It must be spelled identically on every call, must appear in step_order (for custom sequences), and mu… |
| step_order | array | – | The full ordered list of step names for a CUSTOM sequence. Send it on every call, IDENTICAL each time. Omit only if using AgenticRail's built-in MSMD spine. It is LOCKED on the sequence's first call:… |
No output schema declared.
No examples provided.
verify_receipt ~171
CALL THIS AFTER A SEQUENCE SEALS, and after any DENY, passing the sequence_id RETURNED by evaluate_step. An enforced run that is never verified has produced evidence nobody has checked. Fetch the verification report for an AgenticRail sequence and report whether its receipt chain is intact. Demo- sequences need no key; other sequences need Authorization: Bearer <your-key>. Returns the verification_status (VERIFIED_INTACT / CHAIN_BROKEN / …) plus the per-receipt signature, chain-hash, and independent-archive checks. This is the same evidence a third party can verify offline against the published Ed25519 keys — no need to trust AgenticRail.
| Name | Type | Req | Description |
|---|---|---|---|
| sequence_id | string | yes | The sequence to verify. Use a 'demo-' sequence for keyless verification. |
No output schema declared.
No examples provided.
What is the AgenticRail Gate - sequence enforcement and verifiable… MCP server?
AgenticRail Gate - sequence enforcement and verifiable… is an MCP server listed in the public MCP registry as nz.agenticrail/gate. Deterministic runtime enforcement of step order for AI agents: ALLOW/DENY before a step runs. This page covers its hosted endpoint (https://mcp.agenticrail.nz/).
Is the AgenticRail Gate - sequence enforcement and verifiable… MCP server safe to use?
AgenticRail Gate - sequence enforcement and verifiable… scores 80 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 AgenticRail Gate - sequence enforcement and verifiable… MCP server expose?
AgenticRail Gate - sequence enforcement and verifiable… exposes 2 tools: evaluate_step, verify_receipt. Their descriptions and schemas cost roughly 1,232 tokens of context every time the server is loaded.
Does the AgenticRail Gate - sequence enforcement and verifiable… MCP server require authentication?
No. We connected to AgenticRail Gate - sequence enforcement and verifiable… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgenticRail Gate - sequence enforcement and verifiable… MCP server still maintained?
AgenticRail Gate - sequence enforcement and verifiable… 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.