_ registry / mcp + a2a streamable-http · checked 2h ago

net.duffergolf/catalog

https://duffergolf.net

Registry code: bf724afbcefc491e

api record

Read-only facts about Duffer Golf's golf simulator enclosures, from duffergolf.net: the four models and prices, whether a room fits, the FAQ, dealers and how to reach Tate. No tool orders, reserves, pays or sends a message; send people to the page links in the results for that.

endpoint
https://duffergolf.net/mcp
door code
2a1bba33dc219186
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 net.duffergolf/catalog live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is net.duffergolf/catalog free to use?
Yes — the hub reached it with no key and no payment.
What tools does net.duffergolf/catalog have?
5 tools: check_fit, get_faq, contact_info, list_models, find_dealers.
Is net.duffergolf/catalog 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
258ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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

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

  • contact_info open 2h ago

    How to reach Duffer Golf: email, where it is, how fast Tate answers, and the links to the contact, reserve, shop and checkout pages. Read-only: it does not send a message or place an order.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_models open 2h ago

    The four Duffer Golf folding golf simulator enclosures (Duffer 8 and Duffer 10, each as a System or a Complete): delivered price in US dollars, what each one includes, enclosure and room dimensions in inches, build and ship times, warranty, installation and financing. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • find_dealers open 2h ago

    Approved Duffer dealers (shops that sell it, offer local pickup or install it), optionally only those located in or serving one US state. With no dealer nearby, Duffer Golf sells direct and ships to every state. Read-only.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "state": {
          "type": "string",
          "maxLength": 40,
          "description": "A US state as a two-letter code (KS) or its name (Kansas). Omit for every dealer."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • check_fit unknown never probed

    Will a Duffer fit a room? Give the room's width, depth and ceiling height in whole inches. Returns the verdict the duffergolf.net fit checker shows (fits, tight, ask or no), the same verdict for each model, and which number is short. Read-only: it sends nothing to anyone.

    mcp-tool

    {
      "type": "object",
      "required": [
        "width_in",
        "depth_in",
        "ceiling_in"
      ],
      "properties": {
        "depth_in": {
          "type": "integer",
          "maximum": 1199,
          "minimum": 1,
          "description": "Room depth in inches, front to back from the wall it folds against."
        },
        "width_in": {
          "type": "integer",
          "maximum": 1199,
          "minimum": 1,
          "description": "Room width in inches, wall to wall where the bay would stand."
        },
        "ceiling_in": {
          "type": "integer",
          "maximum": 1199,
          "minimum": 1,
          "description": "Ceiling height in inches, to the lowest beam, duct or door track over that spot."
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • get_faq unknown never probed

    Duffer Golf's FAQ, answered by Tate Mauck, who builds them. Pass query to keep only entries that share a word with it (case-insensitive, best matches first); omit it for every entry.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "Words to look for, e.g. \"warranty\" or \"left handed\"."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
_ try it over mcp 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 bf724afbcefc491e.

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

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
2
ok
0
failed
2
success rate
0%
median latency
86ms
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
—

2 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.