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

okc-custom-home-readiness-planner

https://okcluxuryhomeplanner.com

Registry code: 1df7ec13cb00c6e0

api record

Use run_readiness_planner to evaluate a custom-home or remodel project and receive a Project Readiness Brief. Use get_readiness_planner_meta for accepted inputs and pathways, and get_business_info for Cosmopolitan Company contact details. All output is educational, illustrative planning information only — not professional advice or a binding commitment.

endpoint
https://okcluxuryhomeplanner.com/api/mcp
protocol
streamable-http ·2024-11-05
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-custom-home-readiness-planner live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is okc-custom-home-readiness-planner free to use?
Yes — the hub reached it with no key and no payment.
What tools does okc-custom-home-readiness-planner have?
3 tools: run_readiness_planner, get_readiness_planner_meta, get_business_info.
Is okc-custom-home-readiness-planner 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.7%· all time 99.7%

latency
572ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 383 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • evaluate custom home project readiness
  • get planner inputs
  • get home builder contact info
takes → gives
data → data, text
tools
3 reads
_ 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

_ what it can do 3 tools
2 open 1 never probed 2 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.

  • get_readiness_planner_meta reads open 23h ago

    Returns metadata describing the readiness planner: its purpose, the assessment sections, the seven possible pathways, the six readiness dimensions, expected completion time, and the educational-use disclaimer.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_business_info reads open 23h ago

    Returns approved public business information for Cosmopolitan Company: name, website, phone, email, address, description, and service areas across the Oklahoma City metro.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • run_readiness_planner reads unknown never probed

    Evaluates a custom-home or major-remodel project across six readiness dimensions and returns a personalized Project Readiness Brief. Accepts normalized assessment answers (q1-q24) and returns the likely project pathway, what appears aligned vs. what needs attention, property/site risk considerations, budget and scope considerations, builder and proposal questions, technology and resilience priorities, recommended next actions, and documents to gather. Educational, illustrative planning output only — not a construction quote, price guarantee, engineering/architectural/code/legal opinion, or binding estimate.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q1": {
          "type": "string",
          "description": "Project path / decision that best describes the user today (e.g. \"Build a new custom home\")."
        },
        "q2": {
          "type": "string",
          "description": "Project location within the OKC metro."
        },
        "q3": {
          "type": "string",
          "description": "Property or site ownership / status."
        },
        "q4": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Site or property conditions and concerns (multi-select)."
        },
        "q5": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Utility, drainage, and access considerations (multi-select)."
        },
        "q6": {
          "type": "string",
          "description": "Timing / decision stage."
        },
        "q7": {
          "type": "string",
          "description": "Decision timeframe."
        },
        "q8": {
          "type": "string",
          "description": "Builder research status."
        },
        "q9": {
          "type": "string",
          "description": "Financing / funding status."
        },
        "q10": {
          "type": "string",
          "description": "Budget range."
        },
        "q11": {
          "type": "string",
          "description": "Home size / scope."
        },
        "q12": {
          "type": "string",
          "description": "Funding readiness."
        },
        "q13": {
          "type": "string",
          "description": "Lifestyle / household need."
        },
        "q14": {
          "type": "string",
          "description": "Aging-in-place / multigenerational need."
        },
        "q15": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Technology and smart-home priorities (multi-select)."
        },
        "q16": {
          "type": "string",
          "description": "Energy / resilience priority."
        },
        "q17": {
          "type": "string",
          "description": "Oklahoma resilience (storm/weather) priority."
        },
        "q18": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Health, comfort, and indoor-air-quality priorities (multi-select)."
        },
        "q19": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Builder proposal / contract considerations (multi-select)."
        },
        "q20": {
          "type": "string",
          "description": "Primary concern."
        },
        "q21": {
          "type": "string",
          "description": "Builder / proposal status."
        },
        "q22": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Documents already gathered (multi-select)."
        },
        "q23": {
          "type": "string",
          "description": "Preferred next step."
        },
        "q24": {
          "type": "string",
          "description": "Additional free-text context (optional)."
        }
      },
      "description": "Assessment answers for the 24-question readiness planner. Provide any subset of q1 through q24. Single-choice questions take a string; multi-select questions (q4, q5, q15, q18, q19, q22) take an array of strings. Call get_readiness_planner_meta for the full list of sections and accepted values.",
      "additionalProperties": true
    }
    arguments 121 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 1df7ec13cb00c6e0.

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