Wall-Event Circumvention Sentinel
Server Details
Sequence sentinel: wall events + channel-switch scoring; HALT, hold, signed receipt.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
The hold lifecycle tools (list_holds, deny_hold, release_hold) are clearly distinct. However, score_action, query_verdict, and observe_result all touch scoring/verdict/result recording, and the cryptic rail/x402 descriptions make their boundaries less obvious. An agent could plausibly misselect score_action when it actually needs query_verdict.
All tool names follow a consistent snake_case verb_noun pattern: deny_hold, list_holds, observe_result, query_verdict, release_hold, score_action. The only minor variation is pluralization in list_holds, which is natural and does not break the pattern.
Six tools is well-scoped for a focused sentinel that manages holds, scores actions, observes runtime results, and queries verdicts. Each tool appears to earn its place without obvious padding or severe under-coverage.
The set covers hold listing, denial, and release, plus action scoring, result observation, and verdict querying. Minor gaps remain around creating holds, inspecting wall configuration/state, or retrieving a single verdict/hold by identifier, but core workflows appear workable.
Available Tools
6 toolslist_holdsCInspect
List your held actions with wall + signals.
Inputs: no named parameters.
observe_resultCInspect
Record a runtime tool result; a wall is recorded only when the event is runtime-sourced.
Inputs: event (required).
query_verdictCInspect
Per-verdict query shape over MCP: scores via the tier rail; the $0.01 x402 rail is POST /query.
Inputs: action (required).
release_holdCInspect
Release a hold (single-use; returns exactly the held action).
Inputs: hold_id (required).
score_actionCInspect
Score one action against the operator's live wall state (tier allowance accounting applies).
Inputs: action (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Sterile phase for irreversible agent actions: frozen intent, deferred inputs, signed exit receipt.
Evidence-bound stopping for agents: judgment ledger, binding futility verdicts, signed receipts.
Coherence-gated signal engine. Paid verdict settled end-to-end 2026-11-01 (SELF-PROOF, XRPL).
Real MCP handshake witness graded per-client, signed expiring receipt.
Related MCP Servers
- AlicenseAqualityBmaintenanceCaller ID and a wax seal for AI agents: signed, sealed handoffs between agents, with trust the receiver computes. An MCP server (stdio) with 9 tools for sending/receiving signed bundles; confirmation of a sender's key is a human word-pair comparison that agents cannot perform.91Apache 2.0
- AlicenseAqualityBmaintenancePolicy-gated agent spend with signed receipts and rail-extract audit: a fail-closed gate issues a COSE receipt for every allowed payment, and the audit reconciles those receipts against a rail extract so a settlement with no receipt is named rather than assumed. It settles on a mock rail, holding no wallet and signing no transaction.51Apache 2.0
- AlicenseAqualityBmaintenanceStops agents double-firing side effects like double-charges or duplicate sends: same-instant races elect exactly one winner, and late duplicates get a sealed, content-addressed receipt replayed instead of a second execution. Tools: fence_prepare, fence_commit, fence_abort.3MIT
- AlicenseBqualityBmaintenanceSigned receipts for agent actions and a read-only-allowlist decision gate, as an MCP server. Ed25519, plus ML-DSA-65 when the post-quantum backend is available. gate_decision returns ALLOW, DENY or ESCALATE from action names and does not observe or block anything. verify_receipt takes expected_kid to pin which key signed. Seven tools.1650 PyPI1Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.