_ registry / mcp http-sse · checked 42m ago

904-booking-hub/904-digital-media

https://book.weare904digitalmedia.com

Registry code: 3c03733ab81ad3cf

api record

This is 904 Digital Media's booking line for AI assistants, run by the 904 Booking Hub. Use list_services, then get_availability, then request_booking to ask 904 Digital Media for a time on a customer's behalf, or request_callback when the customer would rather talk first. Every request waits for 904 Digital Media to confirm it: nothing here books a confirmed appointment, and no payment is ever taken here.

endpoint
https://book.weare904digitalmedia.com/api/mcp/904-digital-media
protocol
http-sse ·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 904-booking-hub/904-digital-media live?
Yes — it answered the hub's last check (checked 42m ago). It answered 100% of checks over the last 30 days.
Is 904-booking-hub/904-digital-media free to use?
Yes — the hub reached it with no key and no payment.
What tools does 904-booking-hub/904-digital-media have?
4 tools: get_availability, request_booking, request_callback, list_services.
Is 904-booking-hub/904-digital-media 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.4%· all time 99.4%

latency
493ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 350 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • list services of a media agency
  • get open appointment times
  • request a booking
  • request a callback
takes → gives
text, data → data
tools
2 reads2 sends messages
_ 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 4 tools
1 open 3 never probed 1 of 4 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_services reads open 14h ago

    List the services 904 Digital Media offers, with each one's id, length, price (when 904 Digital Media shows one), where it happens (phone, video, at the customer's address, or at 904 Digital Media), and any questions 904 Digital Media asks when booking it. A service marked bookable_by_assistant: false takes a deposit or payment, saves a card, is a class or a plan, or needs a file upload; it cannot be requested here, and booking_page is 904 Digital Media's own page where the customer can book it themselves. Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_availability reads unknown 14h ago

    Open start times for one 904 Digital Media service, read from 904 Digital Media's live calendar. Pass service_id from list_services. Optional from and to: a date (YYYY-MM-DD, read in 904 Digital Media's time zone; a to date includes that whole day) or a date-time with its offset (e.g. 2026-10-06T09:00:00-04:00). The default is the next 7 days and the most is 14; the window actually searched is returned as window. Returns up to 50 times, each as an exact start (pass it unchanged to request_booking) and as local time in 904 Digital Media's time zone; when there are more, more is true and next_from is where to continue. Times are not held: request_booking checks again. Read-only.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "service_id"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Latest time: a date (that whole day is included) or a date-time with its offset. Default: 7 days after from; at most 14."
        },
        "from": {
          "type": "string",
          "description": "Earliest time: a date (YYYY-MM-DD, in the business's time zone) or a date-time with its offset. Default: now."
        },
        "staff_id": {
          "type": "string",
          "description": "Only this person's times (a staff id from list_services)."
        },
        "service_id": {
          "type": "string",
          "description": "The service's id from list_services."
        }
      }
    }
    arguments 25 lines
  • request_booking sends messages unknown never probed

    Send 904 Digital Media a booking REQUEST for one appointment on the customer's behalf. Nothing is confirmed until 904 Digital Media confirms it. Use a start from get_availability. Needs the customer's name, phone and email (904 Digital Media emails the customer when it confirms, declines or suggests another time), answers to any required questions from list_services (by question id), and the street address when the service happens at the customer's address. No payment is taken here. What happens next: 904 Digital Media is notified right away and the customer gets an email saying the request was received, then another when 904 Digital Media answers. If the customer will not share an email, use request_callback instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "service_id",
        "start",
        "name",
        "phone"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The customer's full name."
        },
        "email": {
          "type": "string",
          "description": "The customer's email. 904 Digital Media sends the confirmation here, so a booking request needs it."
        },
        "notes": {
          "type": "string",
          "description": "Anything the customer wants 904 Digital Media to know (up to 1000 characters)."
        },
        "phone": {
          "type": "string",
          "description": "The customer's US phone number: 10 digits with area code, no extension."
        },
        "start": {
          "type": "string",
          "description": "The exact start from get_availability (ISO 8601 date-time with offset), unchanged."
        },
        "address": {
          "type": "string",
          "description": "The full street address, when the service happens at the customer's address."
        },
        "answers": {
          "type": "object",
          "description": "Answers to the service's questions from list_services, keyed by question id. For a checklist question (pick: \"any\"), send only the options that apply, joined with \"; \".",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "type": "string"
          }
        },
        "staff_id": {
          "type": "string",
          "description": "A particular person from list_services. Leave out to let the business assign someone."
        },
        "service_id": {
          "type": "string",
          "description": "The service's id from list_services."
        }
      }
    }
    arguments 54 lines
  • request_callback sends messages unknown never probed

    Ask 904 Digital Media to call the customer back. Use it when the customer wants to talk first, has no email, or no listed time suits. Needs the customer's name, phone and a short reason. What happens next: 904 Digital Media is alerted right away and calls the customer back. Nothing is booked, and nothing is texted or emailed to the customer from here.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "name",
        "phone",
        "reason"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The customer's name."
        },
        "phone": {
          "type": "string",
          "description": "The US number 904 Digital Media should call: 10 digits with area code, no extension."
        },
        "reason": {
          "type": "string",
          "description": "What the customer wants to talk about, in a sentence (up to 1000 characters)."
        }
      }
    }
    arguments 23 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 3c03733ab81ad3cf.

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

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.