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

okc-property-check

https://okc-property-check.onrender.com

Registry code: 6a8e979f227ac13a

api record

Oklahoma City small-commercial deal check. okc_flip_math says whether a flip works at the asking price, is close, or is too rich on OKC hard-money terms, and returns a link to the paid OKC Flip Report with the exact max modeled price. Results are estimates, not advice.

endpoint
https://okc-property-check.onrender.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 okc-property-check live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is okc-property-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does okc-property-check have?
1 tool: okc_flip_math.
Is okc-property-check 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
377ms

last good check

priced tools
0

of 1 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 1 tools
1 never probed 0 of 1 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.

  • okc_flip_math unknown 1h ago

    Free deal check for an Oklahoma City small-commercial flip: says whether it works at the asking price, is close, is too rich, or works at no price, on OKC hard-money terms (75% of price at 11% plus 2 points, 2% buy closing, 7% sale costs, $1,000/month carry unless given, minimum 5-month hold, 12% profit-on-cost target). It does not return the max modeled price; it returns a link where the person can buy the full OKC Flip Report (exact max modeled price, break-even, price ladder, what-if checks, cost sheet) with the deal already filled in. Give exit_value, or annual_noi and cap_rate.

    mcp-tool

    {
      "type": "object",
      "required": [
        "asking_price"
      ],
      "properties": {
        "address": {
          "type": "string",
          "description": "Optional address, for your own reference."
        },
        "cap_rate": {
          "type": "number",
          "description": "With annual_noi: the cap rate as a decimal, e.g. 0.085."
        },
        "annual_noi": {
          "type": "number",
          "description": "Alternative to exit_value: stabilized yearly net operating income, USD."
        },
        "exit_value": {
          "type": "number",
          "description": "Expected sale price after the work, USD. Base it on sold comps."
        },
        "building_sf": {
          "type": "number",
          "description": "Optional building square feet, for per-square-foot figures."
        },
        "hold_months": {
          "type": "number",
          "description": "Months from contract to resale. Default 6, minimum 5."
        },
        "reno_budget": {
          "type": "number",
          "description": "Renovation budget, USD. Default 0."
        },
        "asking_price": {
          "type": "number",
          "description": "Asking or purchase price, USD."
        },
        "notify_email": {
          "type": "string",
          "description": "Optional. Leave an email if the person wants Dark Matter Syndicate to follow up about this deal. Only stored if given."
        },
        "carry_per_month": {
          "type": "number",
          "description": "Taxes, insurance, utilities per month while held. Default 1000."
        }
      },
      "additionalProperties": false
    }
    arguments 49 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 6a8e979f227ac13a.

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

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.