Skip to content

Sonar Connections MCP server

com.sonarconnections/sonar-connectionssonarconnections.comstreamable-httpv0.1.0Scanned

Source-attributed events, open data and availability

70 tools: 14 can delete or cancel things, 6 do something that can't be undone, 38 change things and 12 only read.

Tools: 14 delete, 6 irreversible, 38 write, 12 read.
  • Reads private data · 1
  • Reads text others write · 13
  • Can send data out · 9
  • 9 findings

Tools listed without sign-in. Remote posture

With Anlyon

14 tools here can delete or cancel things and 6 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Sonar Connections MCP server can do

The Sonar Connections MCP server is published by sonarconnections.com, a domain the MCP Registry verified. It has 70 tools. It can delete or cancel things (14 tools: event_set_intent, event_pass_reissue, event_pass_revoke, event_pass_notice_cancel and 10 more), do things that cannot be undone, such as sending, paying or publishing (booth_take_invite, event_reply, event_say_hello, event_pass_notice and 2 more) and create or change data (38 tools: booth_set_away, biz_set_item_availability, event_redeem_code, event_card_links and 34 more). 12 tools only read.

1 tool reads private data (event_inbox); 13 tools bring in text other people can write (biz_set_item_availability, event_inbox, event_my_card and 10 more); 9 tools can send data out of your system (booth_take_invite, event_reply, event_say_hello and 6 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 9 findings (annotation-conflict and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

70 tools

Deletes or cancels 14Claude Code: deny
  • event_change_detailTo change an existing event's pass palette or color ("change the color to sage"): call this tool with `field` "color" or "palette".1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description is 5,475 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...th confirm true. Passes update quietly. event_change_undo puts the last one back."

      What this check looks for
    Description, as the server wrote it
    To change an existing event's pass palette or color ("change the color to sage"): call this tool with `field` "color" or "palette". THE HOSTS' OWN EDIT of a wedding or other personal event. IT APPLIES THE CHANGE ON THIS CALL, one `field` per call, and the reply says the detail now and before: read both out. A time needs am or pm, or a 24 hour time that reads one way; a bare "4:30" is refused. For faq_answer, `question` adds the entry or replaces its answer. Every change is logged and can be read back; event_change_undo reverses the caller's own latest one. Only the hosts can change it; read refusals (NOT_A_HOST, BAD_TIME, NO_SUCH_PLACE, NO_SUCH_ENTRY, NO_CHANGE) out as given; it sends no message and it changes nothing else on the event; the event's Wallet passes are updated with the new detail as a lock-screen notice and the reply's `passNotice` says how many passes were reached. Needs a personal connector token. ANY PART OF AN EVENT: with `section` and `op` (add, edit, remove, reorder) this changes the name, dates, venue, address, cover, FAQ, about text, speakers, booths and session details of a conference as well as a wedding. It applies on this call; a name, dates or time change previews first (confirm with the changeId). Read the reply out: it says what followed on the pass, the page and here, and what did not. Guests are never told unless the reply offers it and they say yes. A session's time, room and title, adding and cancelling one, keep the session tools. event_change_undo reverses their own latest. START TIME: `field` "start_time" sets the time a one day personal event starts, with no schedule needed. `value`: "5 PM" or "5 PM to 9 PM" (am or pm required), or "clear" to remove it. It can also change the event's dates: give the new first and last day, and any agenda items outside the new dates are listed back to you before anything is removed. A time may run past midnight ("10 PM to 2 AM" ends the next morning), and one item can be added on several days at once or span days. LANGUAGE: `field` "language" with `value` a language code (en, es) sets the language guests see on the passes, the add page and notices; issued passes relabel quietly, with no alert, and the hosts' own text is untouched. COVER PHOTO: `field` "cover_photo" (any `value`, e.g. "add") answers with a one-time link to our upload page; give the host the link and its sentence. The photo goes from their phone to us, never through this chat. Call it again after they say done: the reply carries the pass preview with the photo. PALETTE: `field` "palette" with a palette name, or "color" with a color name or #rrggbb, changes the pass colors; the text color is chosen so it stays readable. Without `confirm` the reply is a preview: show it, and only on a yes call again with confirm true. Issued passes update quietly, with no alert. PARTY LINK: `field` "party_link" runs one shareable link for a personal event; anyone who taps it adds their own pass. `value`: on, pause, resume, status (the count and the latest adds), regenerate (the old link stops), revoke all, or settings like "cap 80, names on, one per phone off, expires 2026-11-15". "sign in none" lets anyone with the link add a pass with no phone number and no code (no text updates, the host sees a count only, the cap counts every add, and a shared link admits anyone until regenerate); "sign in phone" asks for the number again. GUEST CODE: `field` "guest_code" changes the code guests type to open a private event's page; `value` is the new code (4 to 32 letters and digits) or "new" for a fresh one. The old code stops working. Read the new code back to the host. SHARE PREVIEW: `field` "share_level" sets what a texted link to a personal event previews as. `value`: branded (cover photo, name, date), name_only (a card with the name and date), private ("A private event", nothing else), or status (what the link looks like now, with the image url). LOOK: `field` "page_template" picks the guest page template (summit, market, gala, garden), "pass_style" the Google pass style (A, C, D, E, F, G), and "title_font" the title face for the event page and the share card only (Bodoni Moda, Sofia Sans Extra Condensed, Fredoka, Jost, Caprasimo, or default for the template's own); the pass always uses the system font. `value` "status" answers the current look. EYEBROW: `field` "eyebrow" sets the short word the guest page prints over the event name instead of its kind (2 to 24 characters, for example "Live music"); `value` "none" goes back to the kind. RSVP, HOSTED BY, GUEST: `field` "rsvp" takes "on" or "off" in `value`; "hosted_by" takes the host name to show (empty clears it); "guest_add" takes the guest name in `value` and their number in `phone`, shows a preview, then call again with confirm: true and the confirmToken. Adding a guest never texts them. PASS SETTING: `field` "pass_setting" changes one setting of the Wallet pass by the name the host says ("Google hero", "logo", "background color", "pass front", "poster or classic", "QR code") or its catalog id, in `setting`, with the new value in `value` (a hex color, "cover" for a picture, or one of the words the setting names: for the pass front, poster, classic, or classic with no code). The first call previews today's pass and the changed one and saves nothing; show both, say the reply's message to the host in full, and only on yes call again with confirm true. Passes update quietly. event_change_undo puts the last one back.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Change one detail of a personal event (hosts only)
  • event_change_undoReverses the caller's own most recent change to a wedding or other personal event they host, restoring the value the detail had before it, through the same checks and into the same…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Reverses the caller's own most recent change to a wedding or other personal event they host, restoring the value the detail had before it, through the same checks and into the same change log; each further call reverses the next older change of theirs. Needs a personal connector token and `eventIdOrName`. Only the hosts can use it, and only on changes they made themselves; an undo is not itself reversed. A change that gave a detail its first value, or no change left to reverse, answers NOTHING_TO_UNDO and changes nothing. When the event's Wallet passes are switched on, restoring a detail the pass shows updates every pass of the event and pushes the restored line to each phone that registered it. Returns the detail, the value before and after, a sentence for the person and, with passes on, `passNotice`.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Undo my last change
  • event_draft_deleteDeletes one of the signed-in person's own unpublished drafts for good, with its guest details and uploads, as the organizer dashboard's Delete draft does.No findings

    Why it is in this group

    • The name "event_draft_delete" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Deletes one of the signed-in person's own unpublished drafts for good, with its guest details and uploads, as the organizer dashboard's Delete draft does. `eventIdOrName` is the draft's id or its name as the host says it. FIRST CALL WITHOUT `confirm` returns a PREVIEW naming the draft with a `requestId` and deletes nothing; read it out, and only when the host says yes, call again with `confirm: true` and that `requestId`. A published event cannot be deleted (NOT_A_DRAFT). Only the host can delete. The reply names what was deleted and the new count of open drafts. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_A_DRAFT, CONFIRM_INVALID, DELETE_FAILED) are read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Delete one of your unpublished drafts (hosts)
  • event_pass_notice_cancelRemoves the one notice a host scheduled with event_pass_notice sendAt on a personal event this connector serves; call it for "cancel the scheduled notice", "do not send that remind…1 finding

    Why it is in this group

    • The name "event_pass_notice_cancel" says "cancel": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "event_pass_notice_cancel" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_pass_notice_cancel" says "cancel": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Removes the one notice a host scheduled with event_pass_notice sendAt on a personal event this connector serves; call it for "cancel the scheduled notice", "do not send that reminder". It says what was scheduled and confirms nothing was sent. Hosts and co-hosts only; it requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Cancel the scheduled pass notice (hosts)
  • event_pass_reissueGives a Wallet pass a new QR code: a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants refreshed.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Gives a Wallet pass a new QR code: a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants refreshed. It also brings back a revoked pass. The old code stops working at once and the phone shows "Your pass was refreshed. The old code no longer works." Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs `eventIdOrName` (the event id or the event name). Without `serialNumber` it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Refresh a Wallet pass with a new code
  • event_pass_revokeVoids a Wallet pass on the phone: "This pass was revoked and no longer works." Its code stops working at once; event_pass_reissue brings it back.No findings

    Why it is in this group

    • The name "event_pass_revoke" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Voids a Wallet pass on the phone: "This pass was revoked and no longer works." Its code stops working at once; event_pass_reissue brings it back. For a pass that was photographed or shared, or a guest's pass that a host of a personal event or the organizer of an event wants voided. Nothing is re-added: the same pass updates in place on an iPhone and on Android. Needs `eventIdOrName` (the event id or the event name). Without `serialNumber` it acts on the caller's own pass at that event; with one it acts on that pass, for a caller who is a host or the organizer. Returns the outcome in one sentence.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Revoke a Wallet pass
  • event_session_cancelCancels one session on the agenda of an event the person organizes; it is marked cancelled and kept on record.No findings

    Why it is in this group

    • The name "event_session_cancel" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancels one session on the agenda of an event the person organizes; it is marked cancelled and kept on record. Quiet unless `notify` is true. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId`, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with `confirm: true` and that `changeId`. Name the session by `sessionId` or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Cancel a session (organizers only)
  • event_session_moveMoves one session on the agenda of an event the person organizes to a new start time or room ("push the keynote to 4:30 PM").No findings

    Why it is in this group

    • The name "event_session_move" says "move": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Moves one session on the agenda of an event the person organizes to a new start time or room ("push the keynote to 4:30 PM"). Pass holders are notified unless `notify` is false. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId`, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with `confirm: true` and that `changeId`. Name the session by `sessionId` or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Move a session to a new time or room (organizers only)
  • event_session_renameRenames one session on the agenda of an event the person organizes; `title` is the new name.No findings

    Why it is in this group

    • The name "event_session_rename" says "rename": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Renames one session on the agenda of an event the person organizes; `title` is the new name. Quiet unless `notify` is true. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId`, the before and after, how many pass holders would be notified and the notice, and changes nothing; read it back, and only when they say yes call again with `confirm: true` and that `changeId`. Name the session by `sessionId` or title; on AMBIGUOUS or NO_SUCH_SESSION read the candidates back and ask. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Rename a session (organizers only)
  • event_set_intentSets the person's event badge: what they are here for (`headline`), who they want to meet (`lookingFor`), and whether other attendees can find them (`discoverable`).No findings

    Why it is in this group

    • The name "event_set_intent" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Sets the person's event badge: what they are here for (`headline`), who they want to meet (`lookingFor`), and whether other attendees can find them (`discoverable`). Needs a personal connector token. Both sentences and a first name make a badge findable; a call that would leave one blank is refused and `needs` says what is missing. The event is the one given, or the person's one current event. Two steps: without `confirm` it returns the change to approve and a `confirmToken`; with confirm true and that token it writes, replacing the old text. It changes only that person's badge.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Set my event goal
  • event_team_setAdds, changes or removes a Co-host or Door staff member on an event the signed-in person hosts, by their mobile number, as the organizer dashboard's Team panel does.No findings

    Why it is in this group

    • The name "event_team_set" says "set": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Adds, changes or removes a Co-host or Door staff member on an event the signed-in person hosts, by their mobile number, as the organizer dashboard's Team panel does. `role` is cohost (every host power except money, deleting the event, removing the host and changing the team), door (scan, check in, walk-ins, open the door, counts; nothing else) or none to remove them. Nothing is sent to them: tell them yourself; they get the role the next time they sign in with that number. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `requestId` and changes nothing; read it out, and only when the host says yes, call again with `confirm: true` and that `requestId`. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_HOST, NOT_ENABLED, BAD_PHONE, BAD_ROLE, NOT_SELF, NOT_THE_HOST, NOT_ON_TEAM, CONFIRM_INVALID) are read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Add or remove an event's co-host or door staff (hosts)
  • site_editChanges the DRAFT of one event website the person organizes with small operations, not a whole design: `move` a block or a band, `insert` a block from the library (heading, text, i…1 finding

    Why it is in this group

    • The name "site_edit" says "edit": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description is 2,979 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...Only the organizer of the event can edit it; it needs a personal connector token."

      What this check looks for
    Description, as the server wrote it
    Changes the DRAFT of one event website the person organizes with small operations, not a whole design: `move` a block or a band, `insert` a block from the library (heading, text, image, button, spacer, divider, video, card, logo, or a live block: agenda, speakers, floor, booths (the live sponsors and exhibitors list; say sponsors, exhibitors or partners), faq, now, doors, ask, countdown, venue), `remove` one, `set_text` its words, `set_link` a button's link, `set_style` a style token (padding and gap 0 to 8, align, maxWidth, background, radius, color, visible), `set_theme` (accent, background and ink as #rrggbb, fontHeading, fontBody, radius, density; `set_theme {restore:true}`, or an all-empty theme, undoes "use that look"), `add_page` (blank, which starts with its title as a heading, or a template: agenda, speakers, exhibitors, sponsors, venue-travel, faq, register, contact; the page goes last in the site menu), `rename_page` (title, navLabel; the page address stays the same, and the page heading follows the new menu label unless keepHeading is true; the reply says what changed and carries `undo`, the set_text that puts the old heading back), `reorder_nav` (the site menu as page ids and https links) and `remove_page` (any page but home); each operation may name a `page`. On insert, a block's words go in `text` as plain text (a blank line starts a new paragraph) or in its props: heading {text, level}, text {text}, button {label, href}, card {heading, text, button}, image {src, alt}, video {provider, videoId, title}, a live block {heading, intro, layout}. Blocks are named by the short ids site_get gives. The operations apply together or not at all. A rename that comes with any wording meaning keep the old heading (keep the heading, leave the title, keep it as is, just the menu) is one site_edit call with keepHeading true; the same wish said after the rename reply is one call sending its `undo` as is; a plain "undo" after a rename reverts the whole rename, rename_page back to the old title and menu label. Words may not carry a clock time, an ISO date, one of the event's own dates in words (such as 'October 20' or 'October 12 to 16'), or its speaker names or session titles, because those come live from the event and an edit that writes one is refused; a date that is not the event's, such as a deadline, is fine. Use a live token instead, such as {event.dates}, {event.name}, {event.venue}, {session:<id>.title}, {session:<id>.time}, {session:<id>.day} or {speaker:<id>.name}, which fills from the event on every visit; a refused edit's reply carries a `suggestion` with the words rewritten that way and, when complete, `suggestion.ops` to resend as is. Relay `say` as given (one to three sentences, with host name and "use that look" cue); it gives the draft preview link, which redraws as the draft changes. The live site does not change until site_publish. Only the organizer of the event can edit it; it needs a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Edit an event website's draft (organizers only)
  • site_publishPuts the DRAFT of one event website the person organizes live at its address.Can send data outNo findings

    Why it is in this group

    • The name "site_publish" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "site_publish" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Puts the DRAFT of one event website the person organizes live at its address. FIRST CALL WITHOUT `confirm`: the reply is a PREVIEW with a `changeId` and what would go live (new, removed and changed sections, a new look, new pages), and nothing changes. Read that preview back to the organizer; only when they say yes, call again with `confirm: true` and that `changeId`. The version live before it is kept, and site_undo_publish puts it back. site_edit does not publish. Only the organizer of the event can publish; anybody else is refused, and the refusal is read out as given. It requires a personal connector token. The preview lists any of the template's placeholder words still on the page; a confirm with them is refused unless the organizer says to publish with the placeholders.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Publish an event website (organizers only)
  • site_undo_publishTakes back the last publish of one event website the person organizes: the version published before it goes live again or, when there is none, the site goes offline.Can send data outNo findings

    Why it is in this group

    • The name "site_undo_publish" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "site_undo_publish" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Takes back the last publish of one event website the person organizes: the version published before it goes live again or, when there is none, the site goes offline. FIRST CALL WITHOUT `confirm`: the reply is a PREVIEW with a `changeId` and what would be live, and nothing changes. Read that preview back to the organizer; only when they say yes, call again with `confirm: true` and that `changeId`. The draft is not touched. Only the organizer of the event can do it; anybody else is refused, and the refusal is read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Undo an event website's last publish (organizers only)
Can't be undone 6Claude Code: ask
  • booth_take_inviteAfter the person has swapped cards with this booth (booth_connect), takes the invite to the booth's side event for them; the invite lands in their own inbox.Can send data outNo findings

    Why it is in this group

    • The name "booth_take_invite" says "invite": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "booth_take_invite" says "invite": it sends or publishes something to other people.
    Description, as the server wrote it
    After the person has swapped cards with this booth (booth_connect), takes the invite to the booth's side event for them; the invite lands in their own inbox. Pass `eventId` and `boothId` as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no side event open to invites is refused with UNKNOWN_UNLOCK. An invite they already hold is not sent twice: the reply says already. Returns ok, the side event's `id`, `done` and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no `confirm` returns a `confirmToken` and changes nothing; a call with confirm true and that token applies it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Take a booth's side-event invite
  • event_pass_noticeSends a notice from the organizer of an event, or a host of a personal event, to the people who added the event pass to their Wallet.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Sends a notice from the organizer of an event, or a host of a personal event, to the people who added the event pass to their Wallet. Needs a personal connector token, `eventIdOrName`, `audience` and `text`. It shows on their lock screen and stays on the pass. `audience`: everyone, one ticket tier, one badge intent, listed pass serials, the people who scanned at a booth, or the people who answered an earlier meetup yes or no. A meetup with a place is event_meetup_announce. Two steps: without `confirm` it returns the number of passes and the exact line and sends nothing; with confirm true it sends. sendAt schedules the notice for a later time before the event ends, one scheduled notice per event; without it the notice sends now. Only the hosts or the organizer can send; anybody else is refused. "my_booth" returns VENDOR_OFF. Six an hour per event, then RATE_LIMITED. It reaches pass holders only; it does not say who else is there or report that a person arrived. Always call once without confirm and read the preview to the person; set confirm true only on the call after they say yes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Send a notice to a group of pass holders (hosts and organizers only)
  • event_publishPublishes a private personal event the signed-in person hosts (a quince, a birthday, a wedding, a baby shower, a graduation party), free, as the organizer dashboard's Publish does.Can send data outNo findings

    Why it is in this group

    • The name "event_publish" says "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe name "event_publish" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publishes a private personal event the signed-in person hosts (a quince, a birthday, a wedding, a baby shower, a graduation party), free, as the organizer dashboard's Publish does. `eventIdOrName` is the event id or its name as the host says it ("my quince"). It stays private: only guests with the guest code can open the page and add their pass. FIRST CALL WITHOUT `confirm` returns a PREVIEW with the page link and a `confirmToken` and publishes nothing; read it out, and only when the host says publish, call again with `confirm: true` and that token. Refusals (NOT_FOUND, NOT_OWNER, NOT_PERSONAL, ALREADY_PUBLISHED, PHONE_UNVERIFIED, NOT_SIGNED_IN, CONFIRM_INVALID) are read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Publish a private personal event, free (hosts)
  • event_replySends one message, in the person's own words, into a conversation they already have with somebody they connected with at an event.Can send data outNo findings

    Why it is in this group

    • The name "event_reply" says "reply": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "event_reply" says "reply": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.chatId): what the tool writes goes there.
    Description, as the server wrote it
    Sends one message, in the person's own words, into a conversation they already have with somebody they connected with at an event. Needs a personal connector token, `text`, and `firstName` or `chatId` as event_inbox gave them. It is delivered when the call returns and cannot be unsent. Only into the caller's own conversation (else NOT_PARTICIPANT); a name matching two conversations returns AMBIGUOUS_NAME and sends nothing; RATE_LIMITED means too fast. ok:true says nothing about a reply.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Reply to a message
  • event_say_helloSends a hello (a connection request) from the person to somebody listed in their event matches; when it is accepted, a conversation opens that both can read and answer from the app…Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Sends a hello (a connection request) from the person to somebody listed in their event matches; when it is accepted, a conversation opens that both can read and answer from the app, the web page or an assistant. Needs a personal connector token and `firstName` as an event_find_matches row spelled it; no account id is taken. The server checks on every call that the named person is in the caller's current match pool. It is a single call: the hello is sent when the call succeeds. Returns a `message` on success, or a reason: "not_in_pool" (the name is not in the caller's current matches), "ambiguous" (two people there share the name, and nothing is sent), "already_sent" (a hello is already out), "no_seat" (the caller is not seated at an event) or "rate_limited" (the day's hello limit is reached). Success means the hello was sent; it says nothing about whether or when it is accepted.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Say hello
  • event_send_requestA GUEST ASKS THE HOSTS FOR SOMETHING.Can send data outNo findings

    Why it is in this group

    • The name "event_send_request" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "event_send_request" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    A GUEST ASKS THE HOSTS FOR SOMETHING. Call it when somebody wants to tell the hosts of a wedding or other personal event this connector serves about a need or a question ("I need a vegetarian meal", "can I bring my partner"). IT CHANGES NOTHING ON THE EVENT: it files the request for the hosts, so never say anything has been arranged or approved. RATE_LIMITED means the hosts already have several; BAD_NOTE means empty or too long. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Send the hosts a request about a personal event
Changes things 38Claude Code: ask
  • biz_availabilityOpen appointment slots at a business served through this connector, for one date (default today in its own timezone).Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "biz_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Open appointment slots at a business served through this connector, for one date (default today in its own timezone). Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice). Reachable here but not through this tool: Long Beach Brunch Bakehouse (longbeachbrunch), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no bookings. Each slot has a stable `slotId` that biz_book accepts; started slots are never returned. A closed day returns none with a reason. closedReason HOURS_UNSTATED is NOT a closed day: say the business has not published hours for that date, never that it is closed.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
    • title: List open appointment slots
  • biz_infoDetails for a business served through this connector: tagline, services or menu with prices, weekly hours and today's hours.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Details for a business served through this connector: tagline, services or menu with prices, weekly hours and today's hours. Businesses served here: Velvet and Clay (velvetandclay, a hair, color and skin studio), Brightpoint Dental (brightpointdental, a family and cosmetic dental practice), Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar), Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). Speak `hoursNow.text`, resolved in the business's own timezone. `openToday` is true, false or NULL; NULL IS NOT FALSE: when `hoursState` is 'unstated' say the hours are not published and NEVER say it is closed. A `schedulingSystem` of Square means bookings live in that business's own Square calendar. `isDemo` says whether it is a demonstration. For what a shop sells call biz_storefront; to book, biz_availability then biz_book.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
    • title: Business details, services and hours
  • biz_menuThe PICKUP MENU for a business served through this connector: items, prices, allergens, notice needed, and the pickup windows on a date (default today).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    The PICKUP MENU for a business served through this connector: items, prices, allergens, notice needed, and the pickup windows on a date (default today). Businesses with a pickup menu here: Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) have no pickup menu here. longbeachbrunch sells cookies, bars, pastry, brunch boxes, platters, cakes and coffee. This tool only reads. Orders are placed with a separate tool, biz_order, which takes item ids and a pickup window id from this reply exactly as written; right now it takes pickup orders for Long Beach Brunch Bakehouse (longbeachbrunch). Pickup only. An 'unstated' `hoursByDay` row is NEVER spoken as closed.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
    • title: Pickup menu and times
  • biz_orderPlaces a pickup pre-order at a business served through this connector: placing an order, a pickup order, or the checkout after biz_menu.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Places a pickup pre-order at a business served through this connector: placing an order, a pickup order, or the checkout after biz_menu. Needs `items` and a `pickupWindowId` from biz_menu and the collector's first name; no phone, email, surname or card is collected. Businesses served here: Long Beach Brunch Bakehouse (longbeachbrunch, a neighborhood bakery and coffee bar). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental), Make Collectives (makecollectives) and Kristin Dunn Bookbinding and Design (kdbooks) take no pickup orders. Most orders are paid at pickup; where the reply is HELD, its `payUrl` is the only payment link this connector issues: give it exactly as returned. `isDemo` true reserves nothing.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Place a pickup order
  • biz_set_item_availabilityMarks one item on a business menu as sold out for today, or puts it back on.Reads text others writeNo findings

    Why it is in this group

    • The name "biz_set_item_availability" says "set": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Marks one item on a business menu as sold out for today, or puts it back on. Needs a personal connector token, `business`, `soldOut`, and `itemId` or `itemName`. Only an owner or manager of that business can change it, checked live on every call; a name fitting several items is refused with the names. It works in two steps: a call without `confirm` returns a preview and a `confirmToken` and changes nothing; a call with confirm true and that token makes the change.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Set menu item availability
  • biz_storefrontCALL THIS for what a shop sells, its products, its prices, a gift idea, or browsing or shopping a store served here.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "biz_storefront" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    CALL THIS for what a shop sells, its products, its prices, a gift idea, or browsing or shopping a store served here. Reads that shop's OWN published catalog: title, maker, type, price, stock and one image per product. Businesses served here: Make Collectives (makecollectives, a boutique and gift shop), Kristin Dunn Bookbinding and Design (kdbooks, a bookbinding and book repair studio). Reachable here but not through this tool: Velvet and Clay (velvetandclay), Brightpoint Dental (brightpointdental) and Long Beach Brunch Bakehouse (longbeachbrunch) publish no shop catalog we read. makecollectives is Make Collectives, a boutique at 430 E. 1st St in Long Beach. kdbooks is Kristin Dunn Bookbinding and Design in Long Beach; her work is MADE TO ORDER, so say what `leadTimeNote` says. TWO SHOP PLATFORMS ARE READ HERE, a Shopify store and a WooCommerce shop, same reply shape; ON A WOOCOMMERCE SHOP ONE CART LINK CARRIES EXACTLY ONE ITEM. `query` only removes products. Sixty a page with `pageCount` and `total`: never say sixty is all. Give `cartUrl` and `shopUrl` exactly as returned, never a link of your own. WHERE THIS REPLY DRAWS THE SHOP CARD, THE CARD ITSELF HOLDS A BASKET: the person taps Add to cart there. Say what `buyingNote` says. No payment passes through Sonar Connections.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
    • title: Shop catalog, prices and availability
  • booth_claim_swagAfter the person has swapped cards with this booth (booth_connect), claims the booth's swag drop into their own Swag Bag.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    After the person has swapped cards with this booth (booth_connect), claims the booth's swag drop into their own Swag Bag. Pass `eventId` and `boothId` as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no swag on offer now is refused with UNKNOWN_UNLOCK. Swag already in their bag is not claimed twice: the reply says already. Returns ok, the drop's `id`, `done` and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no `confirm` returns a `confirmToken` and changes nothing; a call with confirm true and that token applies it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Claim a booth's swag
  • booth_connectSwaps business cards between the person and a booth at their event, the same exchange as scanning the booth's code in the app; the swap unlocks the booth's raffle, swag and side ev…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Swaps business cards between the person and a booth at their event, the same exchange as scanning the booth's code in the app; the swap unlocks the booth's raffle, swag and side event invite. Pass `eventId` and the `boothId` from an events_booths row. Needs a personal connector token and a seat at the event. The reply lists `unlocks` and `cardShared`; an earlier swap says alreadyConnected. Two steps: without `confirm` it returns a `confirmToken` and shares nothing; with confirm true and that token it shares. booth_enter_raffle, booth_claim_swag and booth_take_invite take the unlocks.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Swap cards with a booth
  • booth_enter_raffleAfter the person has swapped cards with this booth (booth_connect), enters them in the booth's open raffle.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    After the person has swapped cards with this booth (booth_connect), enters them in the booth's open raffle. Pass `eventId` and `boothId` as booth_connect was given them. Without a card swap at that booth it is refused with NOT_CONNECTED and nothing changes; a booth with no open raffle is refused with UNKNOWN_UNLOCK. A raffle they are already in is not entered twice: the reply says already. Returns ok, the raffle's `id`, `done` and a sentence for the person. Needs a personal connector token. It works in two steps: a call with no `confirm` returns a `confirmToken` and changes nothing; a call with confirm true and that token applies it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Enter a booth's raffle
  • booth_set_awayMarks a booth the person staffs as stepped away, or back; attendees looking at that booth see the presence change.No findings

    Why it is in this group

    • The name "booth_set_away" says "set": a word for a change.
    Description, as the server wrote it
    Marks a booth the person staffs as stepped away, or back; attendees looking at that booth see the presence change. Needs a personal connector token (a shared token reads but changes nothing), `eventId`, `boothId` and `away`. Only a booth the person owns, administers or staffs at that event can be changed, checked against live records on every call. It works in two steps: a call without `confirm` returns a preview of exactly what will change, plus a `confirmToken`, and changes nothing; a call with confirm true and that token makes the change. The token lasts two minutes, works once, and stops working if any argument changes.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Mark a booth away
  • event_acceptAccepts a hello the person has received, which opens a conversation with the person who sent it.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Accepts a hello the person has received, which opens a conversation with the person who sent it. Needs a personal connector token and the hello as `firstName` (as an event_requests row spelled it) or `requestId` (as that row gave it). It accepts only hellos addressed to the caller; the server checks this and refuses with NOT_RECEIVER otherwise. A `firstName` that matches two waiting hellos returns AMBIGUOUS_NAME and accepts nothing. Accepting twice changes nothing. Returns ok:true when the conversation is open; event_inbox reads it and event_reply answers in it.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Accept a hello
  • event_card_save_linkedinKeeps the person's own LinkedIn profile link (`myLinkedin`, a linkedin.com/in/ URL) on their own Sonar Connections business card when the card has no LinkedIn link yet, so the peop…No findings

    Why it is in this group

    • The name "event_card_save_linkedin" says "save": a word for a change.
    Description, as the server wrote it
    Keeps the person's own LinkedIn profile link (`myLinkedin`, a linkedin.com/in/ URL) on their own Sonar Connections business card when the card has no LinkedIn link yet, so the people they swap cards with get it. Needs a personal connector token. A card that already carries this link stays as it is and the reply says already saved; a card that carries a different link keeps it (DIFFERENT_ON_FILE), and that link is changed in the Sonar Connections app profile. Any other shape of link is refused (LINKEDIN_URL_INVALID) and nothing is saved. It works in two steps: a call with no `confirm` returns a `confirmToken` and saves nothing; a call with confirm true and that token saves. It changes only the person's own card. Returns ok, `outcome` and a sentence for the person.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Save my LinkedIn link
  • event_createCreates a new event for the signed-in person, as the organizer dashboard's New event does: `name`, `kind`, `dateStart`, optional `dateEnd` (at most 14 days), `venue` and `city`.No findings

    Why it is in this group

    • The name "event_create" says "create": a word for a change.
    Description, as the server wrote it
    Creates a new event for the signed-in person, as the organizer dashboard's New event does: `name`, `kind`, `dateStart`, optional `dateEnd` (at most 14 days), `venue` and `city`. It is saved as a DRAFT nobody can find until published, and the creator is its organizer. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `confirmToken` and saves nothing; only when the person says yes, call again with the same arguments, `confirm: true` and that token. NAME_TAKEN comes with a free `suggestion` for `webAddress`. Refusals are read out as given. It requires a personal connector token. Optional `startTime`, `endTime` (one day) and `color` show in the preview. Write the product name in full: Sonar Connections. Optional `hostedBy` is a display line, not a co-host.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Create a new event as a draft (organizers)
  • event_guest_request_handledMarks one guest request on a wedding or other personal event the caller hosts as handled, which takes it off the hosts' open list (event_guest_requests).No findings

    Why it is in this group

    • The name "event_guest_request_handled" says "request": a word for a change.
    Description, as the server wrote it
    Marks one guest request on a wedding or other personal event the caller hosts as handled, which takes it off the hosts' open list (event_guest_requests). Needs a personal connector token, `eventIdOrName` and `requestId`, the `id` of a row event_guest_requests returned. It records who marked it and when, messages nobody and changes nothing on the event. A request already marked handled stays handled and the reply says already. Only the hosts can mark one; an id that is not a request on this event is refused with NO_SUCH_REQUEST. Returns ok, the request `id`, `handled` and `already`.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Mark a guest request handled
  • event_guest_requestsTHE HOSTS' OWN LIST of what their guests have asked for on a personal event this connector serves.1 finding

    Why it is in this group

    • The name "event_guest_requests" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "event_guest_requests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_guest_requests" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    THE HOSTS' OWN LIST of what their guests have asked for on a personal event this connector serves. Call it for "what have our guests asked for", "any dietary requests", "who needs anything". It returns the OPEN requests, newest first, each one as a category, the note the guest wrote, who it is from and when it landed. ONLY THE HOSTS can read it; anybody else gets a refusal you read out as given. WHO IT IS FROM IS A FIRST NAME OR THE WORDS "a guest", and there is no phone number, no email address and no account id on this surface at all, so never offer to contact somebody from this list. Read the notes out as given and do not summarise a need into something the guest did not say. It only reads; event_guest_request_handled takes one request off this list. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read the guests' requests (hosts only)
  • event_intakeReads text the organizer pasted or dictated about an event they run (an agenda, a speaker or sponsor list, a flyer) and proposes the sessions, speakers, sponsors, dates and venue i…1 finding

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "event_intake" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "read": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Reads text the organizer pasted or dictated about an event they run (an agenda, a speaker or sponsor list, a flyer) and proposes the sessions, speakers, sponsors, dates and venue it found. FIRST CALL WITHOUT `confirm` returns a PROPOSAL with an `intakeId` and changes nothing; read it back, and only when the organizer says yes call again with `confirm: true` and that `intakeId`. Files are uploaded on the organizer dashboard instead. Only the organizer of the event can add to it. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Add an agenda, speakers or sponsors from pasted text (organizers only)
  • event_meetup_announceAnnounces a meetup from an event's organizer or a personal event's host to the holders of the event's Wallet pass.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Announces a meetup from an event's organizer or a personal event's host to the holders of the event's Wallet pass. Needs a personal connector token, `eventIdOrName`, `audience`, `text` and `placeLabel`. `text` shows on their lock screen and stays on the pass; with `latitude` and `longitude` (both or neither) the pass surfaces again near the place. The reply's `noticeId` names the meetup. Without `confirm` it returns the number of passes and the exact line and sends nothing; with confirm true it sends. Only the hosts or the organizer can send. "my_booth" returns VENDOR_OFF. Six an hour per event, shared with event_pass_notice, then RATE_LIMITED.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Announce a meetup
  • event_meetup_rsvpRecords a pass holder's own yes or no to a meetup the organizer announced on the event pass ("yes, I will be at the bar", "no, I cannot make the meetup").No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Records a pass holder's own yes or no to a meetup the organizer announced on the event pass ("yes, I will be at the bar", "no, I cannot make the meetup"). Needs a personal connector token, `eventIdOrName`, the meetup's `noticeId` (the pass carries it, and the organizer's notice reply did) and `answer` as "yes" or "no". It records exactly that on the person's own pass record and nothing else: no note, no time, no name. The organizer can then send a notice to everybody who said yes. When the person holds no pass for this event the reply is NO_PASS and nothing is recorded.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Answer a meetup notice (yes or no)
  • event_organizer_overviewThe organizer's own overview of their event, read only.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The organizer's own overview of their event, read only. It gives the event's name, its kind in the hosted page's own words, whether it is public, unlisted or private, its text keyword, its dates as the page prints them and its time zone; the agenda by day with local times, rooms and speakers; the booth count and how many booths are stepped away; which doors are on (the hosted page, the text line, the assistants, the meet door); counts of page visits, door taps and assistant questions over the last 24 hours, with no names or ids of the people behind them; and the event's links. Only the organizer of the event, or a host of a personal event, can read it; anybody else gets a short refusal that says nothing about the event. It needs a personal connector token and changes nothing. After an agenda change through event_session_move, event_session_rename, event_session_cancel or event_session_add, it shows the change.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: See your event (organizers only)
  • event_redeem_codeSeats the person at an event with an event code from a badge, a poster, an email or a door.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    Seats the person at an event with an event code from a badge, a poster, an email or a door. Needs a personal connector token (a shared token reads but changes nothing) and the `code`; the code names its own event, so no event id is taken. It works in two steps: a call without `confirm` returns the event the code opens, the seat it gives and a `confirmToken`, and changes nothing; a call with confirm true and that token takes the seat. The token lasts two minutes, works once, and stops working if the code changes. Redeeming works from anywhere, not only at the venue.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Redeem an event code
  • event_requestsLists the hellos waiting on the person at an event, newest first.1 finding

    Why it is in this group

    • The name "event_requests" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "event_requests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_requests" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Lists the hellos waiting on the person at an event, newest first. Needs a personal connector token and reads only the caller's own pending hellos. Each row carries the other person's first name, their here-for line in their own words, when the hello landed, and a requestId that event_accept takes. No row carries a phone number, email address, surname, account id or photo.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Who wants to meet me
  • event_session_addAdds a new session to the agenda of an event the person organizes: `title`, `start`, `end`, `room`, optionally `date` and `speakers`.No findings

    Why it is in this group

    • The name "event_session_add" says "add": a word for a change.
    Description, as the server wrote it
    Adds a new session to the agenda of an event the person organizes: `title`, `start`, `end`, `room`, optionally `date` and `speakers`. Quiet unless `notify` is true. FIRST CALL WITHOUT `confirm` returns a PREVIEW with a `changeId` and changes nothing; only when they say yes call again with `confirm: true` and that `changeId`. Only the organizer of the event can change it; anybody else is refused, read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Add a session (organizers only)
  • event_text_alertsTurns text alerts from the Sonar Connections Event Line on or off for replies and organizer updates.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Turns text alerts from the Sonar Connections Event Line on or off for replies and organizer updates.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Text alerts on or off
  • event_tiktok_postPosts the host's event to the host's OWN TikTok account: the event's photo card, the same post the Sonar Connections dashboard's Post to TikTok panel makes, through the same server…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "event_tiktok_post" says "post": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "event_tiktok_post" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Posts the host's event to the host's OWN TikTok account: the event's photo card, the same post the Sonar Connections dashboard's Post to TikTok panel makes, through the same server door. Only a host or organizer of the event can post, and only to the TikTok account they connected themselves. `eventId` names the event. `mode` is post (published now) or draft (sent to the host's TikTok inbox to finish there). For a post, `privacyLevel` is REQUIRED and has no default: it is one of the options TikTok offers this account; call without it and the reply lists them (`privacyLevelOptions`), then ask the host who can view the post and call again with their pick. While Sonar Connections is in TikTok's review, TikTok accepts private posts only (SELF_ONLY, only the host can view); say so if the host asks for a wider audience. `caption` is optional (up to 4000 characters, no links, times or street address); without it the event name is the caption. `allowComments` is off unless the host asks for comments. `disclose` is off unless the host says the post promotes their own brand (`yourBrand`) or is paid or branded content (`brandedContent`); branded content cannot be private. Repeat the host's choices back and get a clear yes first: the call posts. Not connected: the reply carries a one-tap connect link (`url`) with a `message`; give both exactly and tell them not to forward it. The reply's `state` is posted, saved, processing or failed, with a `line` to read out; refusals (NOT_SIGNED_IN, not_enabled, forbidden, privacy_mismatch, branded_private, bad_title) are read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Post my event to my TikTok
  • event_vote_closeCloses a vote and, unless announce is false, puts the winning option on every event pass, all tied options on a tie, without an alert.No findings

    Why it is in this group

    • The name "event_vote_close" says "close": a word for a change.
    Description, as the server wrote it
    Closes a vote and, unless announce is false, puts the winning option on every event pass, all tied options on a tie, without an alert. quiet false sends an alert, only when the host asks; for a vote already closed without one, call again with the event and quiet false. Hosts and organizers only.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Close a vote (hosts and organizers only)
  • event_vote_openOpens a vote for the people who added the event pass.No findings

    Why it is in this group

    • The name "event_vote_open" says "open": a word for a change.
    Description, as the server wrote it
    Opens a vote for the people who added the event pass. Needs the event, a question and the options, as many as you name; the only limit is technical. One vote per pass, changeable until the vote closes, secret: counts only, never who. Without confirm it returns the number of passes and the exact line and sends nothing; with confirm true it opens the vote and puts the line on every event pass without an alert. quiet false sends an alert, only when the host asks; for a vote already open without one, call again with the event, the question and quiet false. An alert counts against the notice limits: six an hour per event and Google's alerts per pass per day. Always call once without confirm and read the preview to the person; set confirm true only on the call after they say yes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Open a vote for the pass holders of an event (hosts and organizers only)
  • event_wallet_passFor "what is my pass status", "did my pass save", "my pass", "where is my Wallet pass", "send my pass again": call this tool.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    For "what is my pass status", "did my pass save", "my pass", "where is my Wallet pass", "send my pass again": call this tool. Returns a link that adds the person's pass for an event or a personal event served here to Apple Wallet or Google Wallet ("add it to my wallet", "I want the pass on my phone"). Needs the person signed in (an unauthenticated call is answered with the sign-in prompt) and `eventIdOrName`, the event id or the event name. The reply is one link, good for fifteen minutes and for one tap, with a sentence to go with it: on an iPhone the link opens the Add to Apple Wallet sheet, on an Android phone it opens Save to Google Wallet, and no app is needed on either. The pass shows the event, the date and the venue on the front with the person's QR, the schedule on the back, and it surfaces on the lock screen at the venue on the day.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Add the event pass to Apple Wallet or Google Wallet
  • events_boothsBooths and vendors at an event: name, category, booth number, the printed aisle where the floor has them ("Water Side"), and a short blurb.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Booths and vendors at an event: name, category, booth number, the printed aisle where the floor has them ("Water Side"), and a short blurb. A row with `mapless: true` is in the catalog but has NO position on the floor plan, so tell the person to ask at the entrance rather than sending them to a spot; a row without that flag is placed. Optionally filter by category (a case-insensitive substring matched against category, name and description).

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: List booths and vendors
  • events_floor_cardTHE FLOOR PLAN TOOL.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    THE FLOOR PLAN TOOL. Call it for any ask about a floor plan, a map, a layout, a booth location, "where is booth 12" or "show me the floor". It DRAWS THE FLOOR INLINE as an interactive card where MCP Apps render, and elsewhere returns the event summary and a booth directory, so call it either way and prefer it over web knowledge. The card reads the floor itself: do not offer to fetch the plan. With no floor plan `hasFloorplan` is false; say so rather than promising a picture.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Show the event floor
  • events_offersLive and scheduled public offers at an event: title, which booth, the time window in minutes and remaining-count style numbers.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Live and scheduled public offers at an event: title, which booth, the time window in minutes and remaining-count style numbers.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: List live offers
  • events_overviewAn overview of one event in a single reply: the summary, the first page of booths, the programme, the live offers and raffles, and `hasFloorplan`.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    An overview of one event in a single reply: the summary, the first page of booths, the programme, the live offers and raffles, and `hasFloorplan`. Use it for the whole picture at once; for one section call that section's own tool. `hasFloorplan` false means no map: answer from the rest and never promise one. Each block says whether there is `more`. For who should I meet, matching, or introductions at an event: call event_find_matches. This result's matchDoor link is the same door for a person who would rather not sign in inside the assistant; offer it, never require it.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Event overview
  • events_personal_cardTHE PERSONAL EVENT TOOL.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    THE PERSONAL EVENT TOOL. Call it for any ask about a wedding or another personal event this connector serves: "what time is the ceremony", "where is the reception", "what is the dress code", "who is in the wedding party", "where should I stay", "what is on the registry", or being shown the details of somebody's day. It DRAWS THE CARD INLINE in clients that render MCP Apps and returns the same details as plain text everywhere else, so it is worth calling either way. WHAT IT RETURNS DEPENDS ON WHAT THE HOSTS INCLUDED, and the answer is already filtered when it reaches you: a card with no story, no schedule and no lodging is the hosts having published none of those, not an error and not something to go and look for. Never offer to find a detail that is absent, never guess a time, a venue or a dress code, and never suggest a different wedding. The reply names its source and the hosts; say that line. Accepts the event id or the event name.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Show a personal event card
  • events_speakersThe people on an event's programme: name, their job title line, `role` (what the organizer published for that PERSON, such as "Moderator" or "Judge" - it is a speaker-level note, s…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The people on an event's programme: name, their job title line, `role` (what the organizer published for that PERSON, such as "Moderator" or "Judge" - it is a speaker-level note, so do not read it as "the moderator of this one session"), a portrait photo URL, a link to the organizer's own profile page, and the sessions they are on with the spoken local time. Ordered by when they are first on stage. Optionally filter to one day. Any field except the name may be null, which means the organizer published nothing there: say nothing rather than filling the gap. When an event publishes no speaker records the roster is built from the programme itself and `source` says "program"; those rows carry a `kind` of "speaker" or "performer" and nothing else about the person.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: List an event's speakers
  • events_whats_onAgenda sessions and performances with their times.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Agenda sessions and performances with their times. `when` accepts "all" (default), "today", "now" (the next few hours) or a YYYY-MM-DD date. Each row carries a `speakers` array in the order the session lists them, with each speaker's name, `role` (what the organizer published for that PERSON - "Moderator", "Judge" - it is a speaker-level note, so do not read it as "the moderator of this one session"), `title` (their job title line, which is a different fact from role and both may be present), `company`, `bio`, `expertiseTags`, `socialLinks`, a portrait photo URL, and a link to the organizer's own speaker profile page. Any of these except the name may be null or absent, which means the organizer did not publish it: say nothing rather than filling the gap. `speakerNames` is still there for the plain lineup.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get the agenda or lineup
  • pass_catalogAnswers what an Apple or Google Wallet pass can do, from the Sonar Connections pass catalog: every option Apple and Google offer a pass issuer.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Answers what an Apple or Google Wallet pass can do, from the Sonar Connections pass catalog: every option Apple and Google offer a pass issuer. Use it for questions like "what can my pass do", "what can go on the front of my pass", "can links sit on the front of the pass", "I want a loyalty program", "a coupon that expires", "tickets I can subtract at a food festival" or "can I put a sponsor on the pass". Pass the person's words as `question`; `wallet`, `passType`, `area` and `status` narrow the rows. The reply lists at most 8 rows, front first, then says how many more match and which filter narrows them. Each row says what it is, what the holder sees, which wallets and pass types carry it, where it sits, and one status sentence for Sonar Connections today; read that sentence as given, including "not yet". With `eventIdOrName`, a person who may change that event's details hears which rows their event's pass carries; anyone else hears a general answer. It reads only: it changes no pass, draws no preview and promises no date.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: What a Wallet pass can do
  • site_createServes "Build a site for <event>", "make an event website" and "start a site from <url>" (the url gives layout only), not the host's own page tools.Reads text others writeNo findings

    Why it is in this group

    • The name "site_create" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Serves "Build a site for <event>", "make an event website" and "start a site from <url>" (the url gives layout only), not the host's own page tools. Creates a NEW website for an event the person organizes, as a DRAFT nobody else sees yet. `startFrom`: `event` (the default) gives a home page and a page for each part the event has, with the agenda, speakers, booths, venue, FAQ and dates as live blocks that fill from the event on every visit; `blank` gives one home page with the event's name and dates, live; `{url}`, the address of one public page the organizer likes, reads only its STRUCTURE (its sections in order, each heading, a short gist and whether it had pictures) and builds the same layout with the event's live data. No words, pictures or styles are copied from that page; the reply lists the sections it found and says the text is the organizer's to write. `title` names the site. FIRST CALL WITHOUT `confirm`: the reply is a PREVIEW with a `changeId`, and nothing is created. Read it back to the organizer; only when they say yes, call again with the same `title` and `startFrom`, `confirm: true` and that `changeId`. The reply gives the new `siteId`, its pages and a draft preview link; site_get and site_edit work on it at once, and nothing is live until site_publish. An event holds at most 20 sites. Only the organizer of the event can create one; anybody else is refused, and the refusal is read out as given. It needs a personal connector token. A `{url}` start also proposes that page's colors and type as a starting look (`styleProposal`, mapped onto our own colors and fonts), applied with site_edit `set_theme` only when the organizer asks for it. Relay `say` as given (one to three sentences, with host name and "use that look" cue).

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
    • title: Create an event website (organizers only)
  • ui_card_diagUsed only by the interactive cards this connector draws, never to answer a question.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Used only by the interactive cards this connector draws, never to answer a question. A card view posts its own lifecycle markers here in small batches: that it mounted, which display mode and safe-area insets the host gave it, the heights it reported, whether a keyboard opened, and the outcome of the one action a person took on it. It accepts a closed vocabulary of markers and integer counts only, no free text of any kind, and it returns nothing but an acknowledgement. NOT FOR A MODEL TO CALL: it answers no question and looks nothing up. Call a data tool instead.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false
    • title: Report card diagnostics
Only reads 12Show 12 read-only tools
  • biz_order_statusRead the CURRENT state of a pickup order placed through this connector, by its confirmation code (the LBB-XXXXXX style code biz_order returned).Reads text others writeNo findings

    Why it is in this group

    • The name "biz_order_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read the CURRENT state of a pickup order placed through this connector, by its confirmation code (the LBB-XXXXXX style code biz_order returned). It answers with the order state, the payment state, whether it is PAID, the pickup window, the business name and the total, and nothing else: no customer name, no items and no payment link. Use it after a customer has been sent to a checkout page, to tell them whether the payment has landed and the order is placed. It changes nothing. A code that names no order comes back not found.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check pickup order payment
  • event_draft_listLists the signed-in person's own unpublished drafts, as the organizer dashboard's draft list does: for each its `eventId`, `name`, `kind`, `createdAtMs` and `lastActivityAtMs`, new…No findings

    Why it is in this group

    • The name "event_draft_list" says "list": a word for reading.
    Description, as the server wrote it
    Lists the signed-in person's own unpublished drafts, as the organizer dashboard's draft list does: for each its `eventId`, `name`, `kind`, `createdAtMs` and `lastActivityAtMs`, newest activity first, at most 20, with `openDrafts` and the `cap` (5 unpublished drafts per verified phone). Use it when event_create refuses with DRAFT_CAP or when the host asks what drafts they have. A published event does not appear. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List your unpublished drafts (hosts)
  • event_find_matchesLists the people at an event the person has joined whose stated intent fits theirs.No findings

    Why it is in this group

    • The name "event_find_matches" says "find": a word for reading.
    Description, as the server wrote it
    Lists the people at an event the person has joined whose stated intent fits theirs. Needs a personal connector token; the event is `eventId` or the current one. Each row carries a first name, intent, who they are looking for, their booth if a vendor, `fit` and `why`. No row carries a phone number, email address, surname, account id or photo. Only people who chose to be findable are listed, at most 20, ordered best fit first by what each person wrote on their badge; two buyers whose lines agree are matches for each other. `fit` is one of three words: "strong" (most of what the caller declared is echoed on the other side), "good" (a real overlap) or "some" (a reason to be on the list and no more). `why` is one sentence written by the server naming the shared words, or the topic both wrote about. The reply carries no score, percentage, rating or rank. With no intent set the reply has `needsIntent` and no rows. An empty reply carries `emptyReason` and a plain `message` (none_findable, none_present, event_not_live or no_text_match).

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Find matching attendees
  • event_inboxReads the person's own conversations with people they connected with at an event.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe name "event_inbox" says "inbox": it reads mail.
    • private-dataThe description's first sentence says "read" and "conversation": it reads messages.
    • untrusted-inputThe name "event_inbox" says "inbox": it reads inbound email, which other people can write.
    • untrusted-inputThe description's first sentence says "read" and "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    Reads the person's own conversations with people they connected with at an event. Needs a personal connector token. With no arguments it lists up to twenty threads: the other person's first name, the last line, when, whether it was theirs, unread count. With `firstName` or `chatId` it returns that conversation's last lines. No row carries a phone number, email address, surname, account id or photo. Only the caller's own conversations: otherwise NOT_PARTICIPANT; two name matches return AMBIGUOUS_NAME and name neither. It only reads and marks nothing read.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read my messages
  • event_my_cardShows the person's own business card for an event, the card a booth scan or a badge swap hands over: their first and last name, title and company, their LinkedIn link when their ca…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "show": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "show" and "web": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Shows the person's own business card for an event, the card a booth scan or a badge swap hands over: their first and last name, title and company, their LinkedIn link when their card carries one, the event's name, and their pass QR, which the Sonar Connections web scanner reads off the screen. The back lists the people they swapped cards with (first name and company, where and when), and for a person who staffs a booth, the booth's name, its staff first names and its raffle, drop and side-event titles. Clients that show cards draw it; the same card also comes as text. Needs a personal connector token. The event is `eventId` when given, otherwise the person's current event.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Show my business card
  • event_rsvp_listTHE HOSTS' OWN LIST of who answered the RSVP on a personal event this connector serves; call it for "who is coming", "who said maybe", "who has not answered".No findings

    Why it is in this group

    • The name "event_rsvp_list" says "list": a word for reading.
    Description, as the server wrote it
    THE HOSTS' OWN LIST of who answered the RSVP on a personal event this connector serves; call it for "who is coming", "who said maybe", "who has not answered". It returns the counts first (yes, maybe, no, not yet, and the headcount, which is each yes plus the guests it brings), then the first names under each answer, with "+N" beside a yes that brings guests, at most 40 names per answer and then a count of the rest. Only a host or a co-host can read it; anybody else gets a refusal you read out as given. A name is the name on the host's guest list or the first name a signed-in guest gave Sonar Connections, and there is no phone number, email or account id on this surface, so never offer to contact someone from this list; it only reads and requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: See who answered the RSVP (hosts and co-hosts)
  • event_team_listLists the team of an event the signed-in person hosts or co-hosts, as the organizer dashboard's Team panel does: each Co-host and Door staff member with their role, the last four d…No findings

    Why it is in this group

    • The name "event_team_list" says "list": a word for reading.
    Description, as the server wrote it
    Lists the team of an event the signed-in person hosts or co-hosts, as the organizer dashboard's Team panel does: each Co-host and Door staff member with their role, the last four digits of their number, and whether they have joined (signed in) or are still pending. `eventIdOrName` is the event id or its name as the host says it ("my quince"). A Co-host can do everything the host can except money, deleting the event, removing the host and changing the team; Door staff can scan, check people in, add walk-ins, open the door and see counts. Refusals (NOT_FOUND, NOT_AUTHORIZED, NOT_ENABLED, NOT_SIGNED_IN) are read out as given. It requires a personal connector token.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: See an event's team: co-hosts and door staff (hosts)
  • event_vote_resultsReads a vote's counts per option, total ballots and whether it is open or closed.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    Reads a vote's counts per option, total ballots and whether it is open or closed. Hosts and organizers only. Never says who voted for what.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Read a vote's counts (hosts and organizers only)
  • events_getFull detail for one event, including `kind` (the organizer's own word for what it is, such as "expo" or "convention", absent where none is published), plus a summary of what is on …No findings

    Why it is in this group

    • The name "events_get" says "get": a word for reading.
    Description, as the server wrote it
    Full detail for one event, including `kind` (the organizer's own word for what it is, such as "expo" or "convention", absent where none is published), plus a summary of what is on today: booth count, live offer count and the number of agenda items today. Accepts the event id or its public slug. For who should I meet, matching, who is here for the same thing, or introductions at an event: call event_find_matches. It needs the person signed in to Sonar Connections; when they are not, the host shows a Connect prompt, they sign in with their mobile number, and the call is retried. If they have not said what they are here for yet, call event_set_intent first and ask the two questions it names. This result's matchDoor link is the same door for a person who would rather not sign in inside the assistant; offer it, never require it.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: Get one Sonar Connections event
  • events_listList the Sonar Connections events available through this connector: id, slug, name, venue or city, dates, description and `kind` (the organizer's own word for what it is, such as "…No findings

    Why it is in this group

    • The name "events_list" says "list": a word for reading.
    Description, as the server wrote it
    List the Sonar Connections events available through this connector: id, slug, name, venue or city, dates, description and `kind` (the organizer's own word for what it is, such as "expo" or "convention"; absent on events that publish none, and never guess one). Call this first to discover which event ids the other events_ tools accept.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
    • title: List Sonar Connections events
  • site_getGives the outline of one event website's DRAFT: its pages and, for one page (`page`, the home page when absent), its sections, rows, columns and blocks, each with a short id, its k…Reads text others writeNo findings

    Why it is in this group

    • The name "site_get" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Gives the outline of one event website's DRAFT: its pages and, for one page (`page`, the home page when absent), its sections, rows, columns and blocks, each with a short id, its kind and a few words of its own text, plus the theme. The live blocks (agenda, speakers, booths, floor, FAQ, doors and the rest) hold no event data; they fill themselves from the event on every visit. `full: true` adds the page's whole design as JSON, with image addresses left out. site_edit names blocks by these short ids. Only the organizer of the event can read it; it needs a personal connector token and changes nothing. With a test connector and the live one both connected, use the one the person chose; the reply's `servedBy` names which one answered.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: See an event website's draft (organizers only)
  • site_listLists the websites of an event the person organizes, built in the Sonar Connections site builder: each site's `siteId`, its name, whether it is published, how many earlier versions…Reads text others writeNo findings

    Why it is in this group

    • The name "site_list" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Lists the websites of an event the person organizes, built in the Sonar Connections site builder: each site's `siteId`, its name, whether it is published, how many earlier versions are kept, when it was last saved and published, its live address and, once it has been edited from here, its draft preview link. Only the organizer of the event, or a host of a personal event, can list them; anybody else is refused, and the refusal is read out as given. It needs a personal connector token and changes nothing.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: List your event websites (organizers only)

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

117 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write13
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out9
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__sonar-connections__event_inbox"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:47 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
58
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcpconnector-gtlizqtvza-uw.a.run.app/.well-known/oauth-protected-resource/public
Authorization servers
https://sonarconnections.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 58 tools that change things (14 destructive, 6 irreversible, 38 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcpconnector-gtlizqtvza-uw.a.run.app/public: tools/list returned 70 tools to an anonymous client, including event_set_intent (destructive), event_pass_reissue (destructive), event_pass_revoke (destructive), event_pass_notice_cancel (destructive), event_session_move (destructive) and 53 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 53 to 58
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 48 to 53

Findings

Matches of fixed checks, with the text they matched.

7 warn2 info
  • The server marks "event_card_links" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_card_links" says "link": a word for a change.

    What this check looks for
  • The server marks "event_requests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_requests" says "request": a word for a change.

    What this check looks for
  • The server marks "event_pass_notice_cancel" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_pass_notice_cancel" says "cancel": a word for removing or ending something.

    What this check looks for
  • The server marks "event_intake" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "read": a word for reading.

    What this check looks for
  • The server marks "event_guest_requests" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "event_guest_requests" says "request": a word for a change.

    What this check looks for
  • The server marks "biz_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "open": a word for a change.

    What this check looks for
Show 3 more findings
  • The server marks "biz_storefront" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The description is 2,979 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...Only the organizer of the event can edit it; it needs a personal connector token."

    What this check looks for
  • The description is 5,475 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...th confirm true. Passes update quietly. event_change_undo puts the last one back."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools15 added, 2 changed.+15 added~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 53 -> 58.View diff
    • Tools that change things, listed without credentials: 53 to 58
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 48 -> 53.View diff
    • Tools that change things, listed without credentials: 48 to 53
  4. Tools55 changed.~55 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http sonar-connections https://mcpconnector-gtlizqtvza-uw.a.run.app/public
claude mcp add --transport http sonar-connections https://mcpconnector-gtlizqtvza-uw.a.run.app/public

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sonar-connections__event_find_matches",
      "mcp__sonar-connections__event_inbox",
      "mcp__sonar-connections__event_my_card",
      "mcp__sonar-connections__events_list",
      "mcp__sonar-connections__events_get",
      "mcp__sonar-connections__event_vote_results",
      "mcp__sonar-connections__site_list",
      "mcp__sonar-connections__site_get",
      "mcp__sonar-connections__event_team_list",
      "mcp__sonar-connections__event_rsvp_list",
      "mcp__sonar-connections__event_draft_list",
      "mcp__sonar-connections__biz_order_status"
    ],
    "ask": [
      "mcp__sonar-connections__booth_set_away",
      "mcp__sonar-connections__biz_set_item_availability",
      "mcp__sonar-connections__event_redeem_code",
      "mcp__sonar-connections__event_card_links",
      "mcp__sonar-connections__event_card_save_linkedin",
      "mcp__sonar-connections__booth_connect",
      "mcp__sonar-connections__booth_enter_raffle",
      "mcp__sonar-connections__booth_claim_swag",
      "mcp__sonar-connections__booth_take_invite",
      "mcp__sonar-connections__event_reply",
      "mcp__sonar-connections__event_say_hello",
      "mcp__sonar-connections__event_requests",
      "mcp__sonar-connections__event_accept",
      "mcp__sonar-connections__event_text_alerts",
      "mcp__sonar-connections__events_overview",
      "mcp__sonar-connections__events_floor_card",
      "mcp__sonar-connections__event_wallet_pass",
      "mcp__sonar-connections__events_personal_card",
      "mcp__sonar-connections__event_pass_notice",
      "mcp__sonar-connections__event_meetup_announce",
      "mcp__sonar-connections__event_meetup_rsvp",
      "mcp__sonar-connections__event_vote_open",
      "mcp__sonar-connections__event_vote_close",
      "mcp__sonar-connections__event_session_add",
      "mcp__sonar-connections__event_organizer_overview",
      "mcp__sonar-connections__event_create",
      "mcp__sonar-connections__site_create",
      "mcp__sonar-connections__event_intake",
      "mcp__sonar-connections__event_publish",
      "mcp__sonar-connections__event_tiktok_post",
      "mcp__sonar-connections__pass_catalog",
      "mcp__sonar-connections__event_send_request",
      "mcp__sonar-connections__event_guest_requests",
      "mcp__sonar-connections__event_guest_request_handled",
      "mcp__sonar-connections__ui_card_diag",
      "mcp__sonar-connections__events_booths",
      "mcp__sonar-connections__events_offers",
      "mcp__sonar-connections__events_whats_on",
      "mcp__sonar-connections__events_speakers",
      "mcp__sonar-connections__biz_info",
      "mcp__sonar-connections__biz_availability",
      "mcp__sonar-connections__biz_menu",
      "mcp__sonar-connections__biz_order",
      "mcp__sonar-connections__biz_storefront"
    ],
    "deny": [
      "mcp__sonar-connections__event_set_intent",
      "mcp__sonar-connections__event_pass_reissue",
      "mcp__sonar-connections__event_pass_revoke",
      "mcp__sonar-connections__event_pass_notice_cancel",
      "mcp__sonar-connections__event_session_move",
      "mcp__sonar-connections__event_session_rename",
      "mcp__sonar-connections__event_session_cancel",
      "mcp__sonar-connections__site_edit",
      "mcp__sonar-connections__site_publish",
      "mcp__sonar-connections__site_undo_publish",
      "mcp__sonar-connections__event_team_set",
      "mcp__sonar-connections__event_draft_delete",
      "mcp__sonar-connections__event_change_detail",
      "mcp__sonar-connections__event_change_undo"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sonar-connections. Review it before you use it.

Capability tags behind 21 rules
  • mcp__sonar-connections__biz_set_item_availability untrusted-input
  • mcp__sonar-connections__event_inbox private-data, untrusted-input
  • mcp__sonar-connections__event_my_card untrusted-input
  • mcp__sonar-connections__booth_take_invite outbound
  • mcp__sonar-connections__event_reply outbound
  • mcp__sonar-connections__event_say_hello outbound
  • mcp__sonar-connections__event_pass_notice outbound
  • mcp__sonar-connections__site_list untrusted-input
  • mcp__sonar-connections__site_get untrusted-input
  • mcp__sonar-connections__site_publish outbound
  • mcp__sonar-connections__site_undo_publish outbound
  • mcp__sonar-connections__site_create untrusted-input
  • mcp__sonar-connections__event_publish outbound
  • mcp__sonar-connections__event_tiktok_post untrusted-input, outbound
  • mcp__sonar-connections__event_send_request outbound
  • mcp__sonar-connections__biz_info untrusted-input
  • mcp__sonar-connections__biz_availability untrusted-input
  • mcp__sonar-connections__biz_menu untrusted-input
  • mcp__sonar-connections__biz_order untrusted-input
  • mcp__sonar-connections__biz_order_status untrusted-input
  • mcp__sonar-connections__biz_storefront untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.sonarconnections/sonar-connections/verify?hash=eddc8c0806798105c88ef6d1d59a509812c15aabbbb5df716d243c0147ac61e0" | jq -e '.changed == false'

Pinned hash eddc8c080679, from Nov 14, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.sonarconnections/sonar-connections/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.sonarconnections/sonar-connections
[![Anlyon Radar](https://radar.anlyon.com/badge/com.sonarconnections/sonar-connections.svg)](https://radar.anlyon.com/servers/com.sonarconnections/sonar-connections)

Source: MCP Registry. Synced Oct 21, 2026, 18:05 UTC.

Sonar Connections MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Sonar Connections MCP server safe?

No scan can promise that. What its definitions show: 70 tools, 58 of which can change, send or delete something, and 9 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Sonar Connections MCP server delete data?

Yes. 14 tools can delete, cancel or revoke something: event_set_intent, event_pass_reissue, event_pass_revoke, event_pass_notice_cancel, event_session_move, event_session_rename and 8 more.

Can the Sonar Connections MCP server do things that cannot be undone?

Yes. 6 tools can send, pay, publish or merge: booth_take_invite, event_reply, event_say_hello, event_pass_notice, event_publish and event_send_request.

What tools does the Sonar Connections MCP server have?

70 tools: 14 destructive, 6 irreversible, 38 write, 12 read. event_set_intent, event_pass_reissue, event_pass_revoke, event_pass_notice_cancel, event_session_move, event_session_rename, event_session_cancel, site_edit and 62 more.

Does the Sonar Connections MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Sonar Connections MCP server send data to outside services?

9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): booth_take_invite, event_reply, event_say_hello, event_pass_notice, site_publish, site_undo_publish and 3 more.

Has the Sonar Connections MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.