Sibfly
NPM · @PIPEWORX/MCP-SIBFLY · 2 COMPONENTS
SibFly — satellite-measured ground motion (subsidence / uplift) for any US address.
Available components
Last scanned (12 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sibfly). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 842 tokens (~280/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +3
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sibfly@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-sibfly |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sibfly/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692349220 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b94c005058d28ab92680c2842be7173b93c86c647742b688c0ef73d66c50fd3f2a70607f4ef722ac25fed00c5414f9ad4fd6c157b18bd916906cbdf63 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sibfly_coverage ~192
FREE preflight: does SibFly have satellite ground-motion coverage for this US address, and what would a full report cost? No key required. Returns coverage (true/false), confidence, and would_cost_usd. Use this before sibfly_ground_motion to check a property is covered without spending credits.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional SibFly API key (Bearer). With a key you get the full paid report; without one you get a free coverage/confidence teaser. Free key: POST https://sibfly.com/api/v1/autonomous/register. |
| address | string | – | US street address, e.g. "1600 Pennsylvania Ave NW, Washington DC". Provide this OR lat+lon. |
| lat | number | – | Latitude (WGS84). Use with lon instead of address. |
| lon | number | – | Longitude (WGS84). Use with lat instead of address. |
No output schema declared.
No examples provided.
sibfly_ground_motion ~338
Satellite-measured GROUND MOTION for a US address — is the land under a property SINKING or rising (subsidence / uplift / heave), in mm/year and in/year, from NASA Sentinel-1 InSAR. Use for property foundation risk, land subsidence, sinkhole/settlement concern, real-estate due diligence, or "is this address sinking?". Returns vertical velocity (mm/yr + in/yr) with uncertainty, seasonal amplitude, total motion, a plain-language assessment, confidence, and provenance. With a SibFly key (_apiKey) this is a full paid report ($0.40 from your credits); without a key it returns a FREE teaser (coverage + confidence + would_cost_usd). Out-of-coverage addresses return coverage:false and are never billed.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional SibFly API key (Bearer). With a key you get the full paid report; without one you get a free coverage/confidence teaser. Free key: POST https://sibfly.com/api/v1/autonomous/register. |
| address | string | – | US street address, e.g. "1600 Pennsylvania Ave NW, Washington DC". Provide this OR lat+lon. |
| brief | boolean | – | If true, add a short plain-English narration of the result. |
| include_timeseries | boolean | – | If true, embed the full motion history (per-date measurements) in the same report. |
| lat | number | – | Latitude (WGS84). Use with lon instead of address. |
| lon | number | – | Longitude (WGS84). Use with lat instead of address. |
No output schema declared.
No examples provided.
sibfly_timeseries ~259
Historical ground-motion time series for a US address — the per-date satellite measurements of vertical displacement over time (how the land has moved, month by month). Use to see the TREND of subsidence/uplift, not just the current velocity. series_type "measured" = real per-pass observations (premium frames); "modeled" = fitted trend on real acquisition dates. Needs a SibFly key for the full series ($0.40); keyless returns a coverage teaser.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional SibFly API key (Bearer). With a key you get the full paid report; without one you get a free coverage/confidence teaser. Free key: POST https://sibfly.com/api/v1/autonomous/register. |
| address | string | – | US street address, e.g. "1600 Pennsylvania Ave NW, Washington DC". Provide this OR lat+lon. |
| lat | number | – | Latitude (WGS84). Use with lon instead of address. |
| lon | number | – | Longitude (WGS84). Use with lat instead of address. |
| series_type | string | – | "measured" (real per-pass observations) or "modeled" (fitted trend). Default measured. |
No output schema declared.
No examples provided.
How do I install the Sibfly MCP server?
Sibfly runs locally as an npm package, launched with npx -y @pipeworx/mcp-sibfly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-sibfly
claude mcp add pipeworx-io-sibfly -- npx -y @pipeworx/mcp-sibfly
What is the Sibfly MCP server?
Sibfly is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sibfly. SibFly, satellite-measured ground motion (subsidence / uplift) for any US address. This page covers its npm package (@pipeworx/mcp-sibfly).
Is the Sibfly MCP server safe to use?
Sibfly scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sibfly MCP server expose?
Sibfly exposes 3 tools: sibfly_ground_motion, sibfly_coverage, sibfly_timeseries. Their descriptions and schemas cost roughly 789 tokens of context every time the server is loaded.
Is the Sibfly MCP server still maintained?
Sibfly is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sibfly MCP server under?
Sibfly declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Sibfly MCP server?
VerifyMCP ran 15 checks on Sibfly, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Sibfly: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.