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://thevicinityapp.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.thevicinityapp.www/vicinity-agent-api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 346 ms
- Tools exposed
- 13 tools
- Uptime, last 30 days
- 94.4% from 18 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 (deprecated).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 346 ms |
| 1 day ago | Handshake completed | 303 ms |
| 2 days ago | Handshake completed | 542 ms |
| 3 days ago | Handshake completed | 529 ms |
| 4 days ago | Handshake completed | 284 ms |
| 5 days ago | Handshake completed | 475 ms |
| 6 days ago | Handshake completed | 462 ms |
| 9 days ago | Handshake completed | 916 ms |
| 12 days ago | Handshake completed | 340 ms |
| 14 days ago | Handshake completed | 441 ms |
| 16 days ago | Failed - the response was not JSON-RPC | — |
| 18 days ago | Handshake completed | 385 ms |
| 20 days ago | Handshake completed | 469 ms |
| 22 days ago | Handshake completed | 530 ms |
| 24 days ago | Handshake completed | 351 ms |
| 26 days ago | Handshake completed | 400 ms |
| 27 days ago | Handshake completed | 443 ms |
| 28 days ago | Handshake completed | 346 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.
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.