
Sensormesh Mcp
io.github.jayjexPublished by GitHub account jayjexv0.1.0Updated Oct 24, 2026
MCP server for the SensorMesh open sensor data commons: inventory, reading windows, stats.
Overview
A local MCP server that gives an assistant access to the SensorMesh open sensor data commons for inventory, reading windows and statistics.
- What you can do
- Look up the inventory of sensors available in the SensorMesh open sensor data commons, according to the registry description. Retrieve reading windows of sensor data. Obtain statistics over that sensor data. The registry lists no individual tools, so the exact operations are not documented here.
- When to use it
- Worth adding when an assistant needs to work with open sensor data from SensorMesh, such as checking which sensors exist, pulling readings for a time window, or summarizing statistics.
- Requirements
- Runs as a local process over stdio, installed from the npm package @jayjex/sensormesh-mcp, so a Node.js runtime is needed. It is desktop only and not web executable. No authentication, environment variables or headers are declared, but network access to the SensorMesh data source is implied.
Installation
In SourceWeft
- Open Sensormesh Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
25% 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.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.