Senlay Physical Context MCP server
io.github.smartsurfsolar/senlaysmartsurfsolarstreamable-httpv1.0.0Scanned
Physical-world evidence and operability checks with provenance and explicit data gaps.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Senlay Physical Context MCP server can do
The Senlay Physical Context MCP server is published by the GitHub account smartsurfsolar. It has 4 tools. It can create or change data (1 tool: check_operability), but cannot delete data. 3 tools only read.
1 tool brings in text other people can write (get_forecast_trust).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
check_operabilityDecision support for an activity at a coordinate, including historical forecast reliability when established.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 3Show 3 read-only tools
get_forecast_trustReturn historical forecast reliability at a coordinate, separately for wind speed and direction.Reads text others writeNo findings
Why it is in this group
- The name "get_forecast_trust" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: true
list_domainsList the operational domains accepted by Senlay and a brief of the evidence and threshold logic each domain uses.No findings
Why it is in this group
- The name "list_domains" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
sense_locationReturn current physical-world evidence and historical forecast reliability for a coordinate.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://senlay.cloud/mcp: tools/list returned 4 tools to an anonymous client, including check_operability (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:sense_locationOnly readsdescription
Tools2 changed.~2 changedView diff
- Changed:check_operabilityChanges thingsdescriptioninputSchema
- Changed:sense_locationOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http senlay https://senlay.cloud/mcpclaude mcp add --transport http senlay https://senlay.cloud/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__senlay__sense_location",
"mcp__senlay__list_domains",
"mcp__senlay__get_forecast_trust"
],
"ask": [
"mcp__senlay__check_operability"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as senlay. Review it before you use it.
Capability tags behind 1 rule
- mcp__senlay__get_forecast_trust untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.smartsurfsolar/senlay/verify?hash=5775787a9b69191a52775d3438c1dd3db4473136a6cea2e88946d8b40165cf6a" | jq -e '.changed == false'Pinned hash 5775787a9b69, from Nov 20, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.smartsurfsolar/senlay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.smartsurfsolar/senlay)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.
Senlay Physical Context MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Senlay Physical Context MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Senlay Physical Context MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Senlay Physical Context MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Senlay Physical Context MCP server have?
- 4 tools: 1 write, 3 read. check_operability, sense_location, list_domains and get_forecast_trust.
Does the Senlay Physical Context MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Senlay Physical Context MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Senlay Physical Context MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.