io.github.smartsurfsolarPublished by GitHub account smartsurfsolarv1.0.0Updated Oct 24, 2026
Physical-world evidence and operability checks with provenance and explicit data gaps.
Remote MCP server that gives an assistant physical-world evidence and activity operability checks for a coordinate, with provenance and explicit data gaps.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.smartsurfsolar%2Fsenlay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"senlay-physical-context": {
"type": "http",
"url": "https://senlay.cloud/mcp"
}
}
}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
Add the public stateless Streamable HTTP endpoint to an MCP-capable client. Anonymous trial access requires no signup or OAuth:
The MCP 2026-07-28 server exposes exactly sense_location, check_operability, and list_domains. It preserves Senlay evidence provenance and explicitly reports unavailable inputs instead of inventing values. To use an account tier, add Authorization: Bearer sl_live_... 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.
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.
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.
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.
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.
Nearby accepted observations appear in later authenticated /api/v1/sense and /api/v1/pwm responses as explicitly labelled direct station evidence. Checked station measurements also contribute to Senlay local memory baselines for the same place and season; those baselines are historical context, not current evidence.
The Python connector uses only the standard library, so a Raspberry Pi or ordinary computer needs no package installation. Copy the stationId and one-time station secret returned by the dashboard, then preview a simulated observation locally:
Preview mode does not contact Senlay. To verify the signature and payload without storing a reading, add the account API key and use the commissioning endpoint:
To exercise live ingestion with generated data, use --publish. Simulator readings are always marked estimated, carry simulated: true, and never enter the checked-reading place-memory baseline.
For a real wind sensor, pass its readings to the publisher. The default quality is raw; use --quality checked only when your adapter and sensor calibration justify that claim.
Import SenlayClient and observation from python/senlay_client.py to connect another sensor process directly.
Save both the apiKey and recoveryToken shown by the first command; each is returned only once. Replace [email protected] and my-first-agent with your own identity.
Send the example observation to the local gateway:
The gateway validates observations locally. Set SENLAY_INGEST_URL to forward them to an authorized compatible ingestion endpoint.
For hardware that publishes JSON observations to an MQTT broker, configure the MQTT variables in .env and run:
The bridge subscribes to SENLAY_MQTT_TOPIC, validates every message through the SDK, signs it with the station secret, and forwards it to the HTTPS ingestion endpoint. Use one bridge credential per station; do not share a station secret among devices.
main: stable public releasesdevelop: active public developmentChanges move from a feature branch to develop, then reach main after review and tests. See CONTRIBUTING.md.
Apache-2.0. Contributions are welcome under the same license.
Source: README.md at commit a0b1bff
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.
latrequiredlngrequiredtimedomainDecision 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.
latrequiredlngrequiredtimedomainrequiredList 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.
Takes no parameters.
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.
latrequiredlngrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a license in the repository or the registry entry.
{ "mcpServers": { "senlay": { "url": "https://senlay.cloud/mcp" } }}# 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}}'git clone https://github.com/smartsurfsolar/senlay-platform.gitcd senlay-platformexport SENLAY_STATION_ID='stn_REPLACE_ME'export SENLAY_STATION_SECRET='sl_station_REPLACE_ME'python3 python/simulator.py --seed 1export SENLAY_ACCOUNT_API_KEY='sl_live_REPLACE_ME'python3 python/simulator.py --dry-run --seed 1python3 python/simulator.py --publish --count 3 --interval 10 --seed 1python3 python/publish_reading.py \ --lat 15.8801 --lng 108.3380 \ --wind-speed 7.4 --wind-direction 62CREDS="$(curl -sS -X POST https://senlay.cloud/api/v1/agent-register -H 'content-type: application/json' --data '{"ownerEmail":"[email protected]","agentName":"my-first-agent"}')"; printf '%s\n' "$CREDS"API_KEY="$(printf '%s' "$CREDS" | sed -n 's/.*"apiKey":"\([^"]*\)".*/\1/p')"curl -sS -H "Authorization: Bearer $API_KEY" "https://senlay.cloud/api/v1/sense?lat=15.8801&lng=108.3380&field=kitesurfing"npm installnpm testcp .env.example .envnpm run gatewaynpm run examplenpm run mqtt-bridgeimport { SenlayClient } from '@senlay/open-network';
const client = new SenlayClient({ endpoint: 'https://senlay.cloud/api/v1/observations', providerId: 'prv_REPLACE_ME', signingSecret: process.env.SENLAY_STATION_SECRET});
await client.publish({ stationId: 'stn_REPLACE_ME', observedAt: new Date().toISOString(), location: { lat: 15.8801, lon: 108.3380 }, measurements: [{ phenomenon: 'wind.speed', value: 7.4, unit: 'm/s' }]});