Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Junely — Colorado Kids’ Camps & After-School

REMOTE · JUNELY.CO

Daily-verified Colorado kids' camps & after-school programs: real availability, ages, prices.

Available components

0 this week 83 Trust /100

Last scanned (17 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 997 tokens (~199/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_programs” rewrote its description, which is the text the model reads security
    • “search_programs” reworded the description of “region” cosmetic
  • 13 Nov 26 0
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://junely.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=junely.co CN=YR2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 6b881bc964768b3e62d2bc990a8de50b334
SANs: junely.co
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of junely.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
junely.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; form-action 'self'; frame-ancestors 'none'; script-src 'self' 'unsafe-inline' https://*.posthog.com; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https://*.tile.openstreetmap.org https://*.googleusercontent.com https://*.posthog.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://*.posthog.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(self), camera=(), microphone=(), browsing-topics=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://junely.co/mcp Verified 200
http (plaintext) http://junely.co/mcp HTTPS enforced 308 https://junely.co/mcp
MCP tools · 5 exposed · ~663 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_program_details ~59

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.

NameTypeReqDescription
idstringyesProgram id from a search result

No output schema declared.

No examples provided.

save_camp ~83

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.

NameTypeReqDescription
idstringyesProgram id from a search result

No output schema declared.

No examples provided.

search_programs ~308

Search Junely’s catalog of kids’ summer camps and after-school programs (coverage today: Colorado and Texas), 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.

NameTypeReqDescription
ageinteger–Child’s age in years
categorystring–Category, e.g. STEM, Sports, Arts, Outdoors, Academic
limitinteger–Max results (default 10)
max_pricenumber–Maximum price in USD
monthstring–Month the program should run, e.g. "July" or "7"
open_onlyboolean–Only programs currently open for registration (default false)
querystring–Free-text interest, e.g. "robotics", "horseback riding", "Russian language"
regionstring–Region or city where Junely has listings (today: Colorado and Texas), e.g. "Denver", "Boulder", "Colorado Springs", "Dallas", "Houston", "Austin", "San Antonio"
verticalstring–Camps (default) or after-school programs

No output schema declared.

No examples provided.

watch_program ~75

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.

NameTypeReqDescription
idstringyesProgram id from a search result

No output schema declared.

No examples provided.

whats_open ~138

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.

NameTypeReqDescription
ageinteger––
categorystring––
limitinteger––
regionstring––
verticalstring––

No output schema declared.

No examples provided.

Install

How do I install the Junely — Colorado Kids’ Camps & After-School MCP server?

Junely — Colorado Kids’ Camps & After-School is a hosted endpoint at https://junely.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · junely.co

# add to Claude Code
claude mcp add --transport http co-junely-junely 'https://junely.co/mcp'
Common questions

What is the Junely — Colorado Kids’ Camps & After-School MCP server?

Junely — Colorado Kids’ Camps & After-School is an MCP server listed in the public MCP registry as co.junely/junely. Daily-verified Colorado kids' camps & after-school programs: real availability, ages, prices. This page covers its hosted endpoint (https://junely.co/mcp).

Is the Junely — Colorado Kids’ Camps & After-School MCP server safe to use?

Junely — Colorado Kids’ Camps & After-School scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Junely — Colorado Kids’ Camps & After-School MCP server expose?

Junely — Colorado Kids’ Camps & After-School exposes 5 tools: search_programs, get_program_details, whats_open, save_camp, watch_program. Their descriptions and schemas cost roughly 663 tokens of context every time the server is loaded.

Does the Junely — Colorado Kids’ Camps & After-School MCP server require authentication?

No. We connected to Junely — Colorado Kids’ Camps & After-School without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Junely — Colorado Kids’ Camps & After-School MCP server still maintained?

Junely — Colorado Kids’ Camps & After-School is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Junely — Colorado Kids’ Camps & After-School MCP server?

VerifyMCP ran 13 checks on Junely — Colorado Kids’ Camps & After-School, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.