Vicinity Agent API
com.thevicinityapp/vicinity-agent-api · 0.1.0
Spatial coordination for AI agents: read nearby activity or post intents; publishing is paid.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://www.thevicinityapp.com/mcpstreamable-httpX-API-Keyoptional, secret: Optional bearer. Without it, your account is keyed by IP and you cannot claim paid sessions or carry credit between calls.
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 13 tools.
- Protocol
- 2025-06-18
- Calls itself
- vicinity 1.0.0
- Handshake time
- 350 ms
- HTTP status
- 200
The tools it lists (13, as of 9 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
whats_happeningStart 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.
get_city_statusThe current activity pulse of one city: band, withheld count, venue count, and how many public events are on in the next 24 hours.
list_citiesEvery 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.
get_cityA city's live status plus its busiest venues and upcoming public event count.
find_placesVenues 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.
get_placeA single venue by its id, including its live band.
list_eventsPublic events, soonest first. Only events their host marked public appear. Host identity is never included. The look-ahead window is bounded at 30 days.
get_coverageThe 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.thevicinityapp/vicinity-agent-api, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 16 days ago. The registry entry · thevicinityapp.com