Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Ground Motion is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Measured ground motion per US address (NASA InSAR). Self-register, $0.40/report, misses free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ground-motion-mcp https://sibfly.com/mcp
# 2 — ask your agent for something these tools do
# check_ground_motion, check_portfolio, get_coverage and 6 more
Ground Motion costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ground-motion-mcp https://sibfly.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Measured ground motion (sinking/uplift) for a US address or lat/lon, in mm/year AND in/year, from NASA OPERA Sentinel-1 InSAR. Costs $0.40 from your SibFly credits; out-of-coverage / too-stale / too-low-confidence / fuzzy-geocode return FREE. Use the gate params to avoid paying for data you'd reject. dry_run=true is a FREE coverage+cost preview.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | US street address |
| lat | number | no | — |
| lon | number | no | — |
| explain | boolean | no | add ground_brief: ~600 tokens of plain-English narration + FAQ (engine GL52 free tier / CL46 paying). Adds ~10s latency. Only set when a human will read the output; use ask_inspector for follow-up Q&A |
| dry_run | boolean | no | FREE preview: coverage + would_cost + data age, no rate, no charge |
| max_age_days | integer | no | if data older than this, return free instead of billing |
| min_confidence | number | no | 0-1; below this, return free instead of billing |
| since | string | no | YYYY-MM-DD; if no new data since this date, return free |
| require_significant | boolean | no | if the rate would be no_clear_trend (within its error bar), return FREE instead of billing — never pay for statistical noise |
| compact | boolean | no | lean payload (fewer tokens) |
Batch ground-motion for many US addresses in one call. Only covered addresses are billed ($0.40 each); misses and duplicate cells are free. If credits run out mid-batch the response status is 'insufficient_credits' and unbilled items are marked — top up (buy_credits) and retry them.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| addresses | array | yes | up to 1000 US addresses (must be an ARRAY, not one string) |
| max_spend_usd | number | no | hard budget cap: billing stops at this total; over-budget items come back skipped_for_budget |
FREE pre-flight: is a US address/point covered, how stale is the data (data_age_days), and what a report would cost. Accepts ONE address/lat+lon, OR addresses[] (up to 1000, needs your Bearer key) to size a whole job before spending. Call this before spending.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | — |
| lat | number | no | — |
| lon | number | no | — |
| addresses | array | no | batch mode: size a whole job in one free call |
Multi-year cumulative motion history for an address. Pass from_date and to_date (YYYY-MM-DD) to get the movement between two dates. Costs $0.40 (misses free). dry_run=true is a FREE preview (points + dates + cost, no data); max_age_days returns free instead of billing for stale data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | — |
| lat | number | no | — |
| lon | number | no | — |
| from_date | string | no | — |
| to_date | string | no | — |
| dry_run | boolean | no | FREE preview: coverage + n_points + would_cost, no series, no charge |
| max_age_days | integer | no | if data older than this, return free instead of billing |
FREE: your SibFly credit balance, price per report, reports remaining, and top-up URL.
No parameter schema on file.
FREE: create a new SibFly account and get an API key + free starter credits in ONE call — no human, no captcha, no card. Use this when you have no API key. SAVE the returned api_key and pass it as the Bearer token on later calls (MCP clients: set it as the Authorization header).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | a durable email address (disposable domains rejected) | |
| password | string | no | optional; auto-generated and returned if omitted |
Get a machine-usable payment link to top up credits (requires your Bearer API key). method 'stripe' returns a card checkout_url; 'crypto' returns a BTC invoice_url + txn_id. Open/relay the URL to complete payment; credits land automatically afterwards — confirm with get_account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount_usd | number | yes | 1 to 10000 (USD) |
| method | string | no | default stripe (card) |
FREE follow-up Q&A with the SibFly Inspector about a report you ALREADY BOUGHT (buy via check_ground_motion first). Ask what the numbers mean for foundations, staleness, seasonal swings, etc. It answers only from the report's numbers (never invents), and won't give buy/walk-away advice. Per-account message allowance applies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | your question about the report |
| address | string | yes | the address of a report already purchased on this account |
FREE: your recent billed calls (line-item ledger with request_id, endpoint, address, cost) so you can reconcile spend against reports.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | max rows, default 100, max 1000 |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ground Motion or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_ground_motion | no tags | |
| check_portfolio | no tags | |
| get_coverage | no tags | |
| get_motion_history | no tags | |
| get_account | no tags | |
| register_agent | state-write | state-write: declares readOnlyHint: false |
| buy_credits | state-write | state-write: declares readOnlyHint: false |
| ask_inspector | no tags | |
| get_usage | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Ground Motion can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.