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.

Pikes Peak Trip Planner

REMOTE · PIKESPEAK.INFO · 2 COMPONENTS

Plan a Pikes Peak day: timed-entry permit, gate hours, live road status, costs, hike times, facts.

+3 this week 75 Trust /100

Last scanned (16 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1727 tokens (~345/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 Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 69

    First indexed and scored.

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://pikespeak.info/mcp?src=mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pikespeak.info CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 f91099ebf3c540c8132617d484355511
SANs: pikespeak.info
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pikespeak.info. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
info. DS published 9986 8 Verified
pikespeak.info. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pikespeak.info/mcp?src=mcp Verified 200
http (plaintext) http://pikespeak.info/mcp?src=mcp HTTPS enforced 301 https://pikespeak.info/mcp?src=mcp
MCP tools · 5 exposed · ~1,498 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
compare_pikes_peak_costs ~297

Use this when someone asks what it costs for their group to go up Pikes Peak, or whether driving the Highway, the Highway shuttle or the Cog Railway is cheaper: Highway admission per person or per carload, timed-entry permits, shuttle fares and Cog Railway fares for adults, teens, children and under-6s across one or more vehicles on a date. Uses the official 2026 rate sheets and the railway's online fares. Example questions: "How much is it for 2 adults and 3 kids to drive Pikes Peak?", "Is the Cog Railway or driving cheaper for a family of four?", "Pikes Peak Highway price for 7 people in 2 cars". No tour or hotel prices.

NameTypeReqDescription
adultsinteger–People 16 and older (default 2).
datestring–Date in Colorado: YYYY-MM-DD, "today" or "tomorrow" (default today).
kids_6_12integer–Aged 6 to 12.
seats_per_vehicleinteger–Seats per vehicle (default 5).
teens_13_15integer–Aged 13 to 15 (child on the Highway, adult on the Cog).
under_6integer–Aged 5 and under (free on the Highway).
vehiclesinteger–Vehicles the group drives in (default 1).
NameTypeReqDescription
assumptionsstringyes–
cheapest–––
datestringyes–
disclaimerstringyes–
fitsbooleanyes–
groupobjectyes–
linkstringyes–
optionsarrayyes–
rates_usedobject––
saving_vs_next_usdnumber––
seasonstringyes–
timed_entry_permitbooleanyes–

No examples provided.

hike_time ~321

Use this when someone asks how long it takes to hike Pikes Peak on the Barr Trail or to climb the Manitou Incline, what time to start to be off the summit by noon, or how the Incline reservation works. Barr Trail: hours up and down from the real trail profile by pace (strong, average, relaxed) and acclimatisation, Barr Camp and treeline times, summit time for a start time, latest start for a noon summit. Manitou Incline: time up and down, the published typical time, hours, the free reservation and when a date opens for booking. Example questions: "How long does it take to hike Pikes Peak?", "What time should I start the Barr Trail to summit by noon?", "How long is the Manitou Incline and do I need a reservation?".

NameTypeReqDescription
datestring–Optional hike date YYYY-MM-DD, "today" or "tomorrow"; for the Incline it sets the hours and the reservation release.
from_sea_levelboolean–Not acclimatised to altitude (15% slower above 10,000 ft on the Barr Trail, on the whole Incline).
pacestring–Hiking pace: strong, average (default) or relaxed.
start_timestring–Barr Trail: HH:MM trailhead start, 24-hour (optional).
trailstring–barr_trail (default) = Barr Trail to the summit; manitou_incline = the Incline steps in Manitou Springs.
NameTypeReqDescription
disclaimerstringyes–
down_hoursnumberyes–
down_textstringyes–
linkstringyes–
methodstringyes–
pacestringyes–
trailstringyes–
up_hoursnumberyes–
up_textstringyes–

No examples provided.

pikes_peak_conditions ~180

Use this when someone asks whether Pikes Peak or the Pikes Peak Highway is open today or right now, how far up the road is open (e.g. only to mile 13 Glen Cove after snow), today's gate hours, or the weather on Pikes Peak in the next days. Reads the City of Colorado Springs "Open to" status line from drivepikespeak.com (cached 15 minutes, with the time it was read) and the National Weather Service forecast for the summit-area grid. Example questions: "Is Pikes Peak open today?", "Can I drive to the top of Pikes Peak right now?", "What is the weather on Pikes Peak this weekend?". Not for the rules of a future date.

NameTypeReqDescription
forecast_daysinteger–Days of forecast to return, day and night periods (default 2).
NameTypeReqDescription
closure_today–––
disclaimerstringyes–
forecastarrayyes–
forecast_sourcestringyes–
gate_hours_today–––
linksobjectyes–
road–yes–
road_notestringyes–
todaystringyes–

No examples provided.

pikes_peak_facts ~218

Use this when someone asks a factual question about Pikes Peak, the Pikes Peak Highway, the Cog Railway, the Barr Trail, the Manitou Incline, Garden of the Gods, the Summit Visitor Center, the Pikes Peak International Hill Climb, the Pikes Peak Marathon and Ascent, or history: elevation, distances, fees, hours, rules, parking, records, opening dates. Returns matching facts with value, unit, source URL and the date the source was checked. Example questions: "How tall is Pikes Peak?", "How many steps is the Manitou Incline?", "Is Garden of the Gods free?", "When is the Pikes Peak Hill Climb?". Not for a date-specific plan.

NameTypeReqDescription
limitinteger–Maximum facts (default 10).
querystring–Words to look for, e.g. "summit elevation", "timed entry permit", "Incline steps", "Garden of the Gods parking".
topicstring–Optional topic filter.
NameTypeReqDescription
countnumberyes–
disclaimerstringyes–
factsarrayyes–
linkstringyes–
query–––
topic–––

No examples provided.

plan_pikes_peak_day ~482

Use this when someone plans a day on Pikes Peak (Colorado) and wants to know what applies to their date and way up: drive the Pikes Peak Highway (car), the Highway shuttle from mile 7, the Pikes Peak Cog Railway, or hiking the Barr Trail. Returns whether a timed-entry permit or reservation is needed on that date, Highway gate opening, last-entry and summit-closing times, closures (holidays, Hill Climb race day), a timeline from leaving the start point to being back with the noon thunderstorm cutoff in June to September, snow-season turnaround points, summit sunrise and sunset, what to book in which order (official ticket pages first), sold-out fallbacks (tours that include the ride up, with partner links) and a link that opens the plan in the pikespeak.info planner. Example questions: "Do I need a reservation to drive Pikes Peak on July 4?", "Help me plan a Pikes Peak trip next Saturday by Cog Railway with kids", "What time should we leave Denver to drive up Pikes Peak in October?". Not for live road status or group prices.

NameTypeReqDescription
datestring–Date in Colorado: YYYY-MM-DD, "today" or "tomorrow" (default today).
from_sea_levelboolean–Coming from near sea level, not acclimatised (adds altitude advice and slows the hike).
start_timestring–HH:MM, 24-hour: arrival at the Highway gate (car, shuttle), train departure (cog) or trailhead start (hike). Default: gate opening, 08:00 train, 03:30 trailhead.
starting_pointstring–Optional start for driving times: manitou = Manitou Springs (town centre), cos = Downtown Colorado Springs, cos_airport = Colorado Springs Airport (COS), denver = Downtown Denver, den_airport = Denve…
waystringyescar = drive the Pikes Peak Highway yourself (default), shuttle = drive to the mile 7 lot and ride the Highway shuttle, cog = Pikes Peak Cog Railway from Manitou Springs, hike = Barr Trail on foot.
with_kidsboolean–Children in the group (adds family notes).
NameTypeReqDescription
bookarrayyes–
branch–––
closed–––
datestringyes–
disclaimerstringyes–
gate–––
notesarrayyes–
permitstring––
planner_linkstringyes–
startstringyes–
stepsarrayyes–
sun–––
tours–––
verdictsarrayyes–
waystringyes–
way_labelstringyes–

No examples provided.

Install

How do I install the Pikes Peak Trip Planner MCP server?

Pikes Peak Trip Planner is a hosted endpoint at https://pikespeak.info/mcp?src=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 · pikespeak.info

# add to Claude Code
claude mcp add --transport http info-pikespeak-pikes-peak-trip-planner 'https://pikespeak.info/mcp?src=mcp'
Common questions

What is the Pikes Peak Trip Planner MCP server?

Pikes Peak Trip Planner is an MCP server listed in the public MCP registry as info.pikespeak/pikes-peak-trip-planner. Plan a Pikes Peak day: timed-entry permit, gate hours, live road status, costs, hike times, facts. This page covers its hosted endpoint (https://pikespeak.info/mcp?src=mcp).

Is the Pikes Peak Trip Planner MCP server safe to use?

Pikes Peak Trip Planner scores 75 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 Pikes Peak Trip Planner MCP server expose?

Pikes Peak Trip Planner exposes 5 tools: plan_pikes_peak_day, pikes_peak_conditions, compare_pikes_peak_costs, hike_time, pikes_peak_facts. Their descriptions and schemas cost roughly 1,498 tokens of context every time the server is loaded.

Does the Pikes Peak Trip Planner MCP server require authentication?

No. We connected to Pikes Peak Trip Planner without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pikes Peak Trip Planner MCP server still maintained?

Pikes Peak Trip Planner 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 Pikes Peak Trip Planner MCP server?

VerifyMCP ran 13 checks on Pikes Peak Trip Planner, 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.