MUJ428 Trust Layer — VERIFY BEFORE ACT

io.github.wmujahid428-webPublished by GitHub account wmujahid428-webv1.8.3Updated Oct 27, 2026

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

VerifiedStreamable HTTPWeb executableFinanceSecurity & MonitoringAI & ML

Overview

AI-generated overview

A remote trust-check service that returns evidence guidance, routing and payment-rail preflight before an AI agent takes a consequential action.

What you can do
  • Request preflight guidance and evidence before a consequential action, or when stuck or facing conflicting evidence
  • Resolve whether an intended action needs a Trust Receipt, its evidence profile and next steps, and poll the trust heartbeat for policy and revocation state
  • Browse the service catalog, pricing, assurance tiers and payment rails, and preflight a chosen rail without moving funds
  • Search or publish trust-capability requests in a compatibility directory and record compatibility observations
  • Invoke the paid service bridge, which returns an x402 payment challenge before any settlement
When to use it
Worth adding when an agent workflow needs a documented check, routing decision or payment-rail preflight before actions with real consequences, or when you want a machine-readable catalog of trust and evidence services.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. Some tools involve an x402 payment flow on Base-USDC, which requires an x402-capable caller and a payment signature.
Before you install
Several tools are payment-related: the service bridge can settle a payment once a payment signature is supplied, and pricing and assurance-fee tools quote charges. The first 1,000 qualifying decisions per caller reference are free, after which quota applies. Directory entries marked self-attested are unverified leads, and observations are self-reported telemetry. No authentication is declared.

Installation

In SourceWeft

  1. Open MUJ428 Trust Layer — VERIFY BEFORE ACT in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.wmujahid428-web%2Ftrust-layer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "muj428-trust-layer-verify-before-act": {
      "type": "http",
      "url": "https://wepmhfjzckclvywolrek.supabase.co/functions/v1/trust-layer-mcp"
    }
  }
}

README

This repository has no README.

Tools

14

rescue_agent_before_consequence

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.

Parametersactionbindingtriggerexternalobjectiverequiredaction_refrequiredcaller_refrequiredcapabilityuncertaintyrequiredirreversibleconsequentialevidence_refs

trust_action

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.

Parametersactionrequiredevidenceexternalaction_refrequiredamount_usdcaller_refrequiredirreversibleevidence_statesensitive_dataactual_argumentsauthority_expiredpayment_signature+9 more

invoke_trust_service

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.

Parametersrequestrequiredservicerequiredpayment_signature

get_service_catalog

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

Takes no parameters.

get_payment_rails

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.

Takes no parameters.

resolve_trust_route

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.

Parametersactionbindingexternaltool_nameaction_refcapabilityirreversibleconsequentialtool_annotations

get_trust_heartbeat

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.

Takes no parameters.

find_trust_capabilities

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.

Parametersprotocolcapability

publish_trust_request

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.

Parametersactionprotocolscapabilitydescriptionrequiredrequirementsrequester_refrequired

observe_trust_compatibility

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.

Parametersobserver_refrequiredadvertisement_hashrequired

select_payment_rail

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.

Parametersmoderailassetnetworkbase_railauthorization_protocol

get_trust_layer_pricing

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

Takes no parameters.

select_assurance_tier

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

Parameterstransaction_value_usdrequired

get_capabilities

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

Takes no parameters.

Version history

1
  1. v1.8.3LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.