Log inSubmit server
S

SCRIPTMASTERLABS — Provider Trust

Read-only MCP tools for checking provider identity, payments, history, status, and live trust evidence.

InstallWebsite
Get support Full README Compare alternatives Embed widget

Install SCRIPTMASTERLABS — Provider Trust

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://www.scriptmasterlabs.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · 1d agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 10/25/2026, 5:48:02 PM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://www.scriptmasterlabs.com/mcp

Overview

SCRIPTMASTERLABS — Provider Trust MCP server checks public provider evidence across MCP, A2A, API, and x402 systems. Its read-only tools inspect runtime reachability, identity, payment metadata, settlement evidence, historical trust signals, and backend status. Use it before calling an unfamiliar provider or when comparing providers without reducing incomplete evidence to a fabricated score.

Use cases

  • Verify a provider before sending it work
  • Compare provider evidence side by side
  • Check x402 payment and settlement readiness
  • Inspect historical trust evidence
  • Confirm backend status before verification

Key features

  • Read-only provider verification
  • Live identity and reachability evidence
  • x402 contract and settlement checks
  • Privacy-safe historical trust checks
  • Side-by-side provider comparison
  • Unknown-preserving results without composite scores

Tools7

What SCRIPTMASTERLABS — Provider Trust lets your agent do. Expand a tool for its parameters.

Verified live~720 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 54d

What it can do

From the 7 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 7
Tool definitions changed on 2026-10-25. Review them if you approved this server earlier.

Observed 2026-10-25 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

MaintenanceActively maintainedStatus declared by the project or listing owner.
Tools exposed7Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How SCRIPTMASTERLABS — Provider Trust works

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.

Read the full README

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SCRIPTMASTERLABS — Provider Trust

SCRIPTMASTERLABS — Provider Trust is an MCP server that connects agents to public provider evidence across MCP, A2A, API, and x402 systems. Its main tools verify providers, compare evidence, check identity, inspect payment and settlement details, review privacy-safe history, and query authoritative backend status.

The listed source endpoint is https://www.scriptmasterlabs.com/api/openai-mcp, but the required transport, client configuration, authentication, and environment variables are unspecified.

The source identifies MCP tools and an endpoint, but it does not name supported clients or provide Cursor configuration instructions.

No. Its comparison tool presents provider evidence side by side without fabricating a winner or calculating a composite score. Verification also preserves unknown results when the available live evidence does not establish an answer.

It checks x402 contract information, payment readiness, and settlement evidence.

Related MCP servers

All in Finance & Fintech All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSCRIPTMASTERLABS — Provider Trust AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/scriptmasterlabs-provider-trust?style=directory)](https://allmcps.com/mcp/scriptmasterlabs-provider-trust)
HTML Embed
<a href="https://allmcps.com/mcp/scriptmasterlabs-provider-trust"><img src="https://allmcps.com/api/badge/scriptmasterlabs-provider-trust?style=directory" alt="SCRIPTMASTERLABS — Provider Trust on AllMCPs" /></a>