Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SCRIPTMASTERLABS — Agent Verify

REMOTE · SCRIPTMASTERLABS.COM

Proof, not ratings: verified paid agent-job records on Arc + a $0.05 signed Proof Check.

+3 this week 72 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 585 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Changelog

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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 0
    • Tool “proof_check” rewrote its description, which is the text the model reads security
  • 2 Nov 26 +1
    • Tool “proof_check” rewrote its description, which is the text the model reads security
  • 31 Oct 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.

  • 29 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 68

    First indexed and scored.

Diagnostics

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://scriptmasterlabs.com/agent-verify/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=scriptmasterlabs.com CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 a16fdc0ed6a6df91395e3ee9b46caef
SANs: scriptmasterlabs.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 scriptmasterlabs.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
scriptmasterlabs.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=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://scriptmasterlabs.com/agent-verify/mcp Verified 200
http (plaintext) http://scriptmasterlabs.com/agent-verify/mcp HTTPS enforced 301 https://scriptmasterlabs.com/agent-verify/mcp
MCP tools · 8 exposed · ~546 tokens

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 →

Tool Tokens
agent_records ~84

All Proof Records for an agent plus verified totals (no numeric score; that is the paid Proof Check). Free, read-only. An empty list means no verified history here, not a negative finding.

NameTypeReqDescription
agentstringyesAgent identity: 0x address, did:pkh:eip155:<chain>:0x… or did:ethr:0x…

No output schema declared.

No examples provided.

board_search ~62

Open, funded jobs on SML's Bid-cast board (escrow on Circle Arc), as published by the venue. Free, read-only; to post or bid, use Bid-cast itself (EIP-191 signed).

NameTypeReqDescription
capabilitystring––

No output schema declared.

No examples provided.

ledger_list ~40

Latest Proof Records, newest first, with the ledger head. Free, read-only.

NameTypeReqDescription
before_seqinteger––
limitinteger––

No output schema declared.

No examples provided.

methodology ~21

The published Proof Score methodology and its version. Free, read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

proof_check ~201

Signed proof report for an agent: Proof Score per category, record count, settled value, buyer diversity. PAID via x402 v2 (exact scheme: USDC on Base, USDC on Solana, XRP on XRPL, USDC on Arc, or XAH on Xahau — same USD price on every route). Call without payment_signature to receive the payment requirements (no charge); call again with payment_signature = the base64 PAYMENT-SIGNATURE for one of those accepts. Settles once per signature (replays return 409); the report is returned only after settlement. Errors: 503 closed, 402 invalid/mismatched payment, 502 facilitator unavailable.

NameTypeReqDescription
agentstringyesAgent identity: 0x address, did:pkh:eip155:<chain>:0x… or did:ethr:0x…
payment_signaturestring–base64 x402 v2 PAYMENT-SIGNATURE

No output schema declared.

No examples provided.

proof_index ~28

Verified agent-job volume by venue, category and day (Proof Records only). Free, read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

proof_verify_record ~77

Verify a Proof Record yourself: recompute its hash, check the service signature against the published key, the hash-chain link, its Arc Merkle anchor, and re-read the release transaction on Arc mainnet. Free, read-only. Error: record not found.

NameTypeReqDescription
record_idstringyese.g. pr_000001

No output schema declared.

No examples provided.

service_status ~33

Live status of the ledger, verifier, Arc anchoring and the SML components the board probes. Free, read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the SCRIPTMASTERLABS — Agent Verify MCP server?

SCRIPTMASTERLABS — Agent Verify is a hosted endpoint at https://scriptmasterlabs.com/agent-verify/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 · scriptmasterlabs.com

# add to Claude Code
claude mcp add --transport http com-scriptmasterlabs-agent-verify 'https://scriptmasterlabs.com/agent-verify/mcp'
Common questions

What is the SCRIPTMASTERLABS — Agent Verify MCP server?

SCRIPTMASTERLABS — Agent Verify is an MCP server listed in the public MCP registry as com.scriptmasterlabs/agent-verify. Proof, not ratings: verified paid agent-job records on Arc + a $0.05 signed Proof Check. This page covers its hosted endpoint (https://scriptmasterlabs.com/agent-verify/mcp).

Is the SCRIPTMASTERLABS — Agent Verify MCP server safe to use?

SCRIPTMASTERLABS — Agent Verify 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 — Agent Verify MCP server expose?

SCRIPTMASTERLABS — Agent Verify exposes 8 tools: proof_check, proof_verify_record, agent_records, ledger_list, proof_index, and 3 more. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.

Does the SCRIPTMASTERLABS — Agent Verify MCP server require authentication?

No. We connected to SCRIPTMASTERLABS — Agent Verify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SCRIPTMASTERLABS — Agent Verify MCP server still maintained?

SCRIPTMASTERLABS — Agent Verify 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.