# SCRIPTMASTERLABS — Provider Trust [Verified] [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://www.scriptmasterlabs.com/api/openai-mcp  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/scriptmasterlabs-provider-trust

## Description
Read-only Universal Trust Passport MCP for verifying public provider evidence across MCP, A2A, API and x402: runtime reachability, payment metadata, settlement evidence and trust signals.

## Tools
Capabilities this server exposes over MCP:

- **verify_provider** — Verify a provider or source before an AI agent trusts or uses it. Returns live evidence only; unknown stays unknown.
- **compare_providers** — Compare 2-5 providers using live evidence. No made-up score or winner.
- **check_identity** — Check live provider identity evidence.
- **check_payment** — Check live x402 payment readiness and real settlement evidence.
- **check_history** — Check recent evidence-backed provider history. Traffic volume is context only and is never presented as buyers, trust, or reputation.
- **check_status** — Check whether the Provider Trust backend is live.
- **canon_registry_bulk_lookup** — PAID tool ($0.01 USDC via x402, Base). Resolve up to 100 artifact freshness records in one call against live registries and cryptographically verified CANON publisher manifests: detects stale mirrors, superseded artifacts, and publisher/registry conflicts. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 10000 = $0.01 USDC, payTo of the CANON endpoint). Settlement is performed by the canonical CANON endpoint on SqueezeOS; this MCP never holds funds and never pays on your behalf.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What SCRIPTMASTERLABS — Provider Trust MCP server does

SCRIPTMASTERLABS — Provider Trust provides read-only MCP tools for assessing public evidence about service providers. The supported evidence areas span MCP, A2A, API, and x402 providers. Checks can cover whether a provider is reachable, what identity evidence is available, whether payment arrangements appear ready, whether settlement evidence exists, and what privacy-safe historical trust information is available.

The service is designed for verification before use rather than for changing provider records or executing transactions. Its results preserve an unknown state when the available evidence does not establish an answer. This makes it suitable for workflows that need to distinguish missing or inconclusive evidence from a positive or negative finding.

## Tools and capabilities

The SCRIPTMASTERLABS — Provider Trust MCP server exposes six tools:

- `verify_provider` verifies a provider before use, using live evidence and leaving unsupported conclusions as unknown.
- `compare_providers` places evidence for multiple providers side by side. It does not manufacture a winner or calculate a composite score.
- `check_identity` examines live evidence associated with a provider’s identity.
- `check_payment` checks x402 contract information, payment readiness, and settlement evidence.
- `check_history` retrieves privacy-safe historical trust evidence.
- `check_status` checks the authoritative status of the backend.

Together, these tools support both an overall pre-use check and narrower investigations. For example, an agent can inspect identity or payment evidence independently, then compare several providers without treating the comparison as an automated ranking.

## How it works

An MCP client invokes the verification tools and receives evidence-based results from the provider-trust service. The checks are described as live for provider verification, identity, and payment-related inspection. The available description does not specify a scoring formula, and `compare_providers` explicitly avoids producing a fabricated winner or composite score.

Payment inspection is specific to x402-related evidence: the tool can check the contract, readiness, and settlement dimensions. Historical inspection is limited to privacy-safe trust evidence. Backend health or authority can be checked separately through `check_status`.

## Setup and configuration

The listed source for SCRIPTMASTERLABS — Provider Trust is `https://www.scriptmasterlabs.com/api/openai-mcp`.

## Limitations and notes

SCRIPTMASTERLABS — Provider Trust should be treated as an evidence-checking service, not as a guarantee that a provider is safe or suitable. Unknown results remain unknown, and comparisons do not select a winner. Those details should be verified from the source before deployment.

_Full upstream README: https://allmcps.com/mcp/scriptmasterlabs-provider-trust/readme_