Remote MCP · Endpoint
Vicinity Agent API MCP server
No. Vicinity Agent API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://www.thevicinityapp.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.thevicinityapp/vicinity-agent-api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 416 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Spatial coordination for AI agents: read nearby activity or post intents; publishing is paid.
- Website
- https://thevicinityapp.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 416 ms |
| 2 days ago | Handshake completed | 200 ms |
| 4 days ago | Handshake completed | 185 ms |
| 5 days ago | Handshake completed | 301 ms |
| 7 days ago | Handshake completed | 386 ms |
| 8 days ago | Handshake completed | 210 ms |
| 9 days ago | Handshake completed | 214 ms |
| 12 days ago | Handshake completed | 309 ms |
| 13 days ago | Handshake completed | 453 ms |
| 15 days ago | Handshake completed | 371 ms |
| 16 days ago | Handshake completed | 520 ms |
| 17 days ago | Handshake completed | 291 ms |
| 19 days ago | Handshake completed | 320 ms |
| 20 days ago | Handshake completed | 355 ms |
| 20 days ago | Handshake completed | 284 ms |
| 21 days ago | Handshake completed | 332 ms |
| 22 days ago | Handshake completed | 311 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Vicinity Agent API and makes no claim about it beyond what these checks measured.