SCRIPTMASTERLABS — SML agent-safety
REMOTE · SML-AGENT-PRODUCTS.ONRENDER.COM
Three fast safety checks for agents, each with a signed hash-chained receipt: (1) prompt-injection c
Available components
Last scanned (3 hours ago)
Scores higher than 43% 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 296 tokens (~74/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 59
First indexed and scored.
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://sml-agent-products.onrender.com/agent-safety/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 sml-agent-products.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://sml-agent-products.onrender.com/agent-safety/mcp | Verified | 200 | |
| http (plaintext) | http://sml-agent-products.onrender.com/agent-safety/mcp | HTTPS enforced | 301 | https://sml-agent-products.onrender.com/agent-safety/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 →
catalog ~17
Machine-readable catalog with prices and 402 terms
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
prompt-injection ~82
Prompt-injection check ($0.004 via x402 at POST https://sml-agent-products.onrender.com/agent-safety/v1/prompt-injection). POST {text}. Verdict safe/suspicious/malicious + score + categories + matched spans + obfuscation tricks found + recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Agent-bound text to classify |
No output schema declared.
No examples provided.
url-safety ~89
URL safety check ($0.004 via x402 at GET https://sml-agent-products.onrender.com/agent-safety/v1/url-safety). GET ?url=. Verdict safe/suspicious/dangerous + score + reasons (lookalike, brand impersonation, domain age, redirects, seed-phrase/drainer content, agent-targeted injection).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | – |
No output schema declared.
No examples provided.
x402-health ~108
x402 endpoint health / pay-readiness ($0.002 via x402 at GET https://sml-agent-products.onrender.com/agent-safety/v1/x402-health). GET ?url=&method=GET|POST&maxUsd=. Live probe (never pays): go/caution/no_go, recommended payment option, every accepts problem, discovery + bazaar metadata, latency.
| Name | Type | Req | Description |
|---|---|---|---|
| maxUsd | number | – | – |
| method | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the SCRIPTMASTERLABS — SML agent-safety MCP server?
SCRIPTMASTERLABS — SML agent-safety is a hosted endpoint at https://sml-agent-products.onrender.com/agent-safety/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 · sml-agent-products.onrender.com
claude mcp add --transport http com-scriptmasterlabs-agent-safety 'https://sml-agent-products.onrender.com/agent-safety/mcp'
What is the SCRIPTMASTERLABS — SML agent-safety MCP server?
SCRIPTMASTERLABS — SML agent-safety is an MCP server listed in the public MCP registry as com.scriptmasterlabs/agent-safety. Three fast safety checks for agents, each with a signed hash-chained receipt: (1) prompt-injection c. This page covers its hosted endpoint (https://sml-agent-products.onrender.com/agent-safety/mcp).
Is the SCRIPTMASTERLABS — SML agent-safety MCP server safe to use?
SCRIPTMASTERLABS — SML agent-safety scores 60 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 — SML agent-safety MCP server expose?
SCRIPTMASTERLABS — SML agent-safety exposes 4 tools: prompt-injection, url-safety, x402-health, catalog. Their descriptions and schemas cost roughly 296 tokens of context every time the server is loaded.
Does the SCRIPTMASTERLABS — SML agent-safety MCP server require authentication?
No. We connected to SCRIPTMASTERLABS — SML agent-safety without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SCRIPTMASTERLABS — SML agent-safety MCP server still maintained?
SCRIPTMASTERLABS — SML agent-safety 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.