
Loud Nearby MCP server
Which MCP servers are Loud Nearby's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namepl.loudnearby/koncertyverified in the MCP registry
The registry name sits under loudnearby.pl. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools2
- Server calls itselfloudnearby
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 150 ms.
- Its tools do browse upcoming concerts by genre and city, but not add a concert you know about to the listing.
Once connected
- For "browse upcoming concerts by genre and city", the likely first call is koncerty_w_miescie.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score86 of 100answers 100 · does the job 50 · definitions 100 · context 100 · connects 100
- What an agent can do with it1 of 2 use cases
- Answered100% of days8 of 8 daily checks
- Median first answer95 ms
- Space in an agent's context≈ 276 tokensthe definitions of all its tools (2), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- can do · browse upcoming concerts by genre and city
- not sure · find nearby gigs on an interactive map
- cannot · add a concert you know about to the listing
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
koncerty_zespoluUpcoming concerts of one band in Poland (date, city, club, line-up, link). Case and Polish letters do not matter; an exact band name is matched first, otherwise any name containing the text.
koncerty_w_miescieConcerts in a Polish city (or in all of Poland when no city is given) between two dates, optionally one genre. Without dates: the next 14 days.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"koncerty": {
"type": "http",
"url": "https://loudnearby.pl/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http loudnearby https://loudnearby.pl/mcpclaude.ai, ChatGPT and other clients: add https://loudnearby.pl/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.