# io.skimguard/skimguard (remote · mcp.skimguard.io)

Ask whether a location has recent credit-card-skimmer detections, from a consumer sensor network.

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-13

## Components

- remote · `mcp.skimguard.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-skimguard-skimguard/mcp.md), [page](https://verifymcp.io/servers/io-skimguard-skimguard/mcp)

## Channel facts

- Endpoint: `https://mcp.skimguard.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-13.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2127 tokens (~118/item across 18 items; 17 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 83% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-skimguard-skimguard https://mcp.skimguard.io/mcp
```

### Codex

```toml
[mcp_servers.io-skimguard-skimguard]
url = "https://mcp.skimguard.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-skimguard-skimguard": {
      "type": "remote",
      "url": "https://mcp.skimguard.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-skimguard-skimguard --url https://mcp.skimguard.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-skimguard-skimguard:
    url: "https://mcp.skimguard.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-skimguard-skimguard": {
      "type": "http",
      "url": "https://mcp.skimguard.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-13 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-11 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-08-09 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-07 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-06 (score 73)

First indexed and scored.

## MCP tools (17)

### `skimguard_get_location_status` (~237 tokens)

Get Location Safety Status

Look up SkimGuard card-skimmer scan status for a location by its Google Place ID. Returns how recently the location was scanned, how many scans it has, and whether any suspicious Bluetooth devices were detected. Use this to answer "is this gas station / ATM / store safe to use my card at?". Returns "not publicly tracked" for locations with no public scan data (including private residences, which are deliberately excluded). Side effect: if the Place ID is one SkimGuard has never seen, it is added to SkimGuard's own public location registry so the next nearby scan can attach to it. That writes to SkimGuard data only — never anything you or the user own — so this tool is read-only from the caller's perspective.

Input parameters:

- `days` (integer): Lookback window in days (1-365, default 30)
- `placeId` (string, required): Google Place ID, e.g. ChIJN1t_tDeuEmsRUsoyG83frY4
- `response_format` (string): Response format: 'markdown' (default) or 'json'

### `skimguard_find_nearby_activity` (~143 tokens)

Find Nearby Scan Activity

Find locations near a latitude/longitude that SkimGuard users have scanned recently, with suspicious-detection counts. Use for "any skimmers reported near me?". Only publicly visible locations are returned; private residences are excluded.

Input parameters:

- `days` (integer): Lookback window in days (1-365, default 30)
- `latitude` (number, required)
- `limit` (integer)
- `longitude` (number, required)
- `radius_meters` (integer): Search radius in meters (50-50000, default 2000)
- `response_format` (string): Response format: 'markdown' (default) or 'json'

### `skimguard_lookup_bluetooth_manufacturer` (~99 tokens)

Look Up Bluetooth Manufacturer

Resolve a Bluetooth SIG company identifier to a manufacturer name and SkimGuard risk rating. Accepts decimal (76) or hex (0x004C). Useful for explaining what a device seen in a scan actually is.

Input parameters:

- `company_code` (string, required): BT SIG company identifier, decimal or 0x-hex
- `response_format` (string): Response format: 'markdown' (default) or 'json'

### `skimguard_search_locations` (~219 tokens)

Search Locations by Name

Find a location by NAME or address (e.g. "Shell on Riverside, Austin TX", "Chase ATM near Union Square") and get its SkimGuard card-skimmer scan status. Use this when you know what a place is called but do not have its Google Place ID — it resolves the name first, then reports scan status for each match. Pass latitude/longitude when you know roughly where the user is; it sharply improves matching for common brand names. Locations with no scan data are reported as unknown, never as unsafe.

Input parameters:

- `days` (integer): Lookback window in days (1-365, default 30)
- `latitude` (number): Optional bias — the user's approximate latitude
- `limit` (integer)
- `longitude` (number): Optional bias — the user's approximate longitude
- `query` (string, required): Place name and ideally a city, e.g. "Shell gas station Riverside Austin TX"
- `response_format` (string): Response format: 'markdown' (default) or 'json'

### `skimguard_route_risk` (~275 tokens)

Check Risk Along a Route

Given a series of route points, report locations along that stretch of road with recent suspicious activity or stale scan coverage. IMPORTANT: this checks the road AHEAD, not a whole trip — at most 20 km of the supplied route is examined, and the response says how much was actually checked (examinedMeters / truncated). For accurate results pass real route geometry from a directions provider; passing only a start and end point checks a straight line between them, which will not follow the actual road. TO COVER A LONGER TRIP: split the route geometry into consecutive 20 km segments and call this tool once per segment, then combine the results — that is the supported way to check a full drive. A 500 km trip is about 25 calls, which fits inside the anonymous rate limit. Do NOT report a route as clear unless you have covered all of it this way; say which portion you checked.

Input parameters:

- `corridor_meters` (integer): How far either side of the route to look (10-200 m)
- `lookahead_meters` (integer): How far along the route to look (max 20 km)
- `polyline` (array, required): Ordered route points, start first
- `response_format` (string): Response format: 'markdown' (default) or 'json'

### `skimguard_coverage_stats` (~84 tokens)

SkimGuard Coverage Statistics

Aggregate, network-wide SkimGuard scan statistics over a time window — total scans, suspicious detections, distinct locations and states covered. No identifying data.

Input parameters:

- `days` (integer): Lookback window in days (1-365, default 30)
- `response_format` (string): Response format: 'markdown' (default) or 'json'

### `skimguard_about` (~49 tokens)

About SkimGuard

Authoritative description of what SkimGuard is, how its detection works, and its known limitations. Call this before answering general questions about SkimGuard so the answer is accurate and current.

### `skimguard_my_locations` (~100 tokens)

Business tier — sign in required

Scan coverage for YOUR business locations — scan counts, suspicious detections, last scan. REQUIRES the SkimGuard Business tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_my_stale_locations` (~96 tokens)

Business tier — sign in required

Which of YOUR business locations are overdue for a scan. REQUIRES the SkimGuard Business tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_location_devices` (~93 tokens)

Business tier — sign in required

Bluetooth devices seen at one of YOUR business locations. REQUIRES the SkimGuard Business tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_my_scanner_health` (~96 tokens)

Business tier — sign in required

Whether YOUR SkimGuard scanners are online and reporting. REQUIRES the SkimGuard Business tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_my_merchants` (~94 tokens)

Partner tier — sign in required

Scan activity for merchants attributed to YOUR reseller account. REQUIRES the SkimGuard Partner tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_my_earnings` (~98 tokens)

Partner tier — sign in required

YOUR commission totals and payout status as a SkimGuard reseller. REQUIRES the SkimGuard Partner tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_regional_risk` (~100 tokens)

Data Licensee tier — sign in required

Aggregate skimmer risk by US state (Data Licensee tier). REQUIRES the SkimGuard Data Licensee tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_device_prevalence` (~99 tokens)

Data Licensee tier — sign in required

Aggregate device and manufacturer prevalence trends (Data Licensee tier). REQUIRES the SkimGuard Data Licensee tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_inspection_stats` (~117 tokens)

Data Licensee tier — sign in required

Aggregate PCI POI device-inspection compliance trends — pass/fail, tamper-incident, and tamper-check failure rates (Data Licensee tier). REQUIRES the SkimGuard Data Licensee tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

### `skimguard_training_stats` (~108 tokens)

Data Licensee tier — sign in required

Aggregate PCI staff-training coverage trends — completion, pass rate, delivery mix, and expiry (Data Licensee tier). REQUIRES the SkimGuard Data Licensee tier. You are not signed in to an account with it. Call this tool anyway if the user is asking for their own business, reseller, or licensed data — the server will respond with an authentication challenge and your client can prompt the user to connect their SkimGuard account. Do not fabricate an answer instead.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-skimguard-skimguard/mcp#diagnostics

## Score history

- 2026-08-13: 77
- 2026-08-12: 76
- 2026-08-11: 76
- 2026-08-10: 75
- 2026-08-09: 75
- 2026-08-08: 74
- 2026-08-07: 74
- 2026-08-06: 73

## Links

- Remote endpoint: https://mcp.skimguard.io/mcp
- Website: https://skimguard.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-skimguard-skimguard/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-skimguard-skimguard/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-skimguard-skimguard/mcp