Remote MCP · Endpoint

Automate America MCP server

No. Automate America answered an MCP handshake 12 hours ago.

UpLast checked 12 hours ago

Server URL

https://automateamerica.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.automateamerica/automate-america
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.00 s
Tools exposed
Not measured yet
Uptime, last 30 days
3 checks from 3 checks
Described by its publisher as
Find skilled professionals and open work, and act for a member with their consent.
Listing
From the official MCP registry (active).
Recent checks of Automate America
CheckedResultHandshake
12 hours agoHandshake completed1.00 s
4 days agoHandshake completed39 ms
7 days agoHandshake completed34 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 Automate America and makes no claim about it beyond what these checks measured.