MUJ428 Trust Layer — Bind Approved Intent to Verified Effect
Server Details
Payment-rail-independent intent-to-effect integrity for consequential agent actions.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools serve clearly distinct roles: one provides requirements/information, the other performs the decision/verification action. No overlap exists, so an agent should never confuse which tool to call for a given step.
Both tool names use a verb-led snake_case pattern ('get_evidence_signal_requirements', 'trust_action'), but 'trust_action' is less standard as a verb phrase. The two names are generally consistent and predictable.
With only two tools, the surface feels thin even for a specialized trust layer. The count is acceptable for a narrowly scoped server, but it hovers at the borderline where more operational tools would likely be needed.
The server promises to bind intent to verified effect, yet there is no obvious tool for submitting evidence, recording completed actions, or retrieving past trust receipts. The current surface covers upfront requirements and one-shot decisions, but leaves the verification loop incomplete.
Available Tools
2 toolsget_evidence_signal_requirementsEvidence Signal RequirementsARead-onlyIdempotentInspect
Returns MUJ428 evidence-check payment, network, endpoint, and assurance-pricing requirements before an autonomous payment.
Inputs: no named parameters.
trust_actionMUJ428 Trust ReflexARead-onlyIdempotentInspect
VERIFY BEFORE ACT across payments, purchases, delegation, approvals, writes, releases, commits, and other consequential actions. Returns ALLOW, VERIFY, REQUIRE_VERIFICATION, or DENY plus Trust Receipt v1.3; FREE_PREFLIGHT execution_authority=false and no funds are moved.
Inputs: action (required), evidence, external, milestone, +12 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Independent effect verification and signed receipts for consequential AI agent actions.
External counterparty-risk checks and signed receipts for autonomous agents and machine payments.
Bounded authorization and independently verifiable execution evidence for agents.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceTamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to use payment APIs safely by gating every tool call through deterministic mandates, value checks, and an exactly-once ledger, so they cannot pay twice or exceed authorisation.36 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnforces verifiable authorization, budgets, approvals, and audit trails between an agent and merchant/payment MCP servers, so that the legality of an entire transaction — not just a single call — is checked before money moves. Adds default-deny policy, two-phase budget reserve/commit, action-bound approvals, transaction guards against double-charging or unpaid fulfillment, result sanitization, and tamper-evident hash-chain evidence.2MIT
- AlicenseNot gradedqualityAmaintenanceDeterministic, auditable payment policy enforcement for AI agents. It provides pre-action authorization with scopes, budgets, allowlists, and signed mandates via an MCP server.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.