SCRIPTMASTERLABS — SML token-verdict MCP Server

by scriptmasterlabs Your server? Claim it

not responding

SCRIPTMASTERLABS — SML token-verdict is listed as active in the registry but did not answer our last check. It exposes 3 tools.

Send a token/contract address (Base, Ethereum, BSC), get a deterministic verdict (LOW_RISK / CAUTION

Uptime history 5 days of history · worst day 0%

5 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

231 ms

Response time

average over 24h

open, no key

Access

streamable-http

SCRIPTMASTERLABS — SML token-verdict does not always answer

Over the last week it answered 36.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add token-verdict --transport http https://sml-agent-products.onrender.com/token-verdict/mcp

Settings → Connectors → Add custom connector, then paste this address

https://sml-agent-products.onrender.com/token-verdict/mcp

~/.codex/config.toml

[mcp_servers.token-verdict]
url = "https://sml-agent-products.onrender.com/token-verdict/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "token-verdict": {
      "url": "https://sml-agent-products.onrender.com/token-verdict/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "token-verdict": {
      "type": "http",
      "url": "https://sml-agent-products.onrender.com/token-verdict/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

token

token-risk

Token / contract risk verdict ($0.015 via x402 at GET https://sml-agent-products.onrender.com/token-verdict/v1/token-risk). Deterministic on-chain risk verdict + reasons + confidence + signed receipt for one token/contract address. Query: address, chain (base|ethereum|bsc).

token-risk-post

Token risk verdict (POST, AX1-compatible body) ($0.015 via x402 at POST https://sml-agent-products.onrender.com/token-verdict/v1/token-risk). Same verdict; body {tokenAddress|address, chain}.

catalog

catalog

Machine-readable catalog with prices and 402 terms

Endpoints

URL	Transport	State	Latency	Checked
https://sml-agent-products.onrender.com/token-verdict/mcp	streamable-http	answering	231 ms	4 min ago

Alternatives to SCRIPTMASTERLABS — SML token-verdict

same job, measured the same way

Lorg Check

by lorglabs

Is this token a trap? Is this address safe to pay? Signed verdicts on Base and Ethereum.

answering

Chain Check (x402)

by netlify-chaincheck-api

x402-paid on-chain tools: wallet report, contract scan, token risk, gas, address labels (USDC/Base)

6 tools answering

Regressguard

by bharath-code

Deterministic API regression checks for AI agents: snapshot a baseline, catch broken contracts.

local only

traql

by traql

AML risk scoring for crypto addresses and transactions on Ethereum, BSC, TRON, TON, Bitcoin

62 installs/wk local only

Verdigraph

by jdhart81

Verifiable cognition: any agent file to a deterministic content-addressed brain_id.

4 tools answering

Dmcheck

by chaoz23

Deterministic conduct verdicts for live tabletop sessions - CI for running a game.

127 installs/wk local only

Automaton Onchain Tools

by vercel-automaton-tx-explainer

Paid x402 crypto safety tools (Base/ETH/BSC): tx, approvals, contract risk, token deep scan.

49 tools answering

SCRIPTMASTERLABS — PRO-LO

by scriptmasterlabs

Coherence-gated signal engine. Paid verdict settled end-to-end 2026-11-01 (SELF-PROOF, XRPL).

12 tools answering

SCRIPTMASTERLABS — SML token-verdict — questions

Answers built from our own checks of this server.

What can SCRIPTMASTERLABS — SML token-verdict do?

It exposes 3 tools, read directly from the server on our last check. Among them: catalog, token-risk, token-risk-post. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is SCRIPTMASTERLABS — SML token-verdict working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 231 ms. The bar chart above shows every period we have measured.

The registry lists SCRIPTMASTERLABS — SML token-verdict as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect SCRIPTMASTERLABS — SML token-verdict?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does SCRIPTMASTERLABS — SML token-verdict need an API key?

No. SCRIPTMASTERLABS — SML token-verdict completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.