_ registry / mcp streamable-http · checked 1h ago

umarelli

https://umarelli.org

Registry code: f3cd05c700a1ee83

api record

Umarelli maps construction in New York City and Jersey City from public records. Use search to find a building by address, fetch for its permits, taxes, tax breaks and zoning, and recent_permits for new buildings and major renovations near an address. Figures come from city open data, refreshed within a day of each release, and some city datasets only update quarterly or yearly; link people to the Umarelli page for each building.

endpoint
https://umarelli.org/mcp
protocol
streamable-http ·2025-06-18
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 umarelli live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is umarelli free to use?
Yes — the hub reached it with no key and no payment.
What tools does umarelli have?
3 tools: fetch, search, recent_permits.
Is umarelli 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
100%

90 days 100%· all time 100%

latency
380ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • fetch unknown 1h ago

    Get one building’s record from Umarelli: building permits, assessed value and property tax bill, tax breaks, zoning, and news coverage. The id is a New York City BBL (ten digits), a Jersey City id such as jc:14106:39, or an Umarelli building URL.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "A building id from search, a BBL, or a building URL"
    }
  }
}
    arguments 12 lines
  • search unknown 1h ago

    Find buildings in New York City or Jersey City by street address. Returns ids, names and Umarelli page URLs; pass an id to fetch for the full record. New York City is assumed; include "Jersey City" to search there.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "A street address, e.g. 205 Montague Street, Brooklyn"
    }
  }
}
    arguments 12 lines
  • recent_permits unknown 1h ago

    List new-building and major-renovation permits near a street address in New York City (dated by filing) or Jersey City (dated by issue), newest first, each with a link to its building on Umarelli.

    mcp-tool

    {
  "type": "object",
  "required": [
    "address"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "address": {
      "type": "string",
      "description": "A street address, e.g. 120 Franklin Street, Brooklyn"
    },
    "radius_meters": {
      "type": "number",
      "default": 500,
      "maximum": 2000,
      "minimum": 50
    }
  }
}
    arguments 24 lines
_ try it 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 f3cd05c700a1ee83.

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

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.