# LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue Engine (remote · locatepic.com)

Analyze solar shadow angles, country road/phone clues & EXIF privacy rules for photo geolocation.

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

## Components

- remote · `locatepic.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-locatepic-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-locatepic-mcp/api-mcp)

## Channel facts

- Endpoint: `https://locatepic.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 581 tokens (~72/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server?

LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… is a hosted endpoint at https://locatepic.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-locatepic-mcp 'https://locatepic.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-locatepic-mcp": {
      "url": "https://locatepic.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-locatepic-mcp": {
      "type": "http",
      "url": "https://locatepic.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-locatepic-mcp]
url = "https://locatepic.com/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-locatepic-mcp --url 'https://locatepic.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-locatepic-mcp:
    url: "https://locatepic.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-locatepic-mcp": {
      "Transport": "http",
      "Url": "https://locatepic.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-locatepic-mcp -t streamable-http -u 'https://locatepic.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-locatepic-mcp": {
      "type": "http",
      "url": "https://locatepic.com/api/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-11-21 (score 75, +1)

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

### 2026-11-19 (score 74, +1)

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

### 2026-11-17 (score 73, +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-11-15 (score 72, +1)

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

### 2026-11-13 (score 71, +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-11-11 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-11-10 (score 69)

First indexed and scored.

## MCP tools (8)

### `calculate_solar_shadow_latitude` (~95 tokens)

Solar Shadow Azimuth & Latitude Estimator

Estimate approximate latitude band and hemisphere from object height, shadow length, and UTC capture timestamp for visual photo verification.

Input parameters:

- `month` (integer): Capture month (1-12)
- `objectHeightMeters` (number, required): Vertical height of reference object in meters (e.g. 2.0)
- `shadowLengthMeters` (number, required): Measured ground shadow length in meters (e.g. 1.73)

### `lookup_driving_side_and_road_lines` (~74 tokens)

Country Driving Side & Road Marking Clue Lookup

Look up left-hand vs right-hand traffic rules, center line colors (yellow vs white), and bollard styles by country or region.

Input parameters:

- `countryOrRegion` (string, required): Country name or ISO code (e.g. "Japan", "Australia", "United States", "UK", "Germany")

### `lookup_country_calling_and_domain_clues` (~84 tokens)

Signage Phone Dialing Code & ccTLD Clue Resolver

Identify the country from storefront phone dialing prefixes (+1 to +998) or country-code top-level domain (.de, .jp, .za, .br) visible in street photos.

Input parameters:

- `code` (string, required): Dialing prefix (e.g. "+48", "+81") or ccTLD (e.g. ".ch", ".kr")

### `inspect_exif_gps_tag_reference` (~52 tokens)

EXIF GPS & Camera Metadata Tag Privacy Reference

Check which EXIF/XMP/IPTC tags leak exact GPS coordinates, altitude, compass bearing, and device serial numbers before sharing images online.

Input parameters:

- `fileFormat` (string, required): Image container format

### `classify_six_dimension_osint_clues` (~59 tokens)

6-Dimension Visual Geolocation Clue Checklist

Generate a structured 6-dimension visual geolocation inspection checklist (celestial shadows, road infrastructure, utility poles, architecture, flora, scripts) for an unidentified outdoor photo.

Input parameters:

- `environment` (string, required): Primary scene environment

### `check_social_platform_exif_stripping` (~74 tokens)

Social Media EXIF Metadata Stripping Behavior Lookup

Verify whether major platforms (X/Twitter, Instagram, Reddit, Discord, WhatsApp, Email, Google Drive) strip or preserve embedded GPS EXIF data upon upload.

Input parameters:

- `platform` (string, required): Platform name (e.g. "Discord", "WhatsApp Document", "Instagram", "Email Attachment")

### `convert_dms_decimal_coordinates` (~73 tokens)

DMS to Decimal GPS Coordinate & Plus Code Converter

Convert EXIF Degrees-Minutes-Seconds (DMS) rational GPS tuples into standard WGS84 decimal latitude and longitude coordinates.

Input parameters:

- `dmsString` (string, required): DMS string (e.g. "37°20'19.7\"N 121°53'29.8\"W")

### `get_geolocation_case_study_methodology` (~70 tokens)

Verified Visual Geolocation Case Study & Triangulation Guide

Retrieve step-by-step triangulation methodology from verified LocatePic visual forensics case studies (viaduct skyline geometry, desert road roll-fit, urban botany).

Input parameters:

- `topic` (string, required): Case topic (e.g. "skyline", "highway", "botany")

## Diagnostics

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

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 73
- 2026-11-17: 73
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69

## Common questions

### What is the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server?

LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… is an MCP server listed in the public MCP registry as com.locatepic/mcp. Analyze solar shadow angles, country road/phone clues & EXIF privacy rules for photo geolocation. This page covers its hosted endpoint (https://locatepic.com/api/mcp).

### Is the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server safe to use?

LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server expose?

LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… exposes 8 tools: calculate_solar_shadow_latitude, lookup_driving_side_and_road_lines, lookup_country_calling_and_domain_clues, inspect_exif_gps_tag_reference, classify_six_dimension_osint_clues, and 3 more. Their descriptions and schemas cost roughly 581 tokens of context every time the server is loaded.

### Does the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server require authentication?

No. We connected to LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server still maintained?

LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue… MCP server?

VerifyMCP ran 13 checks on LocatePic — Photo Geolocation, Solar Shadow & OSINT Clue…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://locatepic.com/api/mcp
- Repository: https://github.com/AbigailDavised/locatepic-mcp
- Website: https://locatepic.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-locatepic-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-locatepic-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-locatepic-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-locatepic-mcp/api-mcp
