6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Search Fever's live entertainment catalog across 500+ cities.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Fever Event Discovery MCP server connects Fever — a live entertainment marketplace selling concerts, immersive exhibitions, shows and experiences across 500+ cities — to Claude, ChatGPT and any MCP-compatible agent. It provides two read tools: one finds cities where Fever operates, the other searches events in them. Sign-in is OAuth 2.0.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
openid and 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.inputSchema.search_cities returns a has_results flag distinguishing a listed city from one with live inventory; check it before trusting an empty event search.radius and sort_by=distance work only in coordinate mode. Passing coordinates silently overrides city_code rather than erroring.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.
developer.feverup.com/en/ serves the identical page. · retrieved 2026-08-22initialize returned HTTP 401 with a www-authenticate Bearer challenge naming resource_metadata; RFC 9728 descriptor at https://data-search.apigw.feverup.com/.well-known/oauth-protected-resource/mcp; authorization server metadata at https://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-22developer.feverup.com/robots.txt, which allows all user agents on / and carries no Content-Signal line (retrieved 2026-08-22) · retrieved 2026-08-22Connect Fever Event Discovery once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.