io.github.CHANGCHINFU/mcp-gauge

REMOTE · AEML-X402.ZEABUR.APP · SCANNED AUG 3

US government data (USGS/NOAA/SEC/FDA) with cryptographic proof; x402 pay-per-call, no API key

Available components

70 70 Trust /100

Trust breakdown (6 categories)

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 →

Endpoint Security74

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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
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 Usability65

AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 526 tokens (~175/item across 3 items; 3 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 Management13

Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · aeml-x402.zeabur.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http changchinfu-mcp-gauge https://aeml-x402.zeabur.app/mcp

# ~/.codex/config.toml

[mcp_servers.changchinfu-mcp-gauge]
url = "https://aeml-x402.zeabur.app/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "changchinfu-mcp-gauge": {
      "type": "remote",
      "url": "https://aeml-x402.zeabur.app/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add changchinfu-mcp-gauge --url https://aeml-x402.zeabur.app/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  changchinfu-mcp-gauge:
    url: "https://aeml-x402.zeabur.app/mcp"

// mcp.json

{
  "mcpServers": {
    "changchinfu-mcp-gauge": {
      "type": "http",
      "url": "https://aeml-x402.zeabur.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 59

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Probed https://aeml-x402.zeabur.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=aeml-x402.zeabur.app	CN=YE2,O=Let's Encrypt,C=US	6 Jul 2026	4 Oct 2026	ECDSA 256	ECDSA-SHA384	5f5c8673f3af430a96e2918fa00b750c7f5
SANs: aeml-x402.zeabur.app
CN=YE2,O=Let's Encrypt,C=US (CA)	CN=Root YE,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	ECDSA 384	ECDSA-SHA384	4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA)	CN=ISRG Root X2,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	ECDSA-SHA384	872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	ECDSA 384	SHA256-RSA	6c8f1dc727c7117f7baf853ac980f9cd

DNSSEC insecure

Validation of aeml-x402.zeabur.app. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
app.	present	23684	8	Verified
zeabur.app.	absent			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

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://aeml-x402.zeabur.app/mcp	Verified	200
http (plaintext)	http://aeml-x402.zeabur.app/mcp	HTTPS enforced	302	https://aeml-x402.zeabur.app/mcp

MCP tools — 3 exposed · ~453 tokens

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.

Tool Tokens

find_signal Find which signals/entities are covered (free) ~135

FREE coverage + freshness manifest: which signal_id lines exist, how many entities each covers, and fresh/recent/stale counts - so you can check "is my entity covered and how fresh" BEFORE paying. Optional filters: industry, signal_id, entity.

Input Output Examples

Name	Type	Req	Description
entity	string	—	object id, e.g. a USGS site id
full	boolean	—	true = per-entity detail (larger); default compact summary
industry	string	—	restrict to one domain, e.g. hydrology, agriculture, energy
signal_id	string	—	e.g. hydrology.river-level

Name	Type	Req	Description
cache_note	string	—	What the cache does and does not affect.
cache_policy	string	—	Cache policy in force.
cache_ttl_s	number	—	Cache lifetime of this manifest in seconds.
detail	string	—	Present on some failures: the upstream endpoint's own error text.
error	string	—	Present only when the call failed; human-readable reason.
freshness_rule	string	—	How fresh/recent/stale are decided.
freshness_thresholds	object	—	The numeric thresholds behind freshness_rule.
nature	string	—	What this manifest is.
note	string	—	Screening-level disclaimer.
signals	array	—	One entry per signal line. Compact by default; pass full=true for per-entity detail.
totals	object	—	signal_ids / industries / distinct_entities / freshness counts across the whole catalogue.
update_status_rule	object	—	How on_schedule / overdue / not_published / unknown are decided.

No examples provided.

get_official_record Get the x402 payment challenge for a paid record ~211

Returns the REAL x402 payment challenge (accepts[]: network / asset / payTo / amount) for the paid endpoint that serves a given signal_id+entity. This tool does NOT deliver paid data and does NOT take payment - MCP has no payment layer. Pay at the returned url with your own x402 client (USDC on Base or Solana, gasless EIP-3009; pay from a plain EOA) and you receive the record directly, with record_hash you can verify offline. This tool only fetches the 402 challenge; it delivers no paid data and collects no payment.

Input Output Examples

Name	Type	Req	Description
dim	string	—	which product: full read (gauge, $0.05) or a single add-on
entity	string	yes	which object within that line, e.g. the USGS site id 07010000
signal_id	string	yes	which signal line, e.g. hydrology.river-level - use find_signal to list them

Name	Type	Req	Description
after_payment	string	—	What the paid response carries and how to verify it offline.
detail	string	—	Present on some failures: the upstream endpoint's own error text.
error	string	—	Present only when the call failed; human-readable reason.
expected	string	—	Present on failure: what was expected (an HTTP 402 challenge).
got	integer	—	Present on failure: the HTTP status actually returned.
hint	string	—	Present on failure: the next thing to try, e.g. find_signal.
how_to_pay	string	—	How to sign and send the X-PAYMENT header; pay from a plain EOA.
method	string	—	HTTP method to use at pay_at (always GET).
note	string	—	Standing statement that this server never takes payment.
pay_at	string	—	URL to send the paid GET to.
x402_challenge	object	—	The upstream 402 body verbatim: x402Version + accepts[] (scheme / network / asset / payTo / amount).

No examples provided.

verify_citation Verify a Truth Bear record (free) ~107

FREE. Given a record_hash from any Truth Bear record, look it up and recompute the canonical hash server-side, returning whether it is a genuine Truth Bear official record plus a plain-language reverse lookup of what exactly that hash attests. Use this to check a citation you were handed by another agent or document BEFORE relying on it. No payment, no API key.

Input Output Examples

Name	Type	Req	Description
record_hash	string	yes	sha256:<64 hex>, or a >=8-hex prefix as posted publicly

Name	Type	Req	Description
endpoint	string	—	Always "gauge/verify".
entity	string\|null	—	Object id the reading is about.
error	string	—	Present only when the call failed; human-readable reason.
found	boolean	—	Whether a published Truth Bear reading matches this hash.
hash_core_version	integer\|null	—	Version of the canonical hash core used.
how_to_check_a_claimed_value	string	—	Present when found: how to check a value someone claims.
is_truth_bear_record	boolean\|null	—	true / false, or null when the check could not be run (see undetermined).
note	string	—	Screening-level disclaimer.
ots_status	string\|null	—	Legacy compatibility field; external timestamp anchoring was ruled out of implementation on 2026-07-23, so this stays "pending" forever.
recomputed_hash	string\|null	—	sha256:<64 hex> recomputed from the stored record.
reverse_lookup	string	—	Plain-language statement of exactly what this hash attests.
scope	string	—	What this hash does and does not attest.
signal_id	string\|null	—	e.g. hydrology.river-level
snapshot_date	string\|null	—	YYYY-MM-DD of the reading.
source_ref	string\|null	—	URL of the official source record.
undetermined	boolean	—	true when the lookup itself failed (e.g. DB unavailable) - NOT a verdict of "fake".
verified	boolean	—	Whether the canonical hash recomputed server-side matches the one supplied.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

30 Jul 3 Aug