Aeroz vs GroundTruth — subsurface scan QA & trade estimating

A side-by-side look at the Aeroz and GroundTruth — subsurface scan QA & trade estimating MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

AerozIndustrial & IoT · Remote HTTP/SSEProve a physical item is genuine (NFC chip); read its EU Digital Product Passport, recalls, custody.51GoodAuth: not declared

GroundTruth — subsurface scan QA & trade estimatingIndustrial & IoT · Remote HTTP/SSETwo independent AI models read a GPR, locate or pipe scan and flag the do-not-core call.53GoodAuth: not declared

Verdict: choose Aeroz for industrial & iot work over a hosted endpoint; choose GroundTruth — subsurface scan QA & trade estimating for industrial & iot over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose Aeroz when

You need dedicated capabilities in the Industrial & IoT domain.
You prefer a remote HTTP/SSE transport.
You have the keys it needs: PSA_API_TOKEN.
You want tools like verify_chip, check_recall, dpp_readiness.

Explore Aeroz

Choose GroundTruth — subsurface scan QA & trade estimating when

You need dedicated capabilities in the Industrial & IoT domain.
You prefer a remote HTTP/SSE transport.
You want tools like read_scan, draft_estimate, get_pricing.

Explore GroundTruth — subsurface scan QA & trade estimating

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	A Aeroz	GroundTruth — subsurface scan QA & trade estimating
Category	Industrial & IoT	Industrial & IoT
Quality signal	51/100 · Good	53/100 · Good
Install command	Confirmed	Confirmed
Transport	Remote HTTP/SSE	Remote HTTP/SSE
Auth	Not declared	Not declared
Pricing	Not declared	Not declared
Required env vars	`PSA_API_TOKEN`	None listed
Verified owner	Community listing	Community listing
GitHub stars	—	0
Directory activity	0 views 0 installs 0 upvotes	2 views 0 installs 0 upvotes
Tools	30	3
Full listing	View Aeroz	View GroundTruth — subsurface scan QA & trade estimating

Tools & capabilities

Aeroz tools 30

verify_chipVerify a physical item by its Aeroz chip: the UID plus whatever signature the tap carried. Same answer as GET /v1/verify. Use this before trusting any claim about a physical unit — a database record proves a record exists, not that the object in front of you is the one it describes. Read `proof` and `proves`: proof "presence" means the chip answered a fresh one-time SUN challenge (picc_data + cmac) and was physically there at this tap; proof "identity" means the static `t` signature is the one Aeroz issued for this UID, which a copied tag also carries. verified:false with reason "no_signature" (recognised:true) proves NOTHING about the item — only that the number is on the register. "signature_unchecked" means the signature was not compared (not a mismatch). A failed signature returns NO product data. Each call records the tap and spends the chip's one-time answer, so pass each SUN tap once. A sandbox key answers its seeded sandbox chips as fixtures (mode "sandbox" with a _warning) and any other UID from the register (mode "sandbox", register:true), so a sandbox company can check the test tags it minted.
check_recallCheck whether a specific unit is subject to an active recall, from the register: reads only, verifies no signature and spends no chip answer. Returns known (on the register), recalled, and the recall reason, severity, date and id when one applies. recalled:null means the status is UNKNOWN (the UID is not on the register, or the register could not be read) — never report that as "not recalled". This says nothing about whether the item is genuine; use verify_chip for that. Use whenever a unit is about to be shipped, sold, dispensed, or installed. A sandbox key answers its seeded sandbox chips first and any other UID from the register (register:true).
dpp_readinessAssess how ready a product category is for an EU Digital Product Passport, against the delegated act that applies to it. Returns the required data fields, which are present, and which are missing. IMPORTANT: this is a readiness signal, not a legal compliance determination — never report its output as confirmation that a product is compliant.
list_findingsList findings raised by the Aeroz compliance agents watching this organisation — recall hits, DPP data gaps, regulatory changes, dwell anomalies, and clone detections. Use this to answer "what needs my attention".
list_agentsList the Aeroz compliance agents available to this organisation and which are currently enabled. Use this to explain monitoring coverage or to find an agent worth enabling.
get_usageReturn this organisation's Aeroz verification volume and outcome breakdown over a recent period. Use for reporting on scan volume, authentication failure rates, and trend. The buckets — authentic, recalled (any tap whose answer carried a recall, verified or not), mismatched (failed static or SUN signature), not_found, unverified (no or unchecked signature, test tag, held or disabled unit) and other — always sum to total.
list_sandbox_chipsList the seeded sandbox chips for this organisation, with the UID and signature to pass to verify_chip, one per scenario: authentic, recalled, signature_mismatch (listed with a deliberately WRONG signature) and not_found (a UID that is not on the register). Sandbox only — use when building or testing an integration before physical chips ship.
onboarding_statusReport where this organisation stands in Aeroz onboarding: current stage, percentage complete, health, the single next action, and every open step with which side owns it. Use this to answer "what do we still need to do", "why are we not live yet", or "what is Aeroz waiting on". Steps marked side="aeroz" are Aeroz's obligation, not the customer's — say so plainly rather than presenting them as homework.
onboarding_next_stepReturn only the single most important next action and how to complete it. Use when the user asks what to do next and does not want the whole checklist.
complete_onboarding_stepMark a manual onboarding step complete on behalf of this organisation. Only steps the customer owns and that Aeroz cannot verify automatically can be set this way; an automatically verified step will refuse, because a self-report that contradicts the platform data is worse than no report. Pass the step key from onboarding_status.
business_briefThe full picture of this business as Aeroz holds it: declared product categories with their mandate dates and whether each date is fixed or provisional, onboarding state, open findings, and — importantly — which recall sources are NOT being monitored. Use this to orient before answering anything about the account. Never present an empty findings list as evidence of safety without also reporting coverage_gaps.
ask_agentAsk this organisation's dedicated Aeroz agent a question in plain language and get a grounded answer. Use it for anything a human at the business would ask their account manager: "what do we still need to do", "when is our deadline", "what is Aeroz waiting on", "what is not being monitored", "how do we go live". The answer carries `grounded`: `computed` means it was read directly from the account's own data; `model` means a model composed it from that data and every date and figure was checked against it; `declined` means the agent does not hold what the question needs and said so — relay that honestly rather than filling the gap yourself. Asking refreshes the account's onboarding state and records the question and answer in the conversation (see agent_conversation). It sends nothing outside Aeroz and changes no product, shipment or passport data.
+18 more on the listing page

GroundTruth — subsurface scan QA & trade estimating tools 3

read_scanGet an independent AI second opinion on a subsurface scan before anyone cores or digs. Send a public image URL of a GPR scan, a marked-up concrete slab photo, a utility-locate markup, a concrete radiograph, or a CCTV pipe frame. TWO different AI models read it independently — the second is prompted to refute the first — and you get back every located target with its hazard class (do-not-core / rebar / verify / clear), plus a QA flag when the two reads disagree. Advisory only: a certified technician must review and sign off before any cutting.
draft_estimateTurn a plain-English description of a trade job into a professional itemized bid — real materials by size, fittings, consumables and labor on its own line, at realistic US market prices. Built for one-truck electrical, plumbing, HVAC and general-contracting shops. This is GruntPay: the contractor normally speaks this into their phone. Returns the line items plus a link to brand it and send it to the customer.
get_pricingCurrent GroundTruth and GruntPay plans and prices. Free to call — use it before answering any cost question rather than guessing.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Aeroz

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aeroz": {
      "command": "npx",
      "args": [
        "-y",
        "aeroz"
      ],
      "env": {
        "PSA_API_TOKEN": "YOUR_PSA_API_TOKEN_HERE"
      }
    }
  }
}

GroundTruth — subsurface scan QA & trade estimating

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "groundtruth-subsurface-scan-qa-trade-estimating-2": {
      "url": "https://gtfi.ai/mcp"
    }
  }
}

Frequently asked questions

Aeroz is categorized under Industrial & IoT and uses a remote HTTP/SSE transport. GroundTruth — subsurface scan QA & trade estimating belongs to Industrial & IoT and uses a remote HTTP/SSE transport. Pick Aeroz for industrial & iot work and GroundTruth — subsurface scan QA & trade estimating for industrial & iot.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Aeroz has no declared pricing — check the project's own site. GroundTruth — subsurface scan QA & trade estimating has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add aeroz and groundtruth-subsurface-scan-qa-trade-estimating-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Aeroz has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. GroundTruth — subsurface scan QA & trade estimating has 53/100 (Good) with 2 views, 0 installs and 0 GitHub stars.