Remote MCP · Endpoint

MatchAwards MCP server

No. MatchAwards answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://matchawards.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.matchawards/matchawards-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
64 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search US government contracts, grants and jobs from matchawards.com. Read-only, no key.
Listing
From the official MCP registry (active).
Recent checks of MatchAwards
CheckedResultHandshake
7 hours agoHandshake completed64 ms
12 hours agoHandshake completed88 ms
2 days agoHandshake completed120 ms
4 days agoHandshake completed84 ms
7 days agoHandshake completed79 ms
9 days agoHandshake completed62 ms
11 days agoHandshake completed98 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed89 ms
18 days agoHandshake completed159 ms
20 days agoHandshake completed145 ms
21 days agoHandshake completed144 ms
23 days agoHandshake completed102 ms

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

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