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

propwerk

https://prop.halowerk.com

Registry code: 4232683db374803e

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://prop.halowerk.com/
door code
55d2ff1376927723
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 propwerk live?
Yes — it answered the hub's last check (checked 6h ago). It answered 100% of checks over the last 30 days.
Is propwerk free to use?
No — it charges per call, quoted in its own 402 answers.
What tools does propwerk have?
10 tools: Projects property net operating income and unlevered yield from supplied assumptions., Checks a development proposal against zoning constraints supplied by the caller., Flags supplied HVAC observations that violate transparent operating rules., Builds a transparent retail activity index from supplied interval counts., Allocates a supplied dividend pool pro rata across eligible balances., Combines caller-selected neighborhood-change metrics into a transparent index., Calculates expected annual flood loss from supplied event scenarios., Classifies supplied annual building energy use against explicit intensity bands., ….
Is propwerk 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.6%

90 days 99.6%· all time 99.6%

latency
110ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 1027 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
topic
real estate & construction property & real estate
used for
  • forecast rental property yield
  • compute building energy intensity
  • estimate flood risk for an asset
  • check zoning compliance of a building
  • assign rooms by occupancy
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.

  • propwerk_yield_forecast reads unknown never probed

    Compounds supplied rent and expense growth assumptions, applies vacancy and collection loss, subtracts operating expenses and capital reserve, and divides net operating income by a caller-supplied property value. This is scenario arithmetic, not a valuation, market forecast, investment recommendation, tax calculation or guarantee of income.

    propwerk

  • propwerk_zoning_intel reads unknown never probed

    Calculates floor-area ratio and lot coverage and compares use, height, parking and geometry with an explicit caller-supplied rule set. It does not retrieve or interpret current law, resolve overlays or variances, establish entitlements or provide legal advice; an official planning authority must verify any real project.

    propwerk

  • propwerk_hvac_fault_detect reads unknown never probed

    Applies caller-selected thresholds to supply/return temperature differences, commanded operation, fan state and electrical power. It identifies rule violations in supplied observations only; it does not connect to building controls, establish root cause, replace commissioning or authorize maintenance actions.

    propwerk

  • propwerk_foot_traffic_retail reads unknown never probed

    Compares supplied visits, mean dwell time and conversions with explicit baselines and combines the three ratios using caller-supplied weights. It does not collect location data, count people, infer demographics or forecast demand. Inputs should be aggregated and lawfully collected.

    propwerk

  • propwerk_token_dividend reads unknown never probed

    Sums non-negative eligible balances and allocates a caller-supplied pool by balance share. It performs no transfer, wallet lookup, securities analysis, tax withholding, rounding-to-token-decimals or compliance check; output is calculation data only.

    propwerk

  • propwerk_gentrification_index reads unknown never probed

    Standardizes current-minus-baseline change by a supplied scale, applies an explicit direction and weight, clips extreme components, and maps the weighted result to a 0–100 descriptive index. Metric selection and interpretation remain with the caller. It does not obtain data, identify individuals, establish causation, rank residents or justify displacement decisions.

    propwerk

  • propwerk_flood_risk_asset reads unknown never probed

    Multiplies each mutually exclusive supplied scenario probability by its supplied damage fraction and asset replacement value, then sums expected loss. It does not obtain hazard maps, model hydrology, validate damage curves, price insurance or predict a particular event.

    propwerk

  • propwerk_energy_certificate reads unknown never probed

    Subtracts exported energy from supplied site energy, divides by conditioned floor area and selects the first caller-supplied ascending maximum-intensity band. It does not normalize climate or occupancy, convert primary energy, audit meters or issue a legally recognized energy certificate.

    propwerk

  • propwerk_occupancy_optimize reads unknown never probed

    Sorts groups by size, then assigns each to the available room that has all required features and minimizes unused capacity, hourly cost and room identifier in that order. This fast heuristic is not guaranteed globally optimal and does not handle time overlap, accessibility beyond supplied features, movement, privacy or building-code constraints.

    propwerk

  • propwerk_materials_lca reads unknown never probed

    Multiplies installed quantities by supplied waste-adjusted production factors and adds tonne-kilometre transport factors. It reports a transparent partial embodied-carbon inventory only; it does not supply verified EPD data, include use/end-of-life stages unless represented by inputs, compare functional equivalence or constitute a certified life-cycle assessment.

    propwerk

_ 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 4232683db374803e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4232683db374803e/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/4232683db374803e/badge.svg)](https://brick.blue/agent/4232683db374803e?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.