Skip to main content
Glama
duskwire

preflight402

by duskwire
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
preflightA

One free call before your agent pays.

Probes the URL (no wallet, payment, or auth) and returns a
trust-preview.v1 verdict: liveness and latency, TLS validity, the 402
payment handshake with protocol detection (x402 v1/v2, MPP-capable),
detected networks/asset/price with a USD estimate, ERC-8004 identity
binding with Sybil-filtered reputation for the payee (which can adjust
the recommendation), and a proceed / caution / avoid recommendation with
human-readable reasons. Paid-tier fields (uptime history, reseller
analysis) are present but null on the free tier.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool available, there is no possibility of confusion between tools. The tool's purpose is clearly defined as a URL preflight check.

Naming Consistency5/5

The single tool name 'preflight' is clear and appropriate for its function, and with only one tool, there is no inconsistency to evaluate.

Tool Count3/5

A single tool is on the low end of the scale, suggesting a thin server. However, the tool is comprehensive and well-scoped to the server's stated purpose of preflight checks, making it borderline.

Completeness5/5

The preflight tool covers all essential aspects of the intended function: probing URLs, checking liveness/TLS, payment handshake, network detection, identity, and recommendation. No obvious gaps exist within the preflight domain.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources