Google Search Console integration for Model Context Protocol (MCP)
Community Days is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Community-run Microsoft ecosystem events, calls for speakers and speakers, from CommunityDays.org.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http community-days-mcp https://mcp.communitydays.org/runtime/webhooks/mcp
# 2 — ask your agent for something these tools do
# get_event, get_event_sessions, get_speaker and 4 more
Community Days costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http community-days-mcp https://mcp.communitydays.org/runtime/webhooks/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get a single published Community Days event by its URL slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event URL slug (the slug returned by search_events), or a link to the event's page |
Get all indexed sessions for an event by its URL slug, each with its speaker's name and speakerId (for get_speaker).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Event URL slug (the slug returned by search_events), or a link to the event's page |
Get a speaker's full profile: bio, links, counts, the events, cities and countries they have spoken in, and every session they have given, newest first. One answer per person, across Sessionize and run.events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Speaker identifier: the speakerId returned by search_speakers, or a speaker id from an event's sessions (get_event_sessions) |
Get every session a speaker has given, newest first, across Sessionize and run.events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Speaker identifier: the speakerId returned by search_speakers, or a speaker id from an event's sessions (get_event_sessions) |
List published Community Days events with the events page's filters, no keyword needed: e.g. upcoming events with an open call for speakers, open registration or sponsorship, by cost, type or country. Upcoming soonest first; past most recent first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| when | string | no | upcoming (default: not ended yet, so events under way today are included), past (already ended) or range (from, to or both) |
| from | string | no | With when=range: first start date, yyyy-MM-dd (leave out for no earliest date) |
| to | string | no | With when=range: last start date, yyyy-MM-dd (leave out for no latest date) |
| call_for_speakers | string | no | true: only events whose call for speakers is open now |
| call_for_sponsors | string | no | true: only events whose call for sponsors is open now |
| registration_open | string | no | true: only events whose registration is open now |
| cost | string | no | Comma-separated: free, low_cost ($30 or less), paid (more than $30) |
| event_type | string | no | Comma-separated: in_person, online, hybrid |
| country | string | no | Comma-separated two-letter country codes, e.g. us,ca,gb |
| source | string | no | all (default), community_days (listed on Community Days) or external (copied from Microsoft's event listings; upcoming only, as past and range lists leave copied events out) |
| q | string | no | Optional keyword in the title, city or region (diacritic-insensitive) |
| limit | string | no | How many events, 1 to 50 (default 20) |
Search published Community Days events by keyword. Returns up to 20 matching events: upcoming events first (soonest first), then past events (most recent first).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Search keyword (case-insensitive, diacritic-insensitive — 'sao' matches 'São') |
Search Community Days speakers by name. Returns up to 20 people, one entry each (Sessionize and run.events identities the speaker board has merged appear once), most sessions first, with their session, hour, event and country counts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Speaker name to search (case-insensitive, diacritic-insensitive — 'michal' matches 'Michał') |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Community Days or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_event | no tags | |
| get_event_sessions | no tags | |
| get_speaker | no tags | |
| get_speaker_sessions | no tags | |
| list_events | no tags | |
| search_events | no tags | |
| search_speakers | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Community Days can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.