_ registry / mcp http-sse · checked 24m ago

senlay-physical-context

https://senlay.cloud

Registry code: 109c397864ab7338

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://senlay.cloud/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is senlay-physical-context live?
Yes — it answered the hub's last check (checked 24m ago). It answered 99% of checks over the last 30 days.
Is senlay-physical-context free to use?
Yes — the hub reached it with no key and no payment.
What tools does senlay-physical-context have?
4 tools: sense_location, check_operability, get_forecast_trust, list_domains.
Is senlay-physical-context safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.5%

90 days 99.3%· all time 99.3%

latency
610ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 591 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· fetch failed
  • degraded → live
_ what it is for
topic
weather & environment
used for
  • check operability of an activity at a location
  • get forecast reliability at a coordinate
  • get physical-world evidence for a location
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_domains reads open 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • sense_location reads unknown never probed

    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. Nearby station wind readings are cross-checked; possible sensor/reporting anomalies are flagged for review, not diagnosed as confirmed failures. For drones, separate model-derived precipitation and thunderstorm context is provided when available; the outcome includes wind and model precipitation and thunderstorm indications and is not lightning detection. Required but unavailable evidence is named, never silently estimated.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "lat",
    "lng"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude from -90 to 90."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude from -180 to 180."
    },
    "time": {
      "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)))$",
      "description": "Optional ISO 8601 time. This release supports current conditions only (within 10 minutes of now)."
    },
    "field": {
      "enum": [
        "kitesurfing",
        "surfing",
        "sailing",
        "water_safety",
        "lifeguard",
        "fishing",
        "drone",
        "paragliding",
        "construction",
        "outdoor_work",
        "worksite",
        "agriculture",
        "hiking",
        "running",
        "events",
        "air_quality",
        "general"
      ],
      "type": "string",
      "description": "Alias for domain; when both are supplied they must agree."
    },
    "domain": {
      "enum": [
        "kitesurfing",
        "surfing",
        "sailing",
        "water_safety",
        "lifeguard",
        "fishing",
        "drone",
        "paragliding",
        "construction",
        "outdoor_work",
        "worksite",
        "agriculture",
        "hiking",
        "running",
        "events",
        "air_quality",
        "general"
      ],
      "type": "string",
      "description": "Operational domain; defaults to general. Legacy domain argument remains supported."
    }
  }
}
    arguments 74 lines
  • check_operability reads unknown 9h ago

    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. Drone rain and thunderstorm model context is separate; the outcome includes wind and model precipitation and thunderstorm indications and is not lightning detection. It may be wrong; unavailable evidence is named rather than inferred, and a human remains the final authority.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "lat",
    "lng"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude from -90 to 90."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude from -180 to 180."
    },
    "time": {
      "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)))$",
      "description": "Optional ISO 8601 time. This release supports current conditions only (within 10 minutes of now)."
    },
    "field": {
      "enum": [
        "kitesurfing",
        "surfing",
        "sailing",
        "water_safety",
        "lifeguard",
        "fishing",
        "drone",
        "paragliding",
        "construction",
        "outdoor_work",
        "worksite",
        "agriculture",
        "hiking",
        "running",
        "events",
        "air_quality",
        "general"
      ],
      "type": "string",
      "description": "Alias for domain; when both are supplied they must agree."
    },
    "domain": {
      "enum": [
        "kitesurfing",
        "surfing",
        "sailing",
        "water_safety",
        "lifeguard",
        "fishing",
        "drone",
        "paragliding",
        "construction",
        "outdoor_work",
        "worksite",
        "agriculture",
        "hiking",
        "running",
        "events",
        "air_quality",
        "general"
      ],
      "type": "string",
      "description": "Operational domain to assess; supply domain or field."
    }
  }
}
    arguments 74 lines
  • get_forecast_trust reads unknown 9h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "lat",
    "lng"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude from -90 to 90."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude from -180 to 180."
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 109c397864ab7338.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/109c397864ab7338/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/109c397864ab7338/badge.svg)](https://brick.blue/agent/109c397864ab7338?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.