Remote MCP · Endpoint

Proof of Type Input MCP server

No. Proof of Type Input answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.proofoftype.com/mcp

The last check completed an MCP handshake.

Registry name
com.proofoftype/input
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Add a text box that proves a human typed it, not AI. Code for any framework; verify proof tokens.
Listing
From the official MCP registry (active).
Recent checks of Proof of Type Input
CheckedResultHandshake
1 hour agoHandshake completed80 ms
1 day agoHandshake completed97 ms
2 days agoHandshake completed867 ms
3 days agoHandshake completed245 ms
4 days agoHandshake completed93 ms
5 days agoHandshake completed247 ms
6 days agoHandshake completed85 ms
9 days agoHandshake completed179 ms
11 days agoHandshake completed679 ms
14 days agoHandshake completed130 ms
16 days agoHandshake completed98 ms
18 days agoHandshake completed650 ms
20 days agoHandshake completed747 ms
22 days agoHandshake completed805 ms
24 days agoHandshake completed1.51 s

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

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 Proof of Type Input and makes no claim about it beyond what these checks measured.