Connect FabTally Guard and your agent gets 4 tools, among them deps_check, json_repair, url_read. It answers at https://guard.fabtally.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.
Verify before you act: deps-check, x402-preflight, json-repair & url-read for agents.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
deps_check | 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 Inputs: ecosystem, name, version, x_payment |
json_repair | 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 default Inputs: json, schema, x_payment |
url_read | 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 sto Inputs: url, x_payment |
x402_preflight | 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 reach Inputs: url, x_payment |
Every block below points at https://guard.fabtally.com/mcp. Pick your client and copy.
claude mcp add --transport http fabtally-guard https://guard.fabtally.com/mcp
{
"mcpServers": {
"fabtally-guard": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://guard.fabtally.com/mcp"]
}
}
}{
"mcpServers": {
"fabtally-guard": {
"url": "https://guard.fabtally.com/mcp"
}
}
}{
"servers": {
"fabtally-guard": {
"type": "http",
"url": "https://guard.fabtally.com/mcp"
}
}
}{
"context_servers": {
"fabtally-guard": {
"url": "https://guard.fabtally.com/mcp"
}
}
}{
"mcpServers": {
"fabtally-guard": {
"serverUrl": "https://guard.fabtally.com/mcp"
}
}
}{
"mcpServers": {
"fabtally-guard": {
"url": "https://guard.fabtally.com/mcp"
}
}
}name: FabTally Guard
version: 0.0.1
schema: v1
mcpServers:
- name: FabTally Guard
type: streamable-http
url: https://guard.fabtally.com/mcp{
"mcpServers": {
"fabtally-guard": {
"httpUrl": "https://guard.fabtally.com/mcp"
}
}
}{
"mcpServers": {
"fabtally-guard": {
"type": "http",
"url": "https://guard.fabtally.com/mcp"
}
}
}{
"mcpServers": {
"fabtally-guard": {
"url": "https://guard.fabtally.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fguard.fabtally.com%2Fmcp&type=streamable_http&id=fabtally-guard&name=FabTally%20Guard
It answered our last check on 24 October 2026 in 119 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
4, as returned by the server's own tools/list on 22 September 2026: deps_check, json_repair, url_read, x402_preflight.
It answered our last check on 24 October 2026 in 119 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://guard.fabtally.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.zvmzaretsky. Endpoint host: guard.fabtally.com. ARD identifier: urn:air:io.github.zvmzaretsky:mcp:fabtally-guard.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.