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

junely

https://junely.co

Registry code: 4a9f5682c6086714

api record

Junely catalogs kids’ summer camps and after-school programs (coverage today: Colorado; Texas listings are not in this catalog yet), checked against each provider’s own page — never re-verified on a blanket daily schedule. For Texas, https://junely.co/tx/summer-camps/registration-dates has Junely’s summer camp registration dates. Every listing starts from its captured extraction date (can be weeks old). live_verified is an additional, per-row signal, and it means different things by vertical: for after-school programs, live_verified:true means Junely re-checked that program’s own page today…

endpoint
https://junely.co/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 junely live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is junely free to use?
Yes — the hub reached it with no key and no payment.
What tools does junely have?
5 tools: save_camp, get_program_details, watch_program, search_programs, whats_open.
Is junely 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
98.9%

90 days 98.1%· all time 98.1%

latency
641ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 477 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • search kids summer camps in colorado
  • find programs open for registration
  • get camp program details
  • save a camp to a watchlist
  • set a camp closing alert
takes → gives
text → data
tools
3 reads2 changes data
_ 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
2 open 3 never probed 2 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.

  • search_programs reads open 24h ago

    Search Junely’s catalog of kids’ summer camps and after-school programs (coverage today: Colorado), checked against each provider’s own page. Filter by child age, month, region, category, price, and open availability. Freshness is per row, not daily: every result starts from its captured extraction date (can be weeks old); live_verified additionally means Junely re-checked that program’s own page today for after-school listings, or confirmed plausible status/dates at last capture for camp listings — it is not proof every listing was checked today.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "age": {
          "type": "integer",
          "maximum": 18,
          "minimum": 2,
          "description": "Child’s age in years"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "month": {
          "type": "string",
          "description": "Month the program should run, e.g. \"July\" or \"7\""
        },
        "query": {
          "type": "string",
          "description": "Free-text interest, e.g. \"robotics\", \"horseback riding\", \"Russian language\""
        },
        "region": {
          "type": "string",
          "description": "Region or city where Junely has listings (today: Colorado), e.g. \"Denver\", \"Boulder\", \"Colorado Springs\""
        },
        "category": {
          "type": "string",
          "description": "Category, e.g. STEM, Sports, Arts, Outdoors, Academic"
        },
        "vertical": {
          "enum": [
            "camps",
            "afterschool"
          ],
          "type": "string",
          "description": "Camps (default) or after-school programs"
        },
        "max_price": {
          "type": "number",
          "description": "Maximum price in USD"
        },
        "open_only": {
          "type": "boolean",
          "description": "Only programs currently open for registration (default false)"
        }
      }
    }
    arguments 49 lines
  • whats_open reads open 24h ago

    Programs currently OPEN for registration, most recently updated first — Junely’s honesty signal. Freshness is per row, not a blanket re-check: live_verified means Junely re-checked that program’s own page today for after-school listings; for camps it only reflects the status/dates captured at last extraction, not a same-day check. Rows without live_verified reflect their captured extraction date, which can be weeks old. Optional filters: region, category, age, vertical.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "age": {
          "type": "integer",
          "maximum": 18,
          "minimum": 2
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1
        },
        "region": {
          "type": "string"
        },
        "category": {
          "type": "string"
        },
        "vertical": {
          "enum": [
            "camps",
            "afterschool"
          ],
          "type": "string"
        }
      }
    }
    arguments 28 lines
  • save_camp changes data unknown never probed

    Saves a program to the signed-in user’s Junely watchlist. NOTE: saving also arms spot-opening/status-change email alerts for that program — identical to tapping ★ on junely.co. Only call when the user explicitly asks to save/track a program. Requires connecting the user’s Junely account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Program id from a search result"
        }
      }
    }
    arguments 12 lines
  • get_program_details reads unknown 24h ago

    Full details for a single program by its Junely id (from search results): description, dates, ages, price, current enrollment status, and the provider’s info + registration links.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Program id from a search result"
        }
      }
    }
    arguments 12 lines
  • watch_program changes data unknown never probed

    Sets a fills-up/closing email alert for one program on the signed-in user’s Junely account — identical to the “alert me” button on junely.co. Only call when the user explicitly asks to be alerted. Requires connecting the user’s Junely account.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Program id from a search result"
        }
      }
    }
    arguments 12 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 4a9f5682c6086714.

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