Skip to main content
Glama
Sign In

VerifyLite

by io.github.SecondShotAI
OverviewDiscussionsAdmin

Website safety check with malware/phishing blocklist

check_site_safety_pro
Read-only

Website safety check plus a Google Web Risk lookup for malware, phishing, and unwanted software. Includes the full /safe report: verdict (safe, caution, unsafe), 0-100 score, TLS, redirects, security headers, mixed content, insecure forms, and domain age. A blocklist hit makes the verdict unsafe. Useful for screening links before a payment, login, or download. Not charged if the blocklist cannot be reached. Paid via x402; see list_prices.

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": {
      "url": "<url>"
    },
    "name": "check_site_safety_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute HTTP or HTTPS URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already mark read-only and open-world; the description adds key behavior: a Google Web Risk blocklist hit forces an unsafe verdict, no charge when the blocklist is unreachable, and x402 payment via list_prices. It does not cover auth/permissions or rate limits, but adds meaningful billing and verdict logic.

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

Conciseness5/5

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

Front-loads the core operation, then lists report outputs, usage scenario, and billing caveat; each sentence carries distinct information. There is no repetition or filler.

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

Completeness4/5

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

No output schema exists, so the description usefully summarizes verdict/score/TLS/redirects/headers and billing behavior. It leaves sibling selection implicit, but otherwise supplies enough to call the tool correctly.

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

Parameters3/5

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

Schema coverage is 100% and the single url parameter is documented as an absolute HTTP/HTTPS URL, so the description needn't re-specify it. The description only implies link input and adds no format or validation detail beyond the schema.

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?

Names a specific operation: website safety check plus Google Web Risk blocklist lookup, and enumerates the full report fields. The 'plus'/'full report' phrasing distinguishes it from the basic sibling, though it never names check_site_safety or check_sites_batch explicitly.

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?

Gives a concrete use case: screening links before payment, login, or download, and points to list_prices for paid access. It does not state when to choose check_site_safety or check_sites_batch instead, so exclusions/alternatives are absent.

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

All VerifyLite toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources