Skip to main content
Glama
JonasFuchss

x402 Trust Tools

by JonasFuchss
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

x402 watch — create 30-day endpoint monitor (paid)

x402_watch_create

Create a 30-day watch on an x402 endpoint to receive alerts on changes that break autonomous payments, such as payTo changes and liveness issues. Pay-per-call with auto-pay or price quote.

Instructions

Start monitoring ONE x402 endpoint for 30 days. Get alerted on changes that break autonomous payment: payTo changes (possible takeover/rug), price changes, asset/network changes, 402-spec regressions, delisting, and liveness down/recovered. A self-healing endpoint that repeatedly blips is auto-detected as liveness_flapping and its individual down/up alerts are coalesced into a single flapping notice (plus one 'stopped flapping' notice when it stabilizes) so you are not spammed. Returns a one-time bearer secret + poll URL + renew URL + edit URL + cancel URL + machine-readable next_steps. Use x402_watch_events to poll the append-only log, or configure push delivery to one or more signed HTTPS webhooks and/or Slack/Discord incoming webhooks (max 5 each). webhook_url/slack_url accept a single URL string or an array of URLs. All URLs are connection-tested BEFORE payment — unreachable URLs are rejected with no charge (retry with a corrected URL). On success the response reports per-URL delivery in delivery.connection_test. Webhook signature: x-signature = 'sha256=' + HMAC-SHA256(body) keyed by hex(sha256(secret)), NOT the raw secret. Pay-per-call over x402 (~$0.20); auto-pays if a wallet is configured, otherwise returns the price quote.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsNoEvent types to subscribe to (default all): payto_change, price_change, asset_network_change, spec_regression, delisting, liveness_down, liveness_recovered, liveness_flapping, latency_regression.
endpointYesFull x402 resource URL to watch. It must already be in our observation set.
slack_urlNoOptional Slack or Discord incoming webhook URL(s). Single string or array; max 5.
webhook_urlNoOptional signed HTTPS webhook URL(s) for push delivery. Single string or array; max 5.
liveness_sensitivity_nNoConsecutive missed probes before liveness_down surfaces to you (1=paranoid … 10=relaxed; default 2).

Tool Definition Quality

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses many behaviors: returns bearer secret/poll/renew/edit/cancel URLs, self-healing flapping detection, coalescing alerts, connection testing before payment, webhook signature format, pay-per-call with auto-payment or quote. This is comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph but front-loads the main action. It is concise yet informative; every sentence adds value. Could be slightly more structured (e.g., bullet points) but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, 1 required, and no output schema, the description provides complete context: return values (bearer secret, URLs, next_steps, delivery status), edge cases (connection test, flapping detection), and usage scenarios. It covers all necessary information for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value beyond schema: explains default events (all), that endpoint must already be in observation set, max webhooks (5), and meaning of liveness_sensitivity_n. This improves understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Start monitoring ONE x402 endpoint for 30 days. Get alerted on changes...' It uses a specific verb (monitor) and resource (x402 endpoint) with a time bound, and distinguishes from siblings like x402_watch_events (polling) and x402_watch_cancel.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description indicates when to use the tool (monitoring for 30 days with alerts) and mentions alternatives (x402_watch_events for polling, push delivery options). However, it does not explicitly state when not to use it or provide clear exclusions, which would elevate the score to 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JonasFuchss/x402-trust-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server