SCRIPTMASTERLABS — Triple-Trigger
com.scriptmasterlabs/triple-triggerscriptmasterlabs.comstreamable-httpv2.0.0Scanned
Triple-Trigger MCP: SPEC v2 triple-trigger ticker scans on live Schwab data. $0.05 x402 on Base.
1 tool: 1 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Anlyon alternative
1 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Changes things 1Claude Code: ask
triple_trigger_scanRun one SML Triple-Trigger SPEC v2 scan of a ticker on live Schwab data and get a VERDICT (all three triggers true, with entry/stop/target/R plan), WATCH (two of three), or NONE re…Reads text others write1 finding
Why it is in this group
- The name "triple_trigger_scan" says "trigger": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "triple_trigger_scan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "triple_trigger_scan" says "trigger": a word for a change.
Description, as the server wrote it Run one SML Triple-Trigger SPEC v2 scan of a ticker on live Schwab data and get a VERDICT (all three triggers true, with entry/stop/target/R plan), WATCH (two of three), or NONE result, with market/volatility/cap tags and data timestamps. Use it to check whether a ticker currently shows a liquidity sweep + Fibonacci reclaim (T1), a VWAP reclaim with relative-volume thrust (T2), and same-side unusual options premium vs the ticker's own 20-session baseline (T3). Missing data is reported as no_data, never estimated. $0.05 USDC on Base per accepted scan. First 3 VERDICT scans free with a trial key (pass trial_key; get one via POST /triple-trigger/trial); WATCH/NONE never consume credits.
Annotations the server declares
- destructiveHint: false
- openWorldHint: true
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
The server marks "triple_trigger_scan" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "triple_trigger_scan" says "trigger": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 2.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http triple-trigger https://squeezeos-api.onrender.com/triple-trigger/mcpclaude mcp add --transport http triple-trigger https://squeezeos-api.onrender.com/triple-trigger/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__triple-trigger__triple_trigger_scan"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as triple-trigger. Review it before you use it.
Capability tags behind 1 rule
- mcp__triple-trigger__triple_trigger_scan untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.scriptmasterlabs/triple-trigger/verify?hash=c11c622443ca70318269cbdd4a57c12054265351786e14b9b6eeeb28c148ddb7" | jq -e '.changed == false'Pinned hash c11c622443ca, from Oct 24, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.scriptmasterlabs/triple-trigger/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.scriptmasterlabs/triple-trigger)Source: MCP Registry. Synced Oct 24, 2026, 10:17 UTC.