Home / MCP registry index / io.github.SecondShotAI/verifylite

VerifyLite

io.github.SecondShotAI/verifylite in the official MCP registry. Endpoint https://verifylite.hydratinghealingtouch.workers.dev/mcp.

The registry describes it as: Pay-per-call website safety and URL checks for AI agents. USDC on Base via x402, no API keys.

We read its 34 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http verifylite https://verifylite.hydratinghealingtouch.workers.dev/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "verifylite": {
      "url": "https://verifylite.hydratinghealingtouch.workers.dev/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"verifylite","type":"http","url":"https://verifylite.hydratinghealingtouch.workers.dev/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_prices verify_url check_site_safety check_site_safety_pro check_sites_batch transcribe_audio read_page link_preview domain_report check_email seo_check chain_balance chain_tx chain_token chain_contract chain_gas chain_block token_safety_check token_allowance_check wallet_transfers contract_events token_holders nft_lookup contract_call name_lookup crypto_price check_prompt_injection repair_json read_feed get_time new_uuid random_number ip_info ping

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-secondshotai-verifylite/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-secondshotai-verifylite)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26