FabTally Guard
REMOTE · GUARD.FABTALLY.COM · SCANNED AUG 3
Verify before you act: deps-check, x402-preflight, json-repair & url-read for agents.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 791 tokens (~197/item across 4 items; 4 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 Management7
- Stability observed for 2 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · guard.fabtally.com
claude mcp add --transport http zvmzaretsky-fabtally-guard https://guard.fabtally.com/mcp
[mcp_servers.zvmzaretsky-fabtally-guard] url = "https://guard.fabtally.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zvmzaretsky-fabtally-guard": {
"type": "remote",
"url": "https://guard.fabtally.com/mcp",
"enabled": true
}
}
} openclaw mcp add zvmzaretsky-fabtally-guard --url https://guard.fabtally.com/mcp --transport streamable-http
mcp_servers:
zvmzaretsky-fabtally-guard:
url: "https://guard.fabtally.com/mcp" {
"mcpServers": {
"zvmzaretsky-fabtally-guard": {
"type": "http",
"url": "https://guard.fabtally.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 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.
- 2 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Aug 26 60
First indexed and scored.
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://guard.fabtally.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=guard.fabtally.com | CN=YR1,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | RSA 2048 | SHA256-RSA | 5e0036d3c94e1791c16348cba08db418767 |
| SANs: guard.fabtally.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of guard.fabtally.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fabtally.com. | 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://guard.fabtally.com/mcp | Verified | 200 | |
| http (plaintext) | http://guard.fabtally.com/mcp | HTTPS enforced | 301 | https://guard.fabtally.com/mcp |
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.
deps_check Vet a dependency before install (paid $0.003) ~225
PAID $0.003 (x402, USDC on Base). Vet a software package BEFORE installing it. Returns existence, latest-vs-requested, deprecation/yank markers, known CVEs from OSV.dev, typosquat similarity to popular names, SPDX license, and age/download signals with a plain-English risk verdict. Args: ecosystem (npm|pypi|crates), name, version (optional). Without payment returns the x402 challenge; pass x_payment to settle.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem: npm | pypi | crates. |
| name | string | yes | Package name, e.g. 'lodash', 'requests', 'serde'. |
| version | string | — | Specific version to check for CVEs (optional; defaults to latest). |
| x_payment | string | — | x402 payment payload (base64) for this PAID check. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price… |
No output schema declared.
No examples provided.
json_repair Repair near-miss LLM JSON to a schema (paid $0.002) ~211
PAID $0.002 (x402, USDC on Base). Coerce near-miss LLM JSON to a JSON-Schema-conformant object: strip code fences/prose, fix trailing commas/quotes/unquoted keys, normalise Python literals, balance brackets, then coerce types, apply defaults, and drop extraneous keys. Returns the repaired object OR precise per-field errors. Args: json (the raw string), schema (a JSON Schema object). Without payment returns the x402 challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| json | string | yes | The raw, possibly-malformed JSON text to repair. |
| schema | object | yes | A JSON Schema (draft 2020-12) object the result must conform to. |
| x_payment | string | — | x402 payment payload (base64) for this PAID check. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price… |
No output schema declared.
No examples provided.
url_read Public url -> clean Markdown + token count (paid $0.004) ~159
PAID $0.004 (x402, USDC on Base). Fetch a PUBLIC url and return clean Markdown + a token estimate for RAG ingestion — readability extraction, boilerplate stripped. Respects robots.txt, public pages only, no login/paywall bypass, nothing stored. Args: url. Without payment returns the x402 challenge; pass x_payment to settle.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The public web page URL to fetch and convert to Markdown. |
| x_payment | string | — | x402 payment payload (base64) for this PAID check. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price… |
No output schema declared.
No examples provided.
x402_preflight Verify an x402 endpoint before paying (paid $0.002) ~196
PAID $0.002 (x402, USDC on Base). Verify another x402 endpoint BEFORE paying it: does an unpaid call return a valid x402 v2 402 challenge? do the quoted amount/asset/network/payTo match the site's /.well-known/x402? is TLS valid, host reachable, openapi present? Returns pass/fail + per-check reasons + the parsed price you would pay. Args: url. Without payment returns the x402 challenge; pass x_payment to settle.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The x402 endpoint URL to verify, e.g. https://example.com/v1/thing. |
| x_payment | string | — | x402 payment payload (base64) for this PAID check. If supplied it is forwarded as the X-PAYMENT header to settle the call and return the real result instead of a 402 challenge. Omit to get the price… |
No output schema declared.
No examples provided.