FluxProof
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fluxproof_preflightA | Fetch a public URL and return fetchability, size, final URL, title, and content hash without page content or payment. How it works: given one public page address, FluxProof fetches it once and says whether it can watch it; nothing is created or charged. Example: {"url":"https://example.com/"}. |
| fluxproof_get_free_keyA | Create a free FluxProof API key: one page, checked daily, for 30 days, no card. One per network per month. The key is returned once and is a secret credential. |
| fluxproof_offerA | Return free and paid boundaries and purchase routes without charging. Returns the free daily plan, the $9 paid pass, the human checkout link and the agent payment route. Example: {}. Reading the offer charges nothing. |
| fluxproof_create_monitorA | Create a monitor using a buyer-owned FluxProof API key. Creates persistent state and performs a baseline check, consuming quota. Not idempotent: each call creates a new monitor. |
| fluxproof_check_nowA | Run a monitor now and return a source- and hash-bound change receipt. Consumes check quota, stores a receipt and may deliver a configured webhook. Not an idempotent read. |
| fluxproof_list_changesC | List recent evidence receipts for a monitor. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct role: preflight checks fetchability without charge, offer returns pricing, get_free_key issues a credential, create_monitor sets up state, check_now runs a check, and list_changes reads receipts. There is mild conceptual overlap between preflight and check_now (both fetch a page), but descriptions clarify that only check_now consumes quota and persists state.
All tools share the fluxproof_ prefix and mostly use a verb_noun pattern (get_free_key, create_monitor, check_now, list_changes). The two outliers, preflight and offer, are bare nouns/verbs that break the pattern slightly but remain readable and unambiguous.
Six tools is a well-scoped set for a URL-change monitoring service covering onboarding, payment info, and monitor lifecycle basics. It is on the lean side but every tool earns its place with no filler.
The surface covers key acquisition, offer discovery, fetchability pre-check, monitor creation, checking, and receipt listing. However, there is no way to list monitors, get monitor details, update, or delete a monitor, so the lifecycle is only partially closed and agents will hit dead ends when managing existing monitors.