Senlay Physical Context

Physical-world evidence and operability checks with provenance and explicit data gaps.

Should I use this

Quality & Safety

A
Description quality
93%
Schema completeness
83%
Naming quality
95%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'get_forecast_trust' description lacks action verbin get_forecast_trust

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,099Tokens (tool definitions)
~1.7 KBTypical response size
Moderate attention impact (0.86% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "senlay": {
      "url": "https://senlay.cloud/mcp"
    }
  }
}

Remote endpoints

https://senlay.cloud/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
⚪sense_location(lat, lng, domain, time)

Return current physical-world evidence and historical forecast reliability for a coordinate. Every available value keeps its provenance, distance, age, measured/predicted status and confidence; source divergence is reported. Required but unavailable evidence is named, never silently estimated.

Input Schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude from -90 to 90."
    },
    "lng": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude from -180 to 180."
    },
    "domain": {
      "default": "general",
      "description": "Operational domain; defaults to general.",
      "type": "string",
      "enum": [
        "general",
        "kitesurfing",
        "surfing",
        "sailing",
        "drone",
        "paragliding",
        "hiking",
        "agriculture",
        "construction",
        "running"
      ]
    },
    "time": {
      "description": "Optional ISO 8601 time. This release supports current conditions only (within 10 minutes of now).",
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    }
  },
  "required": [
    "lat",
    "lng"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢check_operability(lat, lng, domain, time)

Decision support for an activity at a coordinate, including historical forecast reliability when established. Returns Senlay Core thresholds, exceeded conditions, source divergence, unknowns and assessment uncertainty. It may be wrong; unavailable evidence is named rather than inferred, and a human remains the final authority.

Input Schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude from -90 to 90."
    },
    "lng": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude from -180 to 180."
    },
    "domain": {
      "type": "string",
      "enum": [
        "general",
        "kitesurfing",
        "surfing",
        "sailing",
        "drone",
        "paragliding",
        "hiking",
        "agriculture",
        "construction",
        "running"
      ],
      "description": "Operational domain to assess."
    },
    "time": {
      "description": "Optional ISO 8601 time. This release supports current conditions only (within 10 minutes of now).",
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    }
  },
  "required": [
    "lat",
    "lng",
    "domain"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢list_domains

List the operational domains accepted by Senlay and a brief of the evidence and threshold logic each domain uses. Actual thresholds and assessments always come from Senlay Core.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢get_forecast_trust(lat, lng)

Return historical forecast reliability at a coordinate, separately for wind speed and direction. It reports UNKNOWN until Core has enough eligible archived forecast-versus-instrument pairs; it never corrects a forecast or predicts when a regime will end. Decision support. Humans remain the final authority.

Input Schema

{
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "minimum": -90,
      "maximum": 90,
      "description": "Latitude from -90 to 90."
    },
    "lng": {
      "type": "number",
      "minimum": -180,
      "maximum": 180,
      "description": "Longitude from -180 to 180."
    }
  },
  "required": [
    "lat",
    "lng"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools