Remote MCP · Endpoint

Fiveable for AP Teachers MCP server

No. Fiveable for AP Teachers answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fiveable.me/api/mcp/teacher

The last check completed an MCP handshake.

Registry name
io.github.thinkfiveable/fiveable-ap-teachers
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
276 ms
Tools exposed
77 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AP rubric grading, assignment drafts, question-bank materials, and class insights for teachers.
Listing
From the official MCP registry (active).
Recent checks of Fiveable for AP Teachers
CheckedResultHandshake
1 hour agoHandshake completed276 ms
2 days agoHandshake completed321 ms
4 days agoHandshake completed220 ms
7 days agoHandshake completed265 ms
9 days agoHandshake completed190 ms
11 days agoHandshake completed460 ms
13 days agoHandshake completed478 ms
15 days agoHandshake completed184 ms
16 days agoHandshake completed190 ms
18 days agoHandshake completed179 ms
19 days agoHandshake completed477 ms
20 days agoHandshake completed243 ms
23 days agoHandshake completed404 ms
24 days agoHandshake completed404 ms

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

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 Fiveable for AP Teachers and makes no claim about it beyond what these checks measured.