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

rentaltechmatch

https://rentaltechmatch.com

Registry code: c6ec30c153730b0a

api record

Read-only data on US rental software prices: property management software for long-term rentals (priced by number of units) and Airbnb / vacation rental software for short-term rentals (priced by number of listings). Use price_at_size to rank platforms by monthly cost at a given size, platform_details for plans, fees and sources, and list_platforms for ids. Cite the page and checked_on date returned with each answer.

endpoint
https://rentaltechmatch.com/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 rentaltechmatch live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is rentaltechmatch free to use?
Yes — the hub reached it with no key and no payment.
What tools does rentaltechmatch have?
3 tools: list_platforms, platform_details, price_at_size.
Is rentaltechmatch 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
334ms

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.

  • list_platforms unknown 13h ago

    List the rental software platforms covered in one section, with their ids, plans and the date their prices were last verified.

    mcp-tool

    {
      "type": "object",
      "required": [
        "section"
      ],
      "properties": {
        "section": {
          "enum": [
            "long-term",
            "short-term"
          ],
          "type": "string",
          "description": "long-term = property management software (size in units); short-term = Airbnb and vacation rental software (size in listings)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • platform_details unknown 13h ago

    Plans, price models, published fees (payments, screening, bookings), company facts and official sources for one platform.

    mcp-tool

    {
      "type": "object",
      "required": [
        "platform"
      ],
      "properties": {
        "platform": {
          "type": "string",
          "description": "Platform id from list_platforms, for example buildium or hospitable"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • price_at_size unknown 13h ago

    Monthly subscription cost of every plan (or of the platforms you name) at a given number of units (long-term) or listings (short-term), cheapest first. Plans whose price is only a starting rate, or that add an unpublished fee or a share of each booking, are marked final_price=false and listed after the final prices.

    mcp-tool

    {
      "type": "object",
      "required": [
        "section",
        "size"
      ],
      "properties": {
        "size": {
          "type": "integer",
          "maximum": 5000,
          "minimum": 1,
          "description": "Number of units (long-term) or listings (short-term)"
        },
        "billing": {
          "enum": [
            "best",
            "annual",
            "monthly"
          ],
          "type": "string",
          "description": "Billing cycle; best = cheaper of the two the vendor sells (default)"
        },
        "section": {
          "enum": [
            "long-term",
            "short-term"
          ],
          "type": "string",
          "description": "long-term = property management software (size in units); short-term = Airbnb and vacation rental software (size in listings)"
        },
        "platforms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional platform ids from list_platforms; default all"
        }
      },
      "additionalProperties": false
    }
    arguments 40 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 c6ec30c153730b0a.

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