Fever Event Discovery
Search Fever's live entertainment catalog across 500+ cities from an AI agent. Two tools, both reads — nothing here books, reserves or pays. OAuth 2.0 with dynamic client registration; the only scope is openid.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Fever Event Discovery via MCP
https://data-search.apigw.feverup.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Fever Event Discovery Tools & Capabilities (2)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Nothing here books, reserves or pays. The connector finds events and hands you a link. Fever's booking capability is a separate B2B product, its Transactional API, reached through an application form rather than through this endpoint.
- The single OAuth scope is an identity claim, not a permission. Both Fever's authorization server metadata and its RFC 9728 resource descriptor name
openidand nothing else. There is no grant-time distinction to make, which is unremarkable on a two-tool read surface but would offer no boundary if the surface ever grew. - Fever publishes no exclusion table. Its documentation enumerates what the two tools do, and never states what the connector will not do. The absence of booking is established by reading the enumeration, not by a vendor commitment — a weaker guarantee than a written boundary, and the reason the purchase question needed three separate checks rather than one.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so parameter types on this page come from Fever's documentation rather than from the server's own
inputSchema. - Rate limits exist but carry no published figure. Fever confirms limits apply and gives an email address for raising them. Build retry handling without knowing the threshold.
- Coverage is Fever's footprint, not the world's. Fever cites 500+ cities across 30+ countries.
search_citiesreturns ahas_resultsflag distinguishing a listed city from one with live inventory; check it before trusting an empty event search. - Sorting and distance are mode-dependent.
radiusandsort_by=distancework only in coordinate mode. Passing coordinates silently overridescity_coderather than erroring. - Rating and price arrive pre-formatted. Fever returns them as display strings including currency and review counts, so an agent cannot sort or compare across currencies without parsing them back out.
- Fever's consumer privacy policy never mentions MCP. The policy Anthropic links for this connector is Fever's general one; on 2026-08-22 it contained no reference to MCP or the Model Context Protocol, so it does not describe what an MCP session sends or retains.
Frequently asked questions
No. Both listed tools are searches, and the only route onward is a link. Fever's tool documentation says search_events returns a url field that is a direct link to the event on Fever, so you leave the conversation to book. Fever does sell a separate Transactional API for booking, but it is a different product on a different host.
Two, and Fever confirms both. Anthropic's directory lists search_cities and search_events, and Fever's developer portal documents exactly those two names with full parameter tables under a heading reading Available Tools. The two lists agree in both directions, which is a stronger result than a directory count nobody else publishes.
Yes. The endpoint returned an authentication challenge to our anonymous request on 2026-08-22, and Fever's setup instructions tell you to authenticate via OAuth 2.0 on first use, with your client opening a browser window to log in. Fever states the connector is currently available at no cost once you have signed in.
One, and it grants nothing. Fever's authorization server metadata advertised a single scope on 2026-08-22, openid, which is an OpenID identity claim rather than an application permission. The server's own RFC 9728 descriptor names the same lone scope, so consent carries no choice about what the two tools may reach.
Public catalog fields about events, not account data. Fever documents the response as carrying an event id and name, a formatted rating such as 4.8/5 with a review count, a formatted price, the venue and city, session availability, and a direct link. Keywords and a description arrive only when you pass include_description as true.
Yes, but Fever publishes no number for them. Its FAQ states that rate limits apply to ensure fair usage across all users and invites anyone needing higher limits to email data-ai@feverup.com. Fever does publish figures for its separate Reporting API, 200 requests per minute, but nothing establishes that the MCP endpoint inherits them.
Live. Fever states the data served through the MCP Server is real-time and updated at the same rate as the Fever platform itself, so events, sessions and availability match what the app shows. Prices and availability for live entertainment move quickly, so treat any figure quoted in a conversation as a snapshot to confirm on Fever.
Yes, and the OAuth flow supports it. Fever's authorization server advertises a registration endpoint, and an unregistered client id on 2026-08-22 was answered with an instruction to register at it. That is dynamic client registration, the protocol Claude Code needs, so no personal access token workaround is required here.
Sources
- Fever Developer Portal, the connector's nominated documentation, carrying setup steps, the two-tool table with full parameters, and the FAQ (retrieved 2026-08-22).
developer.feverup.com/en/serves the identical page. · retrieved 2026-08-22 - Fever experience distribution platform, the "Transactional API" destination (retrieved 2026-08-22) · retrieved 2026-08-22
- Fever business site navigation listing Reporting API, Transactional API and MCP integration as three developer products (retrieved 2026-08-22) · retrieved 2026-08-22
- Fever Reporting API, public OpenAPI document and ReDoc reference (a separate product, cited for contrast) — · (retrieved 2026-08-22) · retrieved 2026-08-22
- Live OAuth posture check: anonymous
initializereturned HTTP 401 with awww-authenticateBearer challenge namingresource_metadata; RFC 9728 descriptor athttps://data-search.apigw.feverup.com/.well-known/oauth-protected-resource/mcp; authorization server metadata athttps://data-search.apigw.feverup.com/.well-known/oauth-authorization-server; a nonsense control path under the same prefix returned a distinct 404 (2026-08-22) · retrieved 2026-08-22 - Fever privacy policy (retrieved 2026-08-22) · retrieved 2026-08-22
developer.feverup.com/robots.txt, which allows all user agents on/and carries noContent-Signalline (retrieved 2026-08-22) · retrieved 2026-08-22- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Fever MCP support — <mailto:data-ai@feverup.com>
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Fever Event Discovery
- Tools
- 2
- Domain
- data-search.apigw.feverup.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.