Analyze solar shadow angles, country road/phone clues & EXIF privacy rules for photo geolocation.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Estimate approximate latitude band and hemisphere from object height, shadow length, and UTC capture timestamp for visual photo verification.
Vertical height of reference object in meters (e.g. 2.0)
Measured ground shadow length in meters (e.g. 1.73)
Capture month (1-12)
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http mcp https://locatepic.com/api/mcp
Estimate approximate latitude band and hemisphere from object height, shadow length, and UTC capture timestamp for visual photo verification.
| Argument | Type | Description |
|---|---|---|
| month | integer | Capture month (1-12) |
| objectHeightMeters* | number | Vertical height of reference object in meters (e.g. 2.0) |
| shadowLengthMeters* | number | Measured ground shadow length in meters (e.g. 1.73) |
{
"type": "object",
"required": [
"objectHeightMeters",
"shadowLengthMeters"
],
"properties": {
"month": {
"type": "integer",
"description": "Capture month (1-12)"
},
"objectHeightMeters": {
"type": "number",
"description": "Vertical height of reference object in meters (e.g. 2.0)"
},
"shadowLengthMeters": {
"type": "number",
"description": "Measured ground shadow length in meters (e.g. 1.73)"
}
}
}Verify whether major platforms (X/Twitter, Instagram, Reddit, Discord, WhatsApp, Email, Google Drive) strip or preserve embedded GPS EXIF data upon upload.
| Argument | Type | Description |
|---|---|---|
| platform* | string | Platform name (e.g. "Discord", "WhatsApp Document", "Instagram", "Email Attachment") |
{
"type": "object",
"required": [
"platform"
],
"properties": {
"platform": {
"type": "string",
"description": "Platform name (e.g. \"Discord\", \"WhatsApp Document\", \"Instagram\", \"Email Attachment\")"
}
}
}Generate a structured 6-dimension visual geolocation inspection checklist (celestial shadows, road infrastructure, utility poles, architecture, flora, scripts) for an unidentified outdoor photo.
| Argument | Type | Description |
|---|---|---|
| environment* | string | Primary scene environment |
{
"type": "object",
"required": [
"environment"
],
"properties": {
"environment": {
"enum": [
"urban",
"highway",
"rural",
"coastal",
"mountain"
],
"type": "string",
"description": "Primary scene environment"
}
}
}Convert EXIF Degrees-Minutes-Seconds (DMS) rational GPS tuples into standard WGS84 decimal latitude and longitude coordinates.
| Argument | Type | Description |
|---|---|---|
| dmsString* | string | DMS string (e.g. "37°20'19.7\"N 121°53'29.8\"W") |
{
"type": "object",
"required": [
"dmsString"
],
"properties": {
"dmsString": {
"type": "string",
"description": "DMS string (e.g. \"37°20'19.7\\\"N 121°53'29.8\\\"W\")"
}
}
}Retrieve step-by-step triangulation methodology from verified LocatePic visual forensics case studies (viaduct skyline geometry, desert road roll-fit, urban botany).
| Argument | Type | Description |
|---|---|---|
| topic* | string | Case topic (e.g. "skyline", "highway", "botany") |
{
"type": "object",
"required": [
"topic"
],
"properties": {
"topic": {
"type": "string",
"description": "Case topic (e.g. \"skyline\", \"highway\", \"botany\")"
}
}
}Check which EXIF/XMP/IPTC tags leak exact GPS coordinates, altitude, compass bearing, and device serial numbers before sharing images online.
| Argument | Type | Description |
|---|---|---|
| fileFormat* | string | Image container format |
{
"type": "object",
"required": [
"fileFormat"
],
"properties": {
"fileFormat": {
"enum": [
"JPEG",
"HEIC",
"PNG",
"WEBP",
"RAW"
],
"type": "string",
"description": "Image container format"
}
}
}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.
| Argument | Type | Description |
|---|---|---|
| code* | string | Dialing prefix (e.g. "+48", "+81") or ccTLD (e.g. ".ch", ".kr") |
{
"type": "object",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"description": "Dialing prefix (e.g. \"+48\", \"+81\") or ccTLD (e.g. \".ch\", \".kr\")"
}
}
}Look up left-hand vs right-hand traffic rules, center line colors (yellow vs white), and bollard styles by country or region.
| Argument | Type | Description |
|---|---|---|
| countryOrRegion* | string | Country name or ISO code (e.g. "Japan", "Australia", "United States", "UK", "Germany") |
{
"type": "object",
"required": [
"countryOrRegion"
],
"properties": {
"countryOrRegion": {
"type": "string",
"description": "Country name or ISO code (e.g. \"Japan\", \"Australia\", \"United States\", \"UK\", \"Germany\")"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 10, 2026.