# SCRIPTMASTERLABS — Provider Trust + CANON (remote · provider-trust-mcp.onrender.com)

Verify providers before agents trust them. Settle-proven end-to-end 2026-11-02 (SELF-PROOF).

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `provider-trust-mcp.onrender.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-scriptmasterlabs-provider-trust/provider-trust-mcp.md), [page](https://verifymcp.io/servers/com-scriptmasterlabs-provider-trust/provider-trust-mcp)

## Channel facts

- Endpoint: `https://provider-trust-mcp.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 461 tokens (~65/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SCRIPTMASTERLABS — Provider Trust + CANON MCP server?

SCRIPTMASTERLABS — Provider Trust + CANON is a hosted endpoint at https://provider-trust-mcp.onrender.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-scriptmasterlabs-provider-trust 'https://provider-trust-mcp.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-scriptmasterlabs-provider-trust": {
      "url": "https://provider-trust-mcp.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-scriptmasterlabs-provider-trust": {
      "type": "http",
      "url": "https://provider-trust-mcp.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-scriptmasterlabs-provider-trust]
url = "https://provider-trust-mcp.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-scriptmasterlabs-provider-trust": {
      "type": "remote",
      "url": "https://provider-trust-mcp.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-scriptmasterlabs-provider-trust --url 'https://provider-trust-mcp.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-scriptmasterlabs-provider-trust:
    url: "https://provider-trust-mcp.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-scriptmasterlabs-provider-trust": {
      "Transport": "http",
      "Url": "https://provider-trust-mcp.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-scriptmasterlabs-provider-trust -t streamable-http -u 'https://provider-trust-mcp.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-scriptmasterlabs-provider-trust": {
      "type": "http",
      "url": "https://provider-trust-mcp.onrender.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 68, +1)

- [security] Tool “verify_provider” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 52 → 65
- [functional] Server version: 1.1.0 → 1.2.0

### 2026-10-25 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 67, 0)

- [security regression] Stability: 0.07 → unverified
- [security] Tool “check_history” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 33 → 52
- [functional improvement] Tool coverage: 33% → 50%
- [functional] Server version: 1.0.1 → 1.1.0
- [functional] New tool “canon_registry_bulk_lookup”

### 2026-09-04 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_status” rewrote its description, which is the text the model reads
- [security] Tool “check_history” rewrote its description, which is the text the model reads
- [security] Tool “check_identity” rewrote its description, which is the text the model reads
- [security] Tool “check_payment” rewrote its description, which is the text the model reads
- [security] Tool “compare_providers” rewrote its description, which is the text the model reads
- [security] Tool “verify_provider” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1
- [cosmetic] “verify_provider” reworded the description of “target”

## MCP tools (7)

### `verify_provider` (~146 tokens)

Verify Provider

PAID tool ($0.001 USDC via x402, Base). Verify a provider or source before an AI agent trusts or uses it. Returns live evidence only; unknown stays unknown. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 1000 = $0.001 USDC, payTo of the canonical SML receiver). Settlement is performed by the canonical CANON endpoint on SqueezeOS; this MCP never holds funds and never pays on your behalf.

Input parameters:

- `target` (string, required): Public HTTPS provider, source, MCP, A2A, or API URL.

### `compare_providers` (~33 tokens)

Compare Providers

Compare 2-5 providers using live evidence. No made-up score or winner.

Input parameters:

- `targets` (array, required)

### `check_identity` (~14 tokens)

Check Identity

Check live provider identity evidence.

### `check_payment` (~19 tokens)

Check Payment

Check live x402 payment readiness and real settlement evidence.

### `check_history` (~39 tokens)

Check History

Check recent evidence-backed provider history. Traffic volume is context only and is never presented as buyers, trust, or reputation.

Input parameters:

- `hours` (integer)

### `check_status` (~17 tokens)

Check Status

Check whether the Provider Trust backend is live.

### `canon_registry_bulk_lookup` (~156 tokens)

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.

Input parameters:

- `items` (array, required): One to 100 package or artifact freshness checks.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-scriptmasterlabs-provider-trust/provider-trust-mcp#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 68
- 2026-10-26: 68
- 2026-10-25: 67
- 2026-10-24: 67
- 2026-09-05: 67
- 2026-09-04: 67
- 2026-09-03: 67

## Common questions

### What is the SCRIPTMASTERLABS — Provider Trust + CANON MCP server?

SCRIPTMASTERLABS — Provider Trust + CANON is an MCP server listed in the public MCP registry as com.scriptmasterlabs/provider-trust. Verify providers before agents trust them. Settle-proven end-to-end 2026-11-02 (SELF-PROOF). This page covers its hosted endpoint (https://provider-trust-mcp.onrender.com/mcp).

### Is the SCRIPTMASTERLABS — Provider Trust + CANON MCP server safe to use?

SCRIPTMASTERLABS — Provider Trust + CANON scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SCRIPTMASTERLABS — Provider Trust + CANON MCP server expose?

SCRIPTMASTERLABS — Provider Trust + CANON exposes 7 tools: verify_provider, compare_providers, check_identity, check_payment, check_history, and 2 more. Their descriptions and schemas cost roughly 424 tokens of context every time the server is loaded.

### Does the SCRIPTMASTERLABS — Provider Trust + CANON MCP server require authentication?

No. We connected to SCRIPTMASTERLABS — Provider Trust + CANON without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SCRIPTMASTERLABS — Provider Trust + CANON MCP server still maintained?

SCRIPTMASTERLABS — Provider Trust + CANON is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://provider-trust-mcp.onrender.com/mcp
- Repository: https://gitlab.com/script-master-labs-llc-group/provider-trust
- Website: https://scriptmasterlabs.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-scriptmasterlabs-provider-trust/provider-trust-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-scriptmasterlabs-provider-trust/provider-trust-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-scriptmasterlabs-provider-trust/provider-trust-mcp