FluxProof
REMOTE · FLUXPROOF.STEELLANTERN.COM
Evidence-bearing public webpage monitoring with hashes, diffs, signed webhooks, REST, and MCP.
Available components
Last scanned (15 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Monitoring and Observability
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 820 tokens (~136/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 0
- Tool “fluxproof_get_free_key” rewrote its description, which is the text the model reads security
- 30 Oct 26 0
- “fluxproof_create_monitor” reworded the description of “url” cosmetic
- “fluxproof_preflight” reworded the description of “url” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 29 Oct 26 −1
- Schema quality: pass → fail ▼ functional
- “fluxproof_create_monitor” added an optional parameter “part” cosmetic
- “fluxproof_create_monitor” added an optional parameter “alert_when” cosmetic
- 27 Oct 26 0
- Tool “fluxproof_offer” rewrote its description, which is the text the model reads security
- “fluxproof_create_monitor” reworded the description of “webhook_url” cosmetic
- 13 Oct 26 −1
- Tool “fluxproof_create_monitor” rewrote its description, which is the text the model reads security
- Tool “fluxproof_get_free_key” rewrote its description, which is the text the model reads security
- Tool “fluxproof_offer” rewrote its description, which is the text the model reads security
- Tool “fluxproof_preflight” rewrote its description, which is the text the model reads security
- “fluxproof_check_now” reworded the description of “api_key” cosmetic
- “fluxproof_create_monitor” reworded the description of “api_key” cosmetic
- “fluxproof_create_monitor” reworded the description of “url” cosmetic
- “fluxproof_list_changes” reworded the description of “api_key” cosmetic
- “fluxproof_preflight” reworded the description of “url” cosmetic
- 11 Oct 26 0
- Tool “fluxproof_offer” changed its title: Show plans and prices cosmetic
- Tool “fluxproof_preflight” changed its title: Check a public page (free) cosmetic
- Tool “fluxproof_check_now” changed its title: Check a watched page now cosmetic
- Tool “fluxproof_create_monitor” changed its title: Start watching a page cosmetic
- Tool “fluxproof_get_free_key” changed its title: Get a free API key cosmetic
- Tool “fluxproof_list_changes” changed its title: List recorded changes cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 10 Oct 26 +1
- Stability: 0.93 → pass security
- Schema quality: 539 → 620 ▼ functional
- New tool “fluxproof_get_free_key” functional
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 6 Nov 2026 · Probed https://fluxproof.steellantern.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=steellantern.com | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1d2d18a9345e680d0e3c3d8852703baa |
| SANs: steellantern.com, fluxproof.steellantern.com, *.fluxproof.steellantern.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 fluxproof.steellantern.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| steellantern.com. | No DS | 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=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fluxproof.steellantern.com/mcp | Verified | 200 | |
| http (plaintext) | http://fluxproof.steellantern.com/mcp | Inconclusive | 405 |
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 →
fluxproof_check_now Check a watched page now ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Buyer-owned FluxProof API key; a secret credential. |
| monitor_id | string | yes | Exact monitor_id returned when this key created the monitor; another account cannot access it. |
No output schema declared.
No examples provided.
fluxproof_create_monitor Start watching a page ~373
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_when | object | – | Optional conditions on the watched part: contains (alert when this text appears) and/or missing (alert when this text disappears), 2–120 characters each. A condition that becomes true is a high-signi… |
| api_key | string | – | Buyer-owned FluxProof API key; a secret credential. |
| interval_minutes | integer | – | Requested schedule in minutes. Free keys use 1440 (daily); paid passes have a 15-minute minimum. |
| label | string | – | Optional human-readable monitor label, up to 120 characters. |
| part | object | – | Optional: watch only part of the page. start is text on the first line of the part (2–120 characters, any case); end is text on its last line, or lines (1–200, default 20) sets its length. Only that… |
| url | string | yes | Required: the full address of one public web page, for example https://example.com/ or https://store.example.com/products/item; a bare domain such as example.com also works. Not a search phrase, prod… |
| watch_terms | array | – | Optional terms to track, each 2–80 characters; at most 20 distinct terms. |
| webhook_url | string | – | Optional public HTTPS webhook receiver; paid pass required. Delivery is signed and can occur when checks run. A Slack or Discord incoming-webhook address gets a readable chat message instead of the J… |
No output schema declared.
No examples provided.
fluxproof_get_free_key Get a free API key ~55
Create a free FluxProof API key: one page, checked daily, for 30 days, no card. One per internet connection (IP address) per month. The key is returned once and is a secret credential.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fluxproof_list_changes List recorded changes ~86
List recent evidence receipts for a monitor.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | Buyer-owned FluxProof API key; a secret credential. |
| limit | integer | – | Maximum recent receipts requested; defaults to 20. History access is restricted by the key’s plan. |
| monitor_id | string | yes | Exact monitor_id returned when this key created the monitor; another account cannot access it. |
No output schema declared.
No examples provided.
fluxproof_offer Show plans and prices ~74
Return free and paid boundaries and purchase routes without charging. Returns the free daily plan, the $9 paid pass (30 days paid once; when offered, also $9 a month through the human checkout, cancel any time), the human checkout link and the agent payment route. Example: {}. Reading the offer charges nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fluxproof_preflight Check a public page (free) ~143
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/"}.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Required: the full address of one public web page, for example https://example.com/ or https://store.example.com/products/item; a bare domain such as example.com also works. Not a search phrase, prod… |
No output schema declared.
No examples provided.
How do I install the FluxProof MCP server?
FluxProof is a hosted endpoint at https://fluxproof.steellantern.com/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 · fluxproof.steellantern.com
claude mcp add --transport http equinoxaifinance-rgb-fluxproof 'https://fluxproof.steellantern.com/mcp'
What is the FluxProof MCP server?
FluxProof is an MCP server listed in the public MCP registry as io.github.equinoxaifinance-rgb/fluxproof. Evidence-bearing public webpage monitoring with hashes, diffs, signed webhooks, REST, and MCP. This page covers its hosted endpoint (https://fluxproof.steellantern.com/mcp).
Is the FluxProof MCP server safe to use?
FluxProof scores 81 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 FluxProof MCP server expose?
FluxProof exposes 6 tools: fluxproof_preflight, fluxproof_get_free_key, fluxproof_offer, fluxproof_create_monitor, fluxproof_check_now, fluxproof_list_changes. Their descriptions and schemas cost roughly 820 tokens of context every time the server is loaded.
Does the FluxProof MCP server require authentication?
No. We connected to FluxProof without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FluxProof MCP server still maintained?
FluxProof is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the FluxProof MCP server?
VerifyMCP ran 12 checks on FluxProof, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about FluxProof: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.