Remote MCP · Endpoint

BC Curriculum MCP server

No. BC Curriculum answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://bc-curriculum-mcp.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.pdg6/bc-curriculum
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Query the full BC K-12 curriculum: Big Ideas, Competencies, Content, and more.
Listing
From the official MCP registry (active).
Recent checks of BC Curriculum
CheckedResultHandshake
2 days agoHandshake completed49 ms
4 days agoHandshake completed48 ms
5 days agoHandshake completed52 ms
7 days agoHandshake completed86 ms
8 days agoHandshake completed60 ms
9 days agoHandshake completed77 ms
12 days agoHandshake completed58 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed56 ms
17 days agoHandshake completed62 ms
18 days agoHandshake completed2.81 s
19 days agoHandshake completed64 ms
20 days agoHandshake completed79 ms
20 days agoHandshake completed55 ms
21 days agoHandshake completed56 ms
23 days agoHandshake completed3.14 s

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with BC Curriculum and makes no claim about it beyond what these checks measured.