Provider Trust — Verify a Source or Provider
REMOTE · SQUEEZEOS-API.ONRENDER.COM · SCANNED SEP 22
Verify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown.
Available components
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 150 tokens (~25/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Provider Trust — Verify a Source or Provider MCP server?
Provider Trust — Verify a Source or Provider is a hosted endpoint at https://squeezeos-api.onrender.com/mcp/provider-trust, 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 · squeezeos-api.onrender.com
claude mcp add --transport http com-scriptmasterlabs-provider-trust 'https://squeezeos-api.onrender.com/mcp/provider-trust'
{
"mcpServers": {
"com-scriptmasterlabs-provider-trust": {
"url": "https://squeezeos-api.onrender.com/mcp/provider-trust"
}
}
} {
"servers": {
"com-scriptmasterlabs-provider-trust": {
"type": "http",
"url": "https://squeezeos-api.onrender.com/mcp/provider-trust"
}
}
} [mcp_servers.com-scriptmasterlabs-provider-trust] url = "https://squeezeos-api.onrender.com/mcp/provider-trust"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-scriptmasterlabs-provider-trust": {
"type": "remote",
"url": "https://squeezeos-api.onrender.com/mcp/provider-trust",
"enabled": true
}
}
} openclaw mcp add com-scriptmasterlabs-provider-trust --url 'https://squeezeos-api.onrender.com/mcp/provider-trust' --transport streamable-http
mcp_servers:
com-scriptmasterlabs-provider-trust:
url: "https://squeezeos-api.onrender.com/mcp/provider-trust" {
"McpServers": {
"com-scriptmasterlabs-provider-trust": {
"Transport": "http",
"Url": "https://squeezeos-api.onrender.com/mcp/provider-trust"
}
}
} assistant mcp add com-scriptmasterlabs-provider-trust -t streamable-http -u 'https://squeezeos-api.onrender.com/mcp/provider-trust'
{
"mcpServers": {
"com-scriptmasterlabs-provider-trust": {
"type": "http",
"url": "https://squeezeos-api.onrender.com/mcp/provider-trust"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 0
- Server version: 1.0.0 → 1.0.1 functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://squeezeos-api.onrender.com/mcp/provider-trust
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 squeezeos-api.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://squeezeos-api.onrender.com/mcp/provider-trust | Verified | 200 | |
| http (plaintext) | http://squeezeos-api.onrender.com/mcp/provider-trust | HTTPS enforced | 301 | https://squeezeos-api.onrender.com/mcp/provider-trust |
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 →
check_history Check History ~22
Check privacy-safe historical trust evidence.
| 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 ~20
Check live x402 contract, readiness, and settlement evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_status Check Status ~14
Check the authoritative backend status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_providers Compare Providers ~30
Compare provider evidence side by side without a fabricated winner or composite score.
| Name | Type | Req | Description |
|---|---|---|---|
| targets | array | yes | – |
No output schema declared.
No examples provided.
verify_provider Verify Provider ~30
Verify a provider before using it. Live evidence only; unknown stays unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
What is the Provider Trust — Verify a Source or Provider MCP server?
Provider Trust — Verify a Source or Provider is an MCP server listed in the public MCP registry as com.scriptmasterlabs/provider-trust. Verify a source or provider before an AI agent trusts it. Evidence only; unknown stays unknown. This page covers its hosted endpoint (https://squeezeos-api.onrender.com/mcp/provider-trust).
Is the Provider Trust — Verify a Source or Provider MCP server safe to use?
Provider Trust — Verify a Source or Provider scores 78 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 Provider Trust — Verify a Source or Provider MCP server expose?
Provider Trust — Verify a Source or Provider exposes 6 tools: verify_provider, compare_providers, check_identity, check_payment, check_history, check_status. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.
Does the Provider Trust — Verify a Source or Provider MCP server require authentication?
No. We connected to Provider Trust — Verify a Source or Provider without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Provider Trust — Verify a Source or Provider MCP server still maintained?
Provider Trust — Verify a Source or Provider is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.