YourAITools MCP Hub

LeakGuard: Find secrets and PII before sending

scan_for_leaks

Read-onlyIdempotent

Check text BEFORE your agent sends it to an LLM, tool, log or webhook: finds crypto wallet keys (BIP39 seed phrases with checksum, EVM/Solana private keys, WIF, xprv), API secrets (GitHub, AWS, Stripe, OpenAI, Anthropic, Slack, Telegram, npm, JWT, PEM) and PII (cards, IBAN, SSN, email, phone). Free preview tier: verdict, safe_to_send and counts by type (text up to 8192 bytes). Redacted text: paid x402 endpoint /v1/lite ($0.005); JSON payloads and live balances of wallets whose keys leaked: /v1/scan ($0.02).

[LeakGuard via YourAITools MCP Hub] Free tier: same as LeakGuard's own MCP server (call without payment and without tier). Paid: lite $0.005 / scan $0.02 per call, with a credits key (Authorization: Bearer yatc_...) or x402 (USDC; the hub returns the payment terms). Failed tool calls aren't charged: credits are refunded automatically and x402 payments only settle on success.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "scan_for_leaks"
  }
}

Input Schema

Name	Required	Description
`json`	No	(paid calls only) Any JSON payload (object, array or value); scanned string by string, keys included
`text`	Yes	Text to check before it is sent (prompt, tool arguments, log, message, file content). POST /v1/scan also accepts {"json": <any JSON payload>}.
`tier`	No	Paid tier: lite $0.005, scan $0.02. Omit tier (with no credits key or x402 payment) to use the free tier.
`style`	No	(paid calls only)
`types`	No	(paid calls only)
`min_severity`	No	(paid calls only)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / text / examples

Added value: +[
+  "Hi, this is Jane Doe (jane.doe@example.com, +1 415 555 0100). Card on file: 4111 1111 1111 1111."
+]

First observedOct 24, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only annotations, the description discloses what the free preview returns, what paid lite and scan tiers return, pricing, payment mechanisms, the free-tier text size limit, and the fact that failed calls are not charged. This is unusually complete behavioral context for an agent deciding whether to call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, leak types, and free/paid behavior. It is verbose and repeats pricing and free-tier information, but the detail is mostly justified by the tiered payment model.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-output-schema scanning tool with a paid/free split, the description covers the key operational facts: detection categories, output differences by tier, limits, pricing, payment options, and failure billing. An agent has enough context to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already defines all six parameters. The description still adds useful meaning by mapping `tier` to outcomes and pricing and by clarifying that free calls operate on text up to 8192 bytes, while JSON payload scanning is paid-only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: check text before it is sent, finding crypto wallet keys, API secrets, and PII. It is clearly narrower than a generic text scanner, but it never explicitly names `scan_text` or another sibling to distinguish itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a clear usage context: before text is sent to an LLM, tool, log, or webhook. It also explains free versus paid tiers, but does not explicitly say when to choose this over nearby siblings such as `scan_text`, `scan_url`, or `scan_tools`.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All YourAITools MCP Hub tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?