Skip to main content
Glama

SCRIPTMASTERLABS — Provider Trust + CANON

Server Details

Verify providers before agents trust them. Settle-proven end-to-end 2026-11-02 (SELF-PROOF).

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

The four check_* tools target clearly different evidence facets (identity, payment readiness/settlement, history, backend liveness), and canon_registry_bulk_lookup targets artifact freshness rather than provider trust. The one soft boundary is verify_provider (paid, single target) versus compare_providers (free, 2-5 targets), which gathers evidence the same way — agents may wonder why pay for one provider when a free multi-provider call exists. Overall mostly distinct with that single confusion point.

Naming Consistency4/5

Names follow predictable snake_case verb_noun patterns: check_identity, check_payment, check_history, check_status, verify_provider, compare_providers. canon_registry_bulk_lookup is the outlier with a four-segment noun-heavy construction, but it is still readable and consistent in style.

Tool Count4/5

Seven tools is well within a healthy range and each has a clear job, with granular checks plus aggregated verify/compare forming a sensible layering. The slight mismatch is that canon_registry_bulk_lookup belongs to an adjacent domain (artifact freshness/supersession) rather than provider trust, making the server feel like two small surfaces bundled together.

Completeness4/5

The trust-verification lifecycle is well covered: identity, payment, history, status, single-target verification, and multi-target comparison, with bulk canonical artifact resolution on the side. Gaps are modest — there is no discovery/listing tool to find providers before verifying them, and no single-artifact counterpart to the bulk canon lookup (though bulk with one item covers it).

Available Tools

7 tools
canon_registry_bulk_lookupCANON Registry Bulk LookupAInspect

PAID tool ($0.01 USDC via x402, Base). Resolve up to 100 artifact freshness records in one call against live registries and cryptographically verified CANON publisher manifests: detects stale mirrors, superseded artifacts, and publisher/registry conflicts. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 10000 = $0.01 USDC, payTo of the CANON endpoint). Settlement is performed by the canonical CANON endpoint on SqueezeOS; this MCP never holds funds and never pays on your behalf.

Inputs: items (required).

check_historyCheck HistoryC
Read-onlyIdempotent
Inspect

Check recent evidence-backed provider history. Traffic volume is context only and is never presented as buyers, trust, or reputation.

Inputs: hours.

check_identityCheck IdentityA
Read-onlyIdempotent
Inspect

Check live provider identity evidence: the published ERC-8004 agent identity document and its source/status envelope, returned exactly as observed. A successful fetch shows declared identity only — it is not external certification and not settlement verification — and missing evidence stays unknown rather than being filled in. Free, read-only.

Inputs: no named parameters.

check_paymentCheck PaymentA
Read-onlyIdempotent
Inspect

Check live x402 payment readiness and real settlement evidence: the canonical x402 payment contract, the readiness endpoint, and recorded settlement evidence, returned as separate envelopes. A 402 challenge, a signature, a readiness flag, or an HTTP 200 alone does not prove settled, accepted delivery — only settlement evidence does. Free, read-only; never signs or spends.

Inputs: no named parameters.

check_statusCheck StatusA
Read-onlyIdempotent
Inspect

Check whether the Provider Trust backend is live: returns the authoritative backend status envelope for the service that powers verify_provider, compare_providers, and the other checks. Use it to distinguish a Provider Trust outage from a target-side evidence gap before relying on any check result. Free, read-only.

Inputs: no named parameters.

compare_providersCompare ProvidersA
Read-onlyIdempotent
Inspect

Compare 2-5 providers side by side using live evidence gathered the same way verify_provider gathers it — identity, payment-readiness, and status evidence for each target, returned as a separate envelope per provider. No composite score is computed and no winner is declared; unknown evidence stays unknown for every target. Free, read-only.

Inputs: targets (required).

verify_providerVerify ProviderAInspect

PAID tool ($0.001 USDC via x402, Base). Verify a provider or source before an AI agent trusts or uses it. Returns live evidence only; unknown stays unknown. Send the x402 PAYMENT-SIGNATURE header on the /mcp request; without payment the call returns the canonical x402 challenge (HTTP 402, amount 1000 = $0.001 USDC, payTo of the canonical SML receiver). Settlement is performed by the canonical CANON endpoint on SqueezeOS; this MCP never holds funds and never pays on your behalf.

Inputs: target (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      alalanet-agent is the open local client of alalanet.com, the free service an AI agent asks before it installs, connects or pays. A stdio MCP server whose key stays on your machine: it signs agent passports, receipts, skill and package releases, mail and memory locally (16 tools) and checks files and agents against alalanet's public transparency log. Hosted checks: https://alalanet.com/mcp.
      2
      16
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to verify packages, datasets, files, and claims before acting on untrusted data, returning an evidence report with sources, timestamps, and explicit limits rather than a simple pass/fail checkmark.
      1
      387 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources