Senlay Physical Context MCP server

Senlay — Verified Physical Context for Systems That Act Outside

This is the Senlay Open Network: the open protocol, JavaScript SDK, and edge-gateway starter for connecting independently operated sensors to verified physical context.

senlay.cloud · API documentation

Connect an AI agent with MCP — no install

Add the public stateless Streamable HTTP endpoint to an MCP-capable client. Anonymous trial access requires no signup or OAuth:

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

The MCP 2026-07-28 server exposes exactly senselocation, checkoperability, and listdomains. It preserves Senlay evidence provenance and explicitly reports unavailable inputs instead of inventing values. To use an account tier, add Authorization: Bearer sllive_... to the server headers. Operability results are decision support; humans remain the final authority.

Official MCP Registry metadata is provided in server.json. Version 1.0.0 is published as io.github.smartsurfsolar/senlay after live endpoint and schema validation.

What is open here

• vendor-neutral observation envelope and JSON Schema
• deterministic validation and normalization
• HMAC request signing for provider-to-gateway transport
• JavaScript client for any compatible ingestion endpoint
• small edge gateway that validates before forwarding
• adapter example and automated tests

The production aggregation engine, global registry, authentication, billing, provider credentials, historical place-memory corpus, risk models, and commercial connectors remain in the private senlay-platform-core repository.

The public website source is maintained separately in senlay-world; its canonical domain is senlay.cloud. See repository boundaries for the public/private split and branch policy.

Status

This is the first 0.x protocol release. Self-service station registration and signed observation ingestion are available at senlay.cloud for authenticated Senlay accounts. The server retains only a non-recoverable hash of every station secret; save each secret when it is returned.

The network is at the start of its path: there are no coverage guarantees and no SLA. It is not claimed as generally available.

Connect a station to the live network

First create a normal account at senlay.cloud/register.html, then create an API key in the dashboard and save it when shown. Stored keys cannot be retrieved; create a replacement if yours is lost. Use that account key for provider and station management; use the station secret only to sign observations.

# Create a provider with your account API key.
curl -sS -X POST https://senlay.cloud/api/v1/providers/register \
  -H "Authorization: Bearer $API_KEY" -H 'content-type: application/json' \
  --data '{"name":"My community network","slug":"my-community-network"}'

# Substitute the returned prv_... ID. Save the returned station secret now.
curl -sS -X POST https://senlay.cloud/api/v1/stations/register \
  -H "Authorization: Bearer $API_KEY" -H 'content-type: application/json' \
  --data '{"providerId":"prv_REPLACE_ME","name":"Beach wind station","sensorType":"weather_station","location":{"lat":15.8801,"lng":108.3380}}'

Before publishing live data, use the dashboard's Send signed test action to verify the station secret and payload shape without storing a fake observation. Then publish to https://senlay.cloud/api/v1/observations using the returned stationId plus the X-Senlay-* signature headers described in the network protocol.

Shortened. The full README is on GitHub.