Remote MCP · Endpoint

Into the Prompt MCP server

No. Into the Prompt answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://intotheprompt.com/mcp

The last check completed an MCP handshake.

Registry name
com.intotheprompt/into-the-prompt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.04 s
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search Into the Prompt's short AI videos, get a learning path and see how the creator program works.
Listing
From the official MCP registry (active).
Recent checks of Into the Prompt
CheckedResultHandshake
34 minutes agoHandshake completed1.04 s
9 days agoHandshake completed1.05 s
10 days agoHandshake completed1.57 s
11 days agoHandshake completed1.26 s
12 days agoHandshake completed1.07 s
14 days agoHandshake completed1.11 s
14 days agoHandshake completed921 ms
15 days agoHandshake completed2.50 s
17 days agoHandshake completed1.54 s
19 days agoHandshake completed1.09 s
21 days agoHandshake completed977 ms
24 days agoHandshake completed525 ms
26 days agoHandshake completed598 ms
28 days agoHandshake completed445 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 Into the Prompt and makes no claim about it beyond what these checks measured.