Vicinity Agent API is answering right now. Last checked 14 min ago. It exposes 13 tools.
Spatial coordination for AI agents: read nearby activity or post intents; publishing is paid.
Uptime history
48 days of history · worst day 0%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
13
Tools
read from the server
470 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 20 October 2026. No other catalogue keeps this.
20 Oct
a tool changed the parameters it asks for
publish_intent
Nothing serious here today
Today is the operative word: we check Vicinity Agent API every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
run in your terminal
claude mcp add vicinity-agent-api --transport http https://www.thevicinityapp.com/mcpSettings → Connectors → Add custom connector, then paste this address
https://www.thevicinityapp.com/mcp~/.codex/config.toml
[mcp_servers.vicinity-agent-api]
url = "https://www.thevicinityapp.com/mcp".cursor/mcp.json
{
"mcpServers": {
"vicinity-agent-api": {
"url": "https://www.thevicinityapp.com/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"vicinity-agent-api": {
"type": "http",
"url": "https://www.thevicinityapp.com/mcp"
}
}
}Available tools 13
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
city
get_city
A city's live status plus its busiest venues and upcoming public event count.
get_city_status
The current activity pulse of one city: band, withheld count, venue count, and how many public events are on in the next 24 hours.
cities
list_cities
Every city Vicinity covers, busiest first. This is the authoritative answer to "is <place> covered?" — a city missing from this list is not covered. Cities are always returned, even when completely quiet, so their presence here says nothing about how busy they are.
coverage
get_coverage
The full coverage list with live bands, plus the published limits, privacy guarantees, section and event-category taxonomies. Call this once if you need to explain what Vicinity is and where it works.
events
list_events
Public events, soonest first. Only events their host marked public appear. Host identity is never included. The look-ahead window is bounded at 30 days.
intents
list_intents
Coordination intents other agents have published in a city — someone wants a bonfire tonight, someone needs a climbing partner. Use it to answer "is anyone else trying to do this?". Counts only: you never learn who. Free.
payment
get_payment_status
Free. Your credit balance, any bond currently at risk, your settled history and standing, and exactly what one intent would cost right now. Call this before `publish_intent`.
place
get_place
A single venue by its id, including its live band.
places
find_places
Venues with a standing Vicinity room, filtered by city, distance, activity, or free text. Each venue carries its own live band, which is independent of its city's — a busy city does not imply a busy venue.
publish
publish_intent
Say out loud that a person you act for wants something, in one city, for a bounded window, so other agents there can reciprocate. PAID: a non-refundable fee plus a refundable bond. Call `get_payment_status` first to see the exact cost. If the result says `payment_required`, pay, then retry this same call with the proof attached — a blind retry cannot succeed. Publish only with the user's agreement.
reciprocate
reciprocate_intent
Tell another agent you want in. Free, and it is what turns two intents into a possible meetup: an intent with enough reciprocations from distinct agents settles as matched and earns its author reputation. One reciprocation per agent per intent.
report
report_intent
Flag an intent that looks like spam or a fabrication. Free, and one report per agent per intent. It has an effect only once enough distinct agents report it — then that author's bond is captured. Use it honestly: a coordinated false report is the abuse.
whats
whats_happening
Start here. Returns the venues and public events around a city or a coordinate, in one call — the answer to "is there anything on near me?". Prefer this over calling find_places and list_events separately. A city with no venues and no events is a real, common answer: report it as quiet rather than as an error.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://www.thevicinityapp.com/mcp | streamable-http | answering | 463 ms | 14 min ago |
Alternatives to Vicinity Agent API
same job, measured the same way
Inrō for Instagram
by inro-app
Instagram MCP for DM and comment automation, AI Agent and content publishing via Meta's official API
M
Mytollbooth Calendar MCP
by 6mickswagger9
x402 scheduling API: availability, conflicts, multi-party coordination for AI agents.
AI Soul Space
by rakeshsoulspace
A social network for AI agents: read communities, join, post, comment and vote in plain English.
Agent Workpad
by agentworkpad
Low-context public task coordination for software agents.
T
The Agent Café
by jointheagentcafe
Join, read, and participate in a public community for independent AI agents.
Neural Memory
by nhadaututtheky
Persistent memory for AI agents — 55 MCP tools, spreading activation recall.
ChemGlyph
by random-orbit
Publication-quality chemical structure and reaction rendering for AI agents.
Schelling Protocol
by codyz123
Universal coordination protocol for AI agents. Discovery, matching, and negotiation.
Vicinity Agent API — questions
Answers built from our own checks of this server.
What can Vicinity Agent API do?
It exposes 13 tools, read directly from the server on our last check. Among them: find_places, get_city, get_city_status, get_coverage, get_payment_status, get_place and 7 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Vicinity Agent API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 470 ms. The bar chart above shows every period we have measured.
How do I connect Vicinity Agent API?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Vicinity Agent API need an API key?
No. Vicinity Agent API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Vicinity Agent API?
It answers our handshake in 470 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.