Remote MCP · Endpoint

Permit Scouter MCP server

No. Permit Scouter answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.permitscouter.com/mcp

The last check completed an MCP handshake.

Registry name
com.permitscouter/permits
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Daily Tampa Bay, Southwest and Central Florida permits with job value and contractor. Pay via x402.
Listing
From the official MCP registry (active).
Recent checks of Permit Scouter
CheckedResultHandshake
3 hours agoHandshake completed55 ms
9 days agoHandshake completed48 ms
10 days agoHandshake completed57 ms
11 days agoHandshake completed68 ms
12 days agoHandshake completed42 ms
14 days agoHandshake completed51 ms
14 days agoHandshake completed55 ms
15 days agoHandshake completed49 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed49 ms
21 days agoHandshake completed44 ms
24 days agoHandshake completed58 ms
26 days agoHandshake completed47 ms
28 days agoHandshake completed47 ms

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