Remote MCP · Endpoint

eightytwenty MCP server

No. eightytwenty answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.eightytwenty.tech/mcp

The last check completed an MCP handshake.

Registry name
io.github.h3692/eightytwenty
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
273 ms
Tools exposed
5 tools
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Builds case-competition and pitch decks in PowerPoint from the layouts behind winning decks.
Listing
From the official MCP registry (active).
Recent checks of eightytwenty
CheckedResultHandshake
5 hours agoHandshake completed273 ms
4 days agoHandshake completed487 ms
7 days agoHandshake completed310 ms

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

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