io.github.Teamdayplay/dayplay-mcp
REMOTE · API.DAYPLAY.IO
Verified real-time places and events for AI agents. SF Bay Area live; more metros rolling out.
Available components
Last scanned (19 hours ago)
Scores higher than 28% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Oct 26 +13
- Endpoint reachability: not serving MCP → behind authorisation ▼ security
- Authorization: unverified → pass ▲ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- 30 Oct 26 −13
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 29 Oct 26 −33
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 28 Oct 26 +1
- Tool “plan_outing” rewrote its description, which is the text the model reads security
- Tool “browse_places” now declares an output schema ▲ functional
- Tool “get_decision_feed” now declares an output schema ▲ functional
- Tool “get_event_bridge” now declares an output schema ▲ functional
- Tool “get_events” now declares an output schema ▲ functional
- Tool “get_genres” now declares an output schema ▲ functional
- Tool “get_happening_today” now declares an output schema ▲ functional
- Tool “get_listing” now declares an output schema ▲ functional
- Tool “get_live_now” now declares an output schema ▲ functional
- Tool “get_local_gems” now declares an output schema ▲ functional
- Tool “get_locals_favorites” now declares an output schema ▲ functional
- Tool “get_marketing_events” now declares an output schema ▲ functional
- Tool “get_marketing_neighborhoods” now declares an output schema ▲ functional
- Tool “get_marketing_places” now declares an output schema ▲ functional
- Tool “get_my_itinerary” now declares an output schema ▲ functional
- Tool “get_neighborhoods” now declares an output schema ▲ functional
- Tool “get_places” now declares an output schema ▲ functional
- Tool “get_profile” now declares an output schema ▲ functional
- Tool “get_subcategories” now declares an output schema ▲ functional
- Tool “get_top_restaurants” now declares an output schema ▲ functional
- Tool “get_top_venues” now declares an output schema ▲ functional
- Tool “get_venue_events” now declares an output schema ▲ functional
- Tool “get_weekend” now declares an output schema ▲ functional
- Tool “list_going” now declares an output schema ▲ functional
- Tool “list_saves” now declares an output schema ▲ functional
- Tool “manage_saved_plans” now declares an output schema ▲ functional
- Tool “mark_going” now declares an output schema ▲ functional
- Tool “plan_outing” now declares an output schema ▲ functional
- Tool “save_listing” now declares an output schema ▲ functional
- Tool “save_outing” now declares an output schema ▲ functional
- Tool “search_embed” now declares an output schema ▲ functional
- Tool “search_parse_intent” now declares an output schema ▲ functional
- Tool “search_query_router” now declares an output schema ▲ functional
- Tool “search_rerank” now declares an output schema ▲ functional
- Tool “search_smart” now declares an output schema ▲ functional
- Tool “search_web” now declares an output schema ▲ functional
- Tool “share_gem” now declares an output schema ▲ functional
- Tool “share_local_favorite” now declares an output schema ▲ functional
- Tool “unmark_going” now declares an output schema ▲ functional
- Tool “unsave_listing” now declares an output schema ▲ functional
- Tool “upvote_listing” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_event_bridge” rewrote its description, which is the text the model reads security
- Tool “get_events” rewrote its description, which is the text the model reads security
- Tool “get_genres” rewrote its description, which is the text the model reads security
- Tool “get_marketing_events” rewrote its description, which is the text the model reads security
- Tool “get_marketing_neighborhoods” rewrote its description, which is the text the model reads security
- Tool “get_marketing_places” rewrote its description, which is the text the model reads security
- Tool “get_neighborhoods” rewrote its description, which is the text the model reads security
- Tool “get_places” rewrote its description, which is the text the model reads security
- Tool “get_subcategories” rewrote its description, which is the text the model reads security
- Schema quality: 71 → 80 ▼ functional
- “get_events” added a required parameter “lat”, so existing callers break ▼ functional
- “get_events” added a required parameter “lng”, so existing callers break ▼ functional
- “get_marketing_events” added a required parameter “lat”, so existing callers break ▼ functional
- “get_marketing_events” added a required parameter “lng”, so existing callers break ▼ functional
- “get_marketing_places” added a required parameter “lat”, so existing callers break ▼ functional
- “get_marketing_places” added a required parameter “lng”, so existing callers break ▼ functional
- “get_places” added a required parameter “lat”, so existing callers break ▼ functional
- “get_places” added a required parameter “lng”, so existing callers break ▼ functional
- “search_web” made “user_lat” required, so existing callers break ▼ functional
- “search_web” made “user_lng” required, so existing callers break ▼ functional
- Server version: 2.1.0 → 2.2.0 functional
- “get_event_bridge” added an optional parameter “tz” cosmetic
- “get_events” added an optional parameter “city” cosmetic
- “get_events” added an optional parameter “radius_km” cosmetic
- “get_events” added an optional parameter “tz” cosmetic
- “get_genres” added an optional parameter “tz” cosmetic
- “get_marketing_events” added an optional parameter “city” cosmetic
- “get_marketing_events” added an optional parameter “radius_km” cosmetic
- “get_marketing_events” added an optional parameter “tz” cosmetic
- “get_marketing_places” added an optional parameter “category” cosmetic
- “get_marketing_places” added an optional parameter “city” cosmetic
- “get_marketing_places” added an optional parameter “radius_km” cosmetic
- “get_marketing_places” added an optional parameter “tz” cosmetic
- “get_places” added an optional parameter “city” cosmetic
- “get_places” added an optional parameter “radius_km” cosmetic
- “get_places” added an optional parameter “tz” cosmetic
- “get_subcategories” added an optional parameter “tz” cosmetic
- “get_events” reworded the description of “neighborhood” cosmetic
- “get_marketing_events” reworded the description of “neighborhood” cosmetic
- “get_marketing_places” reworded the description of “neighborhood” cosmetic
- “get_places” reworded the description of “neighborhood” cosmetic
- 26 Oct 26 +1
- A breaking change shipped without a version bump: still 2.1.0 ▼ security
- Tool “get_event_bridge” rewrote its description, which is the text the model reads security
- Tool “get_genres” rewrote its description, which is the text the model reads security
- Tool “get_happening_today” rewrote its description, which is the text the model reads security
- Tool “get_live_now” rewrote its description, which is the text the model reads security
- Tool “get_local_gems” rewrote its description, which is the text the model reads security
- Tool “get_locals_favorites” rewrote its description, which is the text the model reads security
- Tool “get_subcategories” rewrote its description, which is the text the model reads security
- Tool “get_top_restaurants” rewrote its description, which is the text the model reads security
- Tool “get_top_venues” rewrote its description, which is the text the model reads security
- Tool “get_weekend” rewrote its description, which is the text the model reads security
- Tool “search_query_router” rewrote its description, which is the text the model reads security
- Tool “search_smart” rewrote its description, which is the text the model reads security
- Tool “search_web” rewrote its description, which is the text the model reads security
- Schema quality: 64 → 71 ▼ functional
- “get_local_gems” added a required parameter “lat”, so existing callers break ▼ functional
- “get_local_gems” added a required parameter “lng”, so existing callers break ▼ functional
- “get_top_restaurants” added a required parameter “lat”, so existing callers break ▼ functional
- “get_top_restaurants” added a required parameter “lng”, so existing callers break ▼ functional
- “get_top_venues” added a required parameter “lat”, so existing callers break ▼ functional
- “get_top_venues” added a required parameter “lng”, so existing callers break ▼ functional
- “get_event_bridge” made “lat” required, so existing callers break ▼ functional
- “get_event_bridge” made “lng” required, so existing callers break ▼ functional
- “get_genres” made “lat” required, so existing callers break ▼ functional
- “get_genres” made “lng” required, so existing callers break ▼ functional
- “get_happening_today” made “lat” required, so existing callers break ▼ functional
- “get_happening_today” made “lng” required, so existing callers break ▼ functional
- “get_live_now” made “lat” required, so existing callers break ▼ functional
- “get_live_now” made “lng” required, so existing callers break ▼ functional
- “get_locals_favorites” made “city” required, so existing callers break ▼ functional
- “get_subcategories” made “lat” required, so existing callers break ▼ functional
- “get_subcategories” made “lng” required, so existing callers break ▼ functional
- “get_weekend” made “lat” required, so existing callers break ▼ functional
- “get_weekend” made “lng” required, so existing callers break ▼ functional
- “search_query_router” made “user_lat” required, so existing callers break ▼ functional
- “search_query_router” made “user_lng” required, so existing callers break ▼ functional
- “search_smart” made “user_lat” required, so existing callers break ▼ functional
- “search_smart” made “user_lng” required, so existing callers break ▼ functional
- Schema quality: fair → good functional
- “get_local_gems” added an optional parameter “radius_km” cosmetic
- “get_top_restaurants” added an optional parameter “radius_km” cosmetic
- “get_top_venues” added an optional parameter “radius_km” cosmetic
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 56.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.dayplay.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.dayplay.io | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 5 Sept 2026 | 21 Mar 2027 | RSA 2048 | SHA256-RSA | b54fb6fa6ece3cea21f5a67f4cc450a |
| SANs: api.dayplay.io | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.dayplay.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| dayplay.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="dayplay", resource_metadata="https://api.dayplay.io/.well-known/oauth-protected-resource"
Bearer realm="dayplay", resource_metadata="https://api.dayplay.io/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| www-authenticate | Bearer realm="dayplay", resource_metadata="https://api.dayplay.io/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.dayplay.io/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.dayplay.io/mcp |
| Authorisation server | https://api.dayplay.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.dayplay.io/mcp | Auth required | 401 | |
| http (plaintext) | http://api.dayplay.io/mcp | HTTPS enforced | 301 | https://api.dayplay.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
browse_places ~147
Places inside a radius, sorted by distance. user_lat, user_lng, and radius_km are numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | max_results |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| search_query | string | – | Natural-language query. |
| selected_genres | array | – | selected_genres |
| selected_price_tiers | array | – | selected_price_tiers |
| selected_subcategories | array | – | selected_subcategories |
| user_lat | number | yes | Decimal degrees. Send a number, not a string. |
| user_lng | number | yes | Decimal degrees. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
get_decision_feed ~234
Ranked decision feed. Send user_lat and user_lng as numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_city | string | – | anchor_city |
| event_week_offset | integer | – | event_week_offset |
| max_results | integer | – | max_results |
| offset | integer | – | offset |
| preferred_radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| search_query | string | – | Natural-language query. |
| selected_genres | array | – | selected_genres |
| selected_price_tiers | array | – | selected_price_tiers |
| selected_subcategories | array | – | selected_subcategories |
| selected_time_bands | array | – | selected_time_bands |
| selected_type | string | – | selected_type |
| tz | string | – | tz |
| user_lat | number | yes | Decimal degrees. Send a number, not a string. |
| user_lng | number | yes | Decimal degrees. Send a number, not a string. |
| weekend_day | string | – | sat or sun. |
Structured output declared, but exposes no named fields.
No examples provided.
get_event_bridge ~118
Event-bridge taxonomy near a point. lat and lng are required. tz is an IANA timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| lookahead_weeks | integer | – | lookahead_weeks |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| selected_moods | string | – | selected_moods |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_events ~149
Events near a point. lat and lng are required. date is YYYY-MM-DD. neighborhood is optional.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | category |
| city | string | – | city |
| date | string | – | Calendar date, YYYY-MM-DD. |
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| neighborhood | string | – | Optional neighborhood name, such as Mission. lat and lng select the area. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_genres ~112
Catalog genres near a point. lat and lng are required. tz is an IANA timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| selected_subcategories | string | – | selected_subcategories |
| selected_type | string | – | selected_type |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_happening_today ~101
Events and places happening today. lat and lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| offset | integer | – | offset |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_listing ~24
One event or place.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Dayplay listing id. |
Structured output declared, but exposes no named fields.
No examples provided.
get_live_now ~99
What is happening right now. lat and lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| offset | integer | – | offset |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_local_gems ~86
Curated local gems near a point. lat and lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
get_locals_favorites ~39
Published locals' favorites in one city. city is required.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | city |
| limit | integer | – | limit |
Structured output declared, but exposes no named fields.
No examples provided.
get_marketing_events ~159
Events near a point. lat and lng are required. date is YYYY-MM-DD. neighborhood is optional.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | category |
| city | string | – | city |
| date | string | – | Calendar date, YYYY-MM-DD. |
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| neighborhood | string | – | Optional neighborhood name, such as Mission. lat and lng select the area. |
| offset | integer | – | offset |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_marketing_neighborhoods ~30
Named neighborhoods that resolve without coordinates. The list is San Francisco, Oakland, and Berkeley.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_marketing_places ~163
Places near a point. lat and lng are required. neighborhood is optional.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | category |
| city | string | – | city |
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| neighborhood | string | – | Optional neighborhood name, such as Mission. lat and lng select the area. |
| offset | integer | – | offset |
| open_now | boolean | – | When true, only places open now. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| sort | string | – | sort |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_my_itinerary ~18
The signed-in user's Saved-tab days.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_neighborhoods ~28
Named neighborhoods that resolve without coordinates. The list is San Francisco, Oakland, and Berkeley.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_places ~169
Places near a point. lat and lng are required. neighborhood and category are optional.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | category |
| city | string | – | city |
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| neighborhood | string | – | Optional neighborhood name, such as Mission. lat and lng select the area. |
| newly_opened_days | integer | – | newly_opened_days |
| open_now | boolean | – | When true, only places open now. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| sort | string | – | sort |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_profile ~14
The signed-in user's profile.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_subcategories ~113
Catalog subcategories near a point. lat and lng are required. tz is an IANA timezone.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| selected_moods | string | – | selected_moods |
| selected_type | string | – | selected_type |
| tz | string | – | tz |
Structured output declared, but exposes no named fields.
No examples provided.
get_top_restaurants ~96
Top restaurants near a point. lat and lng are required. city is optional.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | city |
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
get_top_venues ~85
Top-rated places near a point. lat and lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
get_venue_events ~35
Upcoming events at one venue.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Dayplay listing id. |
| limit | integer | – | limit |
Structured output declared, but exposes no named fields.
No examples provided.
get_weekend ~116
Saturday or Sunday feed. weekend_day is sat or sun. lat and lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Decimal degrees. Send a number, not a string. |
| limit | integer | – | limit |
| lng | number | yes | Decimal degrees. Send a number, not a string. |
| offset | integer | – | offset |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| tz | string | – | tz |
| weekend_day | string | – | sat or sun. |
Structured output declared, but exposes no named fields.
No examples provided.
list_going ~17
Events the signed-in user is attending.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_saves ~15
The signed-in user's saves.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
manage_saved_plans ~68
List or save the signed-in user's Dayplay itinerary. Requires Google connect. Sellout, closure, and weather alerts are not available yet.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| alert_type | string | – | – |
| plan | object | – | – |
| plan_id | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
mark_going ~31
Mark a listing as going. Requires listing_id.
| Name | Type | Req | Description |
|---|---|---|---|
| listing_id | string | yes | Dayplay listing id. |
Structured output declared, but exposes no named fields.
No examples provided.
plan_outing ~82
Save an outing for a date and neighborhood onto the signed-in user's Saved tab. Requires Google connect. neighborhood is a Bay Area name such as Mission, Oakland, or Berkeley.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | – |
| date | string | yes | YYYY-MM-DD |
| interests | string | – | – |
| neighborhood | string | yes | – |
| vibe | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
save_listing ~39
Bookmark a listing for the signed-in user.
| Name | Type | Req | Description |
|---|---|---|---|
| list_name | string | – | list_name |
| listing_id | string | – | Dayplay listing id. |
Structured output declared, but exposes no named fields.
No examples provided.
save_outing ~61
Write plan stops onto a calendar day. date is YYYY-MM-DD. stops are listing_id objects.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Calendar date, YYYY-MM-DD. |
| stops | array | yes | Stops to save, in order. Each object needs listing_id. |
Structured output declared, but exposes no named fields.
No examples provided.
search_embed ~39
Embed text for the signed-in user.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | Natural-language query. |
| texts | array | – | Alternate list of strings to embed. |
Structured output declared, but exposes no named fields.
No examples provided.
search_parse_intent ~40
Parse a search query into filters for the signed-in user.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | action |
| query | string | yes | Natural-language query. |
Structured output declared, but exposes no named fields.
No examples provided.
search_query_router ~98
Turn a search phrase into filters for the signed-in user. user_lat and user_lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| search_query | string | yes | Natural-language query. |
| user_lat | number | yes | Decimal degrees. Send a number, not a string. |
| user_lng | number | yes | Decimal degrees. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
search_rerank ~49
Rerank listings for the signed-in user.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Listings to rerank. Each item needs an id and title. |
| query | string | yes | Natural-language query. |
Structured output declared, but exposes no named fields.
No examples provided.
search_smart ~139
Search events and places for the signed-in user. user_lat and user_lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | max_results |
| query | string | yes | Natural-language query. |
| radius_km | number | – | Radius in kilometers. Send a number, not a string. |
| selected_genres | array | – | selected_genres |
| selected_subcategories | array | – | selected_subcategories |
| selected_type | string | – | selected_type |
| user_lat | number | yes | Decimal degrees. Send a number, not a string. |
| user_lng | number | yes | Decimal degrees. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
search_web ~97
Add web results to a search for the signed-in user. user_lat and user_lng are required.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | max_results |
| query | string | – | Natural-language query. |
| search_query | string | yes | Natural-language query. |
| user_lat | number | yes | Decimal degrees. Send a number, not a string. |
| user_lng | number | yes | Decimal degrees. Send a number, not a string. |
Structured output declared, but exposes no named fields.
No examples provided.
share_gem ~77
Submit a gem.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | category |
| description | string | – | description |
| location_text | string | – | location_text |
| photo_url | string | – | photo_url |
| submission_type | string | – | submission_type |
| title | string | yes | title |
| website_url | string | – | website_url |
Structured output declared, but exposes no named fields.
No examples provided.
share_local_favorite ~90
Submit a locals' favorite.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | address |
| category | string | yes | category |
| city | string | – | city |
| description | string | – | description |
| latitude | number | yes | Decimal degrees. Send a number, not a string. |
| longitude | number | yes | Decimal degrees. Send a number, not a string. |
| name | string | yes | name |
Structured output declared, but exposes no named fields.
No examples provided.
unmark_going ~26
Remove a going RSVP.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Dayplay listing id. |
Structured output declared, but exposes no named fields.
No examples provided.
unsave_listing ~24
Remove one save.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Dayplay listing id. |
Structured output declared, but exposes no named fields.
No examples provided.
upvote_listing ~25
Upvote a listing.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Dayplay listing id. |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.Teamdayplay/dayplay-mcp server?
io.github.Teamdayplay/dayplay-mcp is a hosted endpoint at https://api.dayplay.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.dayplay.io
claude mcp add --transport http teamdayplay-dayplay-mcp 'https://api.dayplay.io/mcp'
What is the io.github.Teamdayplay/dayplay-mcp server?
io.github.Teamdayplay/dayplay-mcp is listed in the public MCP registry as io.github.Teamdayplay/dayplay-mcp. Verified real-time places and events for AI agents. SF Bay Area live; more metros rolling out. This page covers its hosted endpoint (https://api.dayplay.io/mcp).
Is the io.github.Teamdayplay/dayplay-mcp server safe to use?
io.github.Teamdayplay/dayplay-mcp scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Teamdayplay/dayplay-mcp server expose?
io.github.Teamdayplay/dayplay-mcp exposes 40 tools: get_happening_today, get_live_now, get_weekend, get_decision_feed, browse_places, and 35 more. Their descriptions and schemas cost roughly 3,152 tokens of context every time the server is loaded.
Does the io.github.Teamdayplay/dayplay-mcp server require authentication?
Yes. io.github.Teamdayplay/dayplay-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.Teamdayplay/dayplay-mcp server still maintained?
io.github.Teamdayplay/dayplay-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.Teamdayplay/dayplay-mcp server?
VerifyMCP ran 5 checks on io.github.Teamdayplay/dayplay-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about io.github.Teamdayplay/dayplay-mcp: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.