_ registry / mcp + a2a JSONRPC · checked 8h ago

iotwerk

https://iot.halowerk.com

Registry code: 91d9b7bc70ca197b

api record

Paid tools via x402. tools/list is free. Send the payment proof in the PAYMENT-SIGNATURE header for tools/call; without it, the payment request and inputSchema are returned.

endpoint
https://iot.halowerk.com/
door code
aa15a267c61ccae3
protocol
JSONRPC ·0.3
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is iotwerk live?
Yes — it answered the hub's last check (checked 8h ago). It answered 99% of checks over the last 30 days.
Is iotwerk free to use?
No — it charges per call, quoted in its own 402 answers.
What tools does iotwerk have?
10 tools: Builds and verifies an HMAC-SHA256 authentication tag for a canonical device challenge., Flags fleet readings that deviate from the cohort using median absolute deviation., Estimates LoRa link margin from a transparent log-distance path-loss budget., Merges local and remote digital-twin changes by field version and exposes conflicts., Estimates cycle and calendar capacity fade from explicit engineering coefficients., Checks a polyline robot path against circular obstacles and reports minimum clearance., Creates a canonical OTA manifest digest and an HMAC release-integrity tag., Finds the minimum-cost route through a supplied mesh graph using Dijkstra’s algorithm., ….
Is iotwerk safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.5%· all time 99.4%

latency
87ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1136 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • estimate battery degradation
  • detect anomalies across a device fleet
  • estimate lora coverage
  • compute mesh network routes
  • calibrate a sensor
takes → gives
data → data
tools
10 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 121 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
46

distinct

settlements
9,342

last 2026-11-10

received on chain
37.4096 USDC

shared-payto

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

_ what it can do 10 tools
10 never probed 0 of 10 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • iotwerk_device_auth reads unknown never probed

    Canonicalizes device_id, nonce and message, computes an HMAC-SHA256 tag with caller-supplied ephemeral key material, and optionally compares a claimed tag in constant time. It does not provision devices, store keys or replace asymmetric device identity; do not submit long-lived production secrets.

    iotwerk

  • iotwerk_fleet_anomaly reads unknown never probed

    Computes cohort median, median absolute deviation and robust z-scores for one numeric reading per device. A caller-selected threshold determines flags. It detects cross-sectional outliers only and does not diagnose root cause or learn temporal behavior.

    iotwerk

  • iotwerk_lora_coverage reads unknown never probed

    Computes free-space loss at one metre, applies a caller-supplied path-loss exponent over distance, then reports estimated receive power and margin against receiver sensitivity. This planning estimate does not model terrain, Fresnel obstruction, interference, antenna mismatch or regulatory duty cycle.

    iotwerk

  • iotwerk_digital_twin_sync reads unknown never probed

    Groups caller-supplied scalar field changes by field name, selects the highest version, and reports a conflict when equal-version values differ. It does not connect to a twin platform, merge nested documents or resolve semantic conflicts.

    iotwerk

  • iotwerk_battery_degradation reads unknown never probed

    Applies a transparent heuristic: cycle fade scales with equivalent full cycles and depth-of-discharge exponent; calendar fade scales with square-root time and a temperature factor. Coefficients are caller supplied or declared defaults. This is not cell-chemistry validation, warranty advice or a safety prognosis.

    iotwerk

  • iotwerk_robotic_path_clearance reads unknown never probed

    Computes the minimum Euclidean distance from each circular obstacle center to every path segment, then subtracts obstacle radius and robot radius. It detects planar static clearance only; it does not model robot shape beyond a circle, dynamics, uncertainty or moving obstacles.

    iotwerk

  • iotwerk_ota_sign reads unknown never probed

    Canonicalizes firmware hash, version, device model and minimum bootloader version, then produces a SHA-256 manifest digest and HMAC-SHA256 release tag using caller-supplied ephemeral key material. This is a symmetric integrity tag, not a vendor PKI signature or code-signing service.

    iotwerk

  • iotwerk_mesh_route reads unknown never probed

    Computes a deterministic shortest path over caller-supplied directed or bidirectional links with non-negative costs. It does not measure live radio conditions, reserve capacity or push routes to devices.

    iotwerk

  • iotwerk_sensor_calibration reads unknown never probed

    Fits reference = slope × observed + offset with ordinary least squares over paired caller-supplied readings. It reports residual diagnostics and does not claim traceability, uncertainty accreditation or suitability beyond the supplied calibration range.

    iotwerk

  • iotwerk_edge_compute_bid reads unknown never probed

    Filters caller-supplied bids by CPU, memory and latency constraints, computes workload cost from quoted unit prices, and ranks feasible candidates by total cost then latency. It does not contact providers, attest hardware or place a bid.

    iotwerk

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 91d9b7bc70ca197b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/91d9b7bc70ca197b/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/91d9b7bc70ca197b/badge.svg)](https://brick.blue/agent/91d9b7bc70ca197b?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on halowerk.com 109 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

101 more sit on this domain. All of them.