Home / MCP registry index / io.skimguard/skimguard

io.skimguard/skimguard

io.skimguard/skimguard in the official MCP registry. Endpoint https://mcp.skimguard.io/mcp.

The registry describes it as: Ask whether a location has recent credit-card-skimmer detections, from a consumer sensor network.

We read its 17 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 skimguard https://mcp.skimguard.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "skimguard": {
      "url": "https://mcp.skimguard.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"skimguard","type":"http","url":"https://mcp.skimguard.io/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

skimguard_get_location_status skimguard_find_nearby_activity skimguard_lookup_bluetooth_manufacturer skimguard_search_locations skimguard_route_risk skimguard_coverage_stats skimguard_about skimguard_my_locations skimguard_my_stale_locations skimguard_location_devices skimguard_my_scanner_health skimguard_my_merchants skimguard_my_earnings skimguard_regional_risk skimguard_device_prevalence skimguard_inspection_stats skimguard_training_stats

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

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

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.