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).
Available components
Last scanned (4 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 461 tokens (~65/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +1
- Tool “verify_provider” rewrote its description, which is the text the model reads security
- Schema quality: 52 → 65 ▼ functional
- Server version: 1.1.0 → 1.2.0 functional
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 0
- Stability: 0.07 → unverified ▼ security
- Tool “check_history” rewrote its description, which is the text the model reads security
- Schema quality: 33 → 52 ▼ functional
- Tool coverage: 33% → 50% ▲ functional
- Server version: 1.0.1 → 1.1.0 functional
- New tool “canon_registry_bulk_lookup” functional
- 4 Sept 26 0
- 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 security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.0.1 functional
- “verify_provider” reworded the description of “target” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://provider-trust-mcp.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of provider-trust-mcp.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://provider-trust-mcp.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://provider-trust-mcp.onrender.com/mcp | HTTPS enforced | 301 | https://provider-trust-mcp.onrender.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
canon_registry_bulk_lookup CANON Registry Bulk Lookup ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | One to 100 package or artifact freshness checks. |
No output schema declared.
No examples provided.
check_history Check History ~39
Check recent evidence-backed provider history. Traffic volume is context only and is never presented as buyers, trust, or reputation.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
No output schema declared.
No examples provided.
check_identity Check Identity ~14
Check live provider identity evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_payment Check Payment ~19
Check live x402 payment readiness and real settlement evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_status Check Status ~17
Check whether the Provider Trust backend is live.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_providers Compare Providers ~33
Compare 2-5 providers using live evidence. No made-up score or winner.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | yes | – |
No output schema declared.
No examples provided.
verify_provider Verify Provider ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | Public HTTPS provider, source, MCP, A2A, or API URL. |
No output schema declared.
No examples provided.
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.
remote · provider-trust-mcp.onrender.com
claude mcp add --transport http com-scriptmasterlabs-provider-trust 'https://provider-trust-mcp.onrender.com/mcp'
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.