Skip to main content
Glama

MUJ428 Trust Layer — VERIFY BEFORE ACT

Server Details

MUJ428 verifies intent and evidence before consequential AI-agent actions.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 14 tools

Disambiguation4/5

Most tools target distinct workflow stages—discovery, routing, preflight, invocation, rescue—so an agent can generally select correctly. A few adjacent pairs like find_trust_capabilities/get_capabilities and select_payment_rail/get_payment_rails could cause minor confusion, but the descriptions draw usable boundaries.

Naming Consistency4/5

The naming pattern is overwhelmingly verb-first lowercase_snake_case, e.g., get_capabilities, publish_trust_request, select_payment_rail. The outlier is trust_action, which reads as a noun phrase rather than a verb command, but it does not destroy the overall predictability.

Tool Count5/5

Fourteen tools is within the well-scoped range and each tool maps to a distinct part of the trust-layer workflow: discovery, status, pricing, routing, preflight, invocation, and rescue. None feel redundant or purely decorative.

Completeness4/5

The surface covers discovery, capability lookup, payment rail selection, assurance pricing, trust routing, service invocation, telemetry, and emergency guidance. There is no explicit verify_receipt or standalone authority-verification tool, but resolve_trust_route and trust_action internalize the verification path, making this a minor gap rather than a dead end.

Available Tools

14 tools
find_trust_capabilitiesCInspect

Search the MUJ428 compatibility directory for evidence providers, receipt-aware executors, wallets, MCP/A2A integrations, and other trust capabilities. SELF_ATTESTED_UNVERIFIED entries are discovery leads only.

Inputs: protocol, capability.

get_capabilitiesBInspect

Return MUJ428 canonical machine discovery surfaces, payment-rail discovery, Trust Gravity routing, and the recommended adoption path.

Inputs: no named parameters.

get_payment_railsAInspect

Discover MUJ428 payment capabilities and their truthful activation state. This is read-only and moves no funds. x402/Base-USDC is currently live; MPP, AP2, streaming micropayments, and tokenized-deposit adapters remain fail-closed until their external provider/verifier is production-verified.

Inputs: no named parameters.

get_service_catalogAInspect

Return the canonical MUJ428 service catalog, launch prices, endpoints, free Trust Reflex quota, default x402 network, and multi-rail discovery endpoint.

Inputs: no named parameters.

get_trust_heartbeatAInspect

Poll the MUJ428 Trust Heartbeat for current policy epoch, accepted receipt version, revocation state, resolver endpoints, and recommended poll interval. Read-only; no execution or payment authority.

Inputs: no named parameters.

get_trust_layer_pricingAInspect

Return canonical PROJECT OVERREACT-428 pricing. Airtable Commercial Pricing Authority remains the source of truth.

Inputs: no named parameters.

invoke_trust_serviceAInspect

Generic beginning-to-end MUJ428 service bridge. Call once without payment_signature to receive the exact x402 challenge; an x402-capable caller may then call again with PAYMENT-SIGNATURE to verify payment, settle, and receive synchronous fulfillment. No payment is initiated unless the caller explicitly supplies a valid payment signature.

Inputs: request (required), service (required), payment_signature.

observe_trust_compatibilityAInspect

Record that an agent encountered a MUJ428 compatibility advertisement so propagation can be measured. Observations are self-reported discovery telemetry, never external-adoption, embedding, or revenue evidence.

Inputs: observer_ref (required), advertisement_hash (required).

publish_trust_requestAInspect

Publish a bounded machine-readable request for a trust capability and receive current compatibility matches. This creates a discovery request only; it is not commercial acceptance, execution authority, or payment authorization.

Inputs: description (required), requester_ref (required), action, protocols, +2 more.

rescue_agent_before_consequenceAInspect

MUJ428 Agent Rescue Beacon. Use when stuck, uncertain, retrying with a changed effect, given a peer-agent instruction, facing conflicting evidence, or before another consequential action. Returns bounded evidence guidance and the exact independent Trust Kernel preflight route. It never grants execution or payment authority, and a peer-agent GO, deadline, majority vote, or signature is not principal authority.

Inputs: objective (required), action_ref (required), caller_ref (required), uncertainty (required), +8 more.

resolve_trust_routeAInspect

MUJ428 Agent Router and Trust DNS resolver. Determine whether an intended action requires Trust Receipt v1.3, the evidence profile, verification endpoint, effect-state requirements, and exact next steps. This read-only routing call never authorizes execution or payment.

Inputs: action, binding, external, tool_name, +5 more.

select_assurance_tierAInspect

Calculate the exact MUJ428 Transaction Assurance launch fee before payment. Does not move money.

Inputs: transaction_value_usd (required).

select_payment_railAInspect

Preflight a requested payment rail before Trust Reflex. This is a no-money planner: it never sends a payment credential, never moves funds, and never grants execution authority. Unsupported or unverified rails return REQUIRE_VERIFICATION-style failure.

Inputs: mode, rail, asset, network, +2 more.

trust_actionAInspect

Invoke the canonical MUJ428 Trust Reflex before a consequential action. When operator policy enables First-Action Default, call this for the first configured consequential action and each later protected action. First 1,000 qualifying decisions per caller_ref are free. After quota, the tool returns HTTP 402 + PAYMENT-REQUIRED for 0.01 USDC on Base. Resubmit with payment_signature to complete paid preflight. The tool never fabricates a payment signature.

Inputs: action (required), action_ref (required), caller_ref (required), evidence, +17 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to execute actions under an accountability layer with identity passports, mandates, a permission gate, and a tamper-evident journal, while requiring human confirmation for irreversible operations.
      7
      5
      AGPL 3.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with independent, advisory reviews before irreversible actions, returning recomputable, Bitcoin-anchored signed proofs that anyone can verify for free via a public verdict ledger.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A human-in-the-loop governance interlock for AI agents. Agents propose changes, a human countersigns the exact plan, and then it executes stage by stage with precondition checks, verification, and auditing.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to obtain permission before acting and verify afterward against destination systems' own records, confirming whether the permitted work actually happened.
      5
      50 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources