FabTally Guard
Related Servers
Alternatives to FabTally Guard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for AI agent security guardrails. Provides input validation, prompt injection detection, PII redaction, output filtering, policy enforcement, rate limiting, and comprehensive audit logging.45 npm1MIT
- AlicenseAqualityAmaintenanceAn MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.3053 PyPI2MIT
- AlicenseAqualityAmaintenanceMCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access31MIT
- AlicenseBqualityDmaintenanceAn MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.1789 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA drop-in proxy that guards MCP servers with policy enforcement, secret redaction, prompt-injection screening, rug-pull detection, rate limiting, and audit logging.6 npmApache 2.0
- AlicenseBqualityCmaintenanceSecurity gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.5696 npm10MIT
TDQS
Scored across 4 tools
Each tool targets a completely different function: dependency vetting, x402 endpoint verification, JSON repair, and URL reading. There is no overlap or potential for confusion between them.
All tool names follow the same lower_snake_case pattern with an object followed by a verb: deps_check, x402_preflight, json_repair, url_read. The convention is uniform and predictable.
With four tools, the server is well-scoped for its purpose. Each tool provides a distinct utility without redundancy, making the set feel intentional and complete.
The tool surface covers a coherent set of guardrail functions: vetting packages, validating payment endpoints, repairing LLM JSON output, and sanitizing URLs for ingestion. There are no obvious missing operations for this domain.