Remote MCP · Endpoint

American Samoa Code MCP server

No. American Samoa Code answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/american-samoa-code/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/american-samoa-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
258 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
American Samoa Code Annotated (A.S.C.A.) — section lookup by citation and topic/keyword search…
Listing
From the official MCP registry (active).
Recent checks of American Samoa Code
CheckedResultHandshake
1 hour agoHandshake completed258 ms
1 day agoHandshake completed479 ms
2 days agoHandshake completed118 ms
2 days agoHandshake completed578 ms
4 days agoHandshake completed407 ms
7 days agoHandshake completed176 ms
9 days agoHandshake completed69 ms
12 days agoHandshake completed69 ms
14 days agoHandshake completed72 ms
16 days agoHandshake completed224 ms
18 days agoHandshake completed1.44 s
20 days agoHandshake completed1.74 s
22 days agoHandshake completed1.00 s
24 days agoHandshake completed1.14 s

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