Skip to content

Immersive Commons MCP server

com.immersivecommons/floor10immersivecommons.comstreamable-httpv1.1.0Scanned

RSVP to San Francisco AI events, book a room, borrow a VR headset, submit a 3D print, find members.

36 tools: 1 can delete or cancel things, 1 do something that can't be undone, 12 change things and 22 only read.

Tools: 1 delete, 1 irreversible, 12 write, 22 read.
  • Reads private data · 7
  • Reads text others write · 12
  • Can send data out · 1
  • 9 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does 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 Immersive Commons MCP server can do

The Immersive Commons MCP server is published by immersivecommons.com, a domain the MCP Registry verified. It has 36 tools. It can delete or cancel things (1 tool: ic_forms_withdraw), do things that cannot be undone, such as sending, paying or publishing (ic_scheduling_get_availability) and create or change data (12 tools: ic_donate, ic_funko_catalog, ic_funko_levels, ic_spatial_beta_program and 8 more). 22 tools only read.

7 tools read private data (ic_donations_total, ic_forms_get, ic_scheduling_list_meeting_types and 4 more); 12 tools bring in text other people can write (ic_signal_list_issues, ic_signal_get_latest, ic_donations_total and 9 more); 1 tool can send data out of your system (ic_scheduling_get_availability). 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 (credentials-mention, 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 10, 2026, version 1.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.

36 tools

Deletes or cancels 1Claude Code: deny
  • ic_forms_withdrawTake your human's own submission back.No findings

    Why it is in this group

    • The name "ic_forms_withdraw" says "withdraw": a word that usually means money moves, which cannot be taken back.
    • The description says "CANNOT BE UNDONE".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Take your human's own submission back. NO TOKEN REQUIRED, and no token grants this on anyone else's behalf: the ONLY things that open a record here are your human's signed-in identity or the submission_id plus the one-time claim_token handed back at submit. An operator cannot do it for them, a reviewer cannot do it for them, and `admin:forms_manage` does not reach this — withdrawing belongs to the person who submitted, because a reviewer withdrawing on somebody's behalf is a rejection wearing that person's name. CONFIRM WITH YOUR HUMAN BEFORE CALLING, in the plainest words you have. THIS CANNOT BE UNDONE BY ANYONE HERE: no reviewer can move a withdrawn record back, and on a form that asks for an email address, answering again on that address is REFUSED, so a withdrawal is not a way to redo an application. If they had been APPROVED, withdrawing hands their place back to the group and somebody on the waitlist can take it — `freed_slot` in the response tells you whether that happened, and it is the sentence to read to them. Idempotent: a record that was already withdrawn comes back ok with `changed: false` rather than an error, so a retry after a timeout is safe. A wrong id, a wrong token and an id that was never issued all return the same `found: false`, so this cannot be used to test which ids exist. Args: { form_id, submission_id?, claim_token? }. Returns: { ok, found, submission_id?, status?, previous_status?, changed?, already_withdrawn?, freed_slot?, counts?, message }. No auth required.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • ic_scheduling_get_availabilityOpen slots for one meeting type AND the member's full booking policy, in ONE response.Reads private dataCan send data out1 finding

    Why it is in this group

    • The name "ic_scheduling_get_availability" says "get": a word for reading.
    • The description's first verb is "open": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • private-dataThe description's first sentence says "meeting": it reads calendars.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

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

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ic_scheduling_get_availability" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Open slots for one meeting type AND the member's full booking policy, in ONE response. The policy is included deliberately so you can solve locally instead of probing: repeated narrowing calls are what turn a lookup into a negotiation, and this surface refuses to be negotiated with. Every start/end is UTC ISO-8601 with a trailing Z; member.tz and the echoed viewer_tz are IANA zone names — never do wall-clock arithmetic without one. READ complete BEFORE YOU READ slots. ok:true with complete:false is an INCOMPLETE SUCCESS, not a failure: part of the member's calendar could not be read, coverage.unknown_minutes says how much and unknown_windows[] says which windows and why. Those windows are OMITTED from slots, never guessed free — so do not tell your human the member is free then, and do not tell them the member is busy then either. The honest sentence is that we could not see part of their calendar. horizon.effective_to may be earlier than what you asked for when a member's constraint data runs out; that is 'not offered', which is a definite statement and is NOT the same fact as unknown. An empty slots with complete:true genuinely means booked solid or outside the window. NO TOKEN REQUIRED. The same reads are served by the scheduling service itself at https://sched.skew.site; its protocol document is https://sched.skew.site/v1/.well-known/scheduling. Args: { handle, meeting_type, from?, to?, tz? }. Returns: { ok, complete, member, meeting_type{duration_minutes,slot_granularity_minutes,min_notice_minutes,max_per_day,buffer_before_minutes,buffer_after_minutes,location_kind,requires_approval}, slots[], coverage, unknown_windows[], horizon?, generated_at }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
Changes things 12Claude Code: ask
  • ic_donateSupport Immersive Commons with an on-chain USDC donation over x402 (HTTP 402 + USDC on Base).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
    Support Immersive Commons with an on-chain USDC donation over x402 (HTTP 402 + USDC on Base). No auth required. Returns the donation tiers, the receiving wallet (payTo), the asset + network, and the donate URL. MCP can't run the in-band 402 handshake itself, so to donate: POST https://www.immersivecommons.com/api/x402/donate with an x402 X-PAYMENT header (sign an EIP-3009 USDC authorization for one of the tier amounts to payTo on the given network); the first call with no X-PAYMENT returns a 402 listing every tier in accepts[]. Optional donor { name, message } can be sent in the JSON body and appear on the public donor wall at /donate. Args: { tier?: string (a tier label, case-insensitive — narrows tiers[] to that single tier and adds `selected_tier` with the exact atomic USDC amount to sign; an unknown label returns error_kind:"validation" naming the valid labels) }.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ic_forms_submitSubmit answers to one form.No findings

    Why it is in this group

    • The name "ic_forms_submit" says "submit": a word for a change.
    Description, as the server wrote it
    Submit answers to one form. NO TOKEN REQUIRED — a form whose audience is `public` takes answers from a caller with no account at all, which is deliberate: the web page accepts anonymous submissions, so an agent path that demanded a token would make acting for your human HARDER than doing it by hand. Each form still declares its own audience ring and it is checked here, live, on every call; a refusal names the ring and how to ask for it, and is distinct from 'no such form'. THIS WRITES A REAL SUBMISSION UNDER A REAL PERSON'S NAME. CONFIRM EVERY ANSWER WITH YOUR HUMAN BEFORE CALLING THIS AND NEVER INVENT ONE — an answer you guessed becomes a promise they have to keep, and the gate questions in particular are commitments rather than preferences. Call ic_forms_get first for the question ids, kinds and exact allowed options. WHAT THIS IS: an expression of interest that opens a screening step — NOT a final application, and nothing is signed here. Do not tell your human they have applied; tell them they have raised their hand. If they are selected, a separate application arrives from the partner out of band. One submission per email address per form; a second is REFUSED and the first is NOT overwritten, so a correction goes to the form's contact address rather than a resubmit. A `claim_token` comes back ONLY for an unattributed submitter, and only once — surface it verbatim, because it is then the only way they can ever read their own submission again. A caller carrying an identity gets none and does not need one. Args: { form_id, answers }. Returns: { ok, submission_id, status, failed_gates, claim_token?, counts, message }. No auth required; a token only attributes the submission.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ic_funko_catalogThe full catalog of things a Funko Me figure can earn — animation clips, props, skins, stages — with the condition that unlocks each one.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 full catalog of things a Funko Me figure can earn — animation clips, props, skins, stages — with the condition that unlocks each one. No auth required; this is the rules table, not anybody's progress. Use it to explain to a human WHY something is locked, or to show what is worth doing on the floor. An item with no `requires` is granted to every signed-in member. Conditions read as { signal, gte } (a measurable: commits this week, events checked in, days of tenure), { minTier } (a membership ring) or { minLevel } (a Funko Me level; ic_funko_levels has the rules). Every `any` lists alternatives: the first one met grants it. For one member's actual progress against these, call ic_funko_progress. Args: { kind?: 'clip'|'prop'|'skin'|'stage'|'capability' }. Returns: { ok, count, items[{ id, kind, label, blurb?, rarity, requires?, asset? }] }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_funko_levelsThe Funko Me level rules: every XP source with its rate and cap, and the 10-level curve with each level's name.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 Funko Me level rules: every XP source with its rate and cap, and the 10-level curve with each level's name. No auth required; this is the rules table, nobody's progress (for one member's level call ic_funko_progress). Levels never go down. Only records the site reads itself earn XP: a Luma check-in (not an RSVP), a verified welcome quest (not a claimed one), a published log entry with a link (not a draft), commits from a linked GitHub (up to 50 a week), hosting a Luma event, using a floor resource (headset, print, transcription), making the figure, and weeks of membership. The membership ring earns no XP. Each source carries `how`, the action that earns it, so you can tell your human what to do next. Args: {}. Returns: { ok, version, xp_sources[{ signal, xp, per, how }], levels[{ level, at_xp, name }], rules[] }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_plans_guest_answerFor the GUEST of a plan or their assistant.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 the GUEST of a plan or their assistant. Judge each option against what your person wants and send only a verdict (ok | veto | unknown) and optional rank (1 = best) per option, and ok per time window. Never send reasons, diet, budget or anything else; there is no field for them. The other person sees only the final proposal. Args: { plan_id, token, answer: { options: [{ id, verdict, rank? }], windows?: [{ id, ok }] } }. No auth required.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ic_plans_guest_respondFor the GUEST of a plan or their assistant: accept or pass on the current proposal, or leave the plan (leave:true, which ends 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
    For the GUEST of a plan or their assistant: accept or pass on the current proposal, or leave the plan (leave:true, which ends it). ASK YOUR PERSON FIRST, it commits them. Both sides accepting confirms the plan; passing moves to the next proposal and says nothing about why. Args: { plan_id, token, accept?: boolean, leave?: boolean }. No auth required.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ic_scheduling_manage_bookingThe way OUT of a booking, and it is first-class on purpose: an agent that has to ask its human to click a link in an email simply ghosts, and no-shows are the failure mode that act…3 findings

    Why it is in this group

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

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...— the booking's own cancel_token IS the credential, exactly as a form's claim token is for..."

      What this check looks for
    • Info

      The input schema at properties.cancel_token.description mentions "credential".

      Matched text

      inputSchema.properties.cancel_token.description: "...e .ics your human saved. It is the only credential for this booking."

      What this check looks for
    • Info

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

      Matched text

      description ends: "...side_window | too_soon | rate_limited | validation | transient. No auth required."

      What this check looks for
    Description, as the server wrote it
    The way OUT of a booking, and it is first-class on purpose: an agent that has to ask its human to click a link in an email simply ghosts, and no-shows are the failure mode that actually burns members' time. NO TOKEN REQUIRED — the booking's own cancel_token IS the credential, exactly as a form's claim token is for an account-less submitter. Putting the exit behind an IC account nobody was issued is how a person ends up emailing a human to be removed. Authorization has not been skipped, it has MOVED into the resource: the token is checked in constant time and a WRONG token gives the SAME answer as a missing booking (not_found), so this cannot be used to discover which booking ids exist. action:read returns the booking's current state. action:cancel is idempotent — cancelling an already-cancelled booking is a SUCCESS, not an error, so a retry after a dropped response does not look like a failure. action:reschedule NEEDS start. A refused move leaves the original booking untouched: the release and the new booking are one transaction, so an error means nothing changed and you may try another slot. Confirm cancel and reschedule with your human first; both are visible to the member immediately. booking.id in a reschedule response is NEW and is the one to keep; cancel_token is unchanged. Reading the OLD id with the same token returns the LIVE booking (booking.id is the new id) plus superseded{id,start,end,rescheduled_by} naming the booking you asked for, so a saved manage link keeps working after the owner moves the meeting. action:read is also how you wait for a Google Meet link: calendar.meet_link.status pending -> ready (location_url is the link) or failed/none (no link is coming); poll no faster than every 2 seconds, for at most 90 seconds. Args: { booking_id, cancel_token, action, start?, reason?, idempotency_key? }. Returns: { ok, booking{id,status,start,end,cancel_token,cancelled_by,rescheduled_by,rescheduled_to}, superseded?{id,start,end,rescheduled_by}, member, meeting_type, location_url, ics, calendar{status,meet_link{status,reason,retrying}} } or { ok:false, error_kind } from not_found | slot_taken | outside_window | too_soon | rate_limited | validation | transient. No auth required.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ic_spatial_beta_applySubmit an application to the 20-person spatial-computing beta.No findings

    Why it is in this group

    • The name "ic_spatial_beta_apply" says "apply": a word for a change.
    Description, as the server wrote it
    Submit an application to the 20-person spatial-computing beta. WRITES a real application under a real person's name and commits them to a 5-week in-person NDA-bound program, so CONFIRM EVERY ANSWER WITH YOUR HUMAN FIRST and never invent one on their behalf - particularly the NDA, commitment and in-person answers, which are promises they have to keep. Call ic_spatial_beta_program first for the catalog and the exact allowed values. One application per email address; a second is refused rather than silently merged. The response carries a `claim_token` shown EXACTLY ONCE: surface it to your human verbatim, because without it an applicant with no IC account can never read their own status again. No auth required; a token only attributes the application. Returns: { ok, application_id, claim_token, status, failed_gates, cohort, message }.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ic_spatial_beta_programEverything needed to apply to the Immersive Commons spatial-computing beta: the terms (20 testers, 5 weeks, $160 paid ON COMPLETION, in person at Frontier Tower San Francisco, stri…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
    Everything needed to apply to the Immersive Commons spatial-computing beta: the terms (20 testers, 5 weeks, $160 paid ON COMPLETION, in person at Frontier Tower San Francisco, strict NDA, a pre-release AI spatial-computing device 6-12 months from release), every application question, and the REASON each is asked. Call this BEFORE ic_spatial_beta_apply so you answer well instead of guessing. `gates` names the three booleans that decide most applications - the NDA, the 5-week commitment, and being able to attend in person; a no to any of them is very likely a rejection, and saying so honestly beats applying anyway. Args: none. Returns: { ok, form, cohort: { size, approved, remaining } }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_spatial_beta_slotsHow many of the 20 spatial-computing beta tester slots are still open.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
    How many of the 20 spatial-computing beta tester slots are still open. Cheap: call this before starting a long application conversation with your human, and call ic_spatial_beta_program for the terms and questions. Args: none. Returns: { ok, cohort: { size, approved, remaining } }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_vault_matchEvaluate a company profile against the Vault's eligibility predicates and get a THREE-VALUED answer per entry: 'eligible' (every stated gate is definitively met), 'ineligible' (a s…1 finding

    Why it is in this group

    • The description's first verb is "evaluate": 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 "ic_vault_match" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Evaluate a company profile against the Vault's eligibility predicates and get a THREE-VALUED answer per entry: 'eligible' (every stated gate is definitively met), 'ineligible' (a stated gate is definitively failed), or 'indeterminate' — which means WE CANNOT TELL FROM WHAT THE VENDOR PUBLISHES, and is a real answer, never a soft no. No auth required. Nothing is ever reported 'eligible' while any gate is unknown or unstructured: a missing profile field lands in `unknown` (supply it and the verdict may flip), and a gate the program states only in prose lands in `manual_review` (a human has to read it). A non-hit against a NAMED partner list is `manual_review` too, never a failure, because every published partner list in the corpus is partial. Every profile field is OPTIONAL — a partial profile is the normal case and returns more `indeterminate`, not an error. Accepts the same category/kind/status/evidence/freshness filters as ic_vault_list. Returns: { ok, total_considered, counts, matches[], notes }. Each match carries failed[], unknown[], manual_review[], missing_prerequisites[] and per-tier verdicts.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_workshop_crosstalk_feedReturns the workshop room's live agent-to-agent traffic, the same feed the /workshop/crosstalk wall shows: the agents in the room (house and guest, with the skill each serves, call…1 finding

    Why it is in this group

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

    Findings

    • Warn

      The server marks "ic_workshop_crosstalk_feed" 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 "return": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Returns the workshop room's live agent-to-agent traffic, the same feed the /workshop/crosstalk wall shows: the agents in the room (house and guest, with the skill each serves, call count and last seen) and the events between them (register, call, complete, fail) in ascending seq order. Pass since = the cursor from your last call to get only newer events. No auth required. Args: { since?: integer >= 0 (default 0) }. Returns { ok, cursor, degraded, agents[] (max 200), events[] (seq > since, max 100) }.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 22Show 22 read-only tools
  • ic_donations_totalReturns the running total raised (USD), the donor count, and the most recent settled donations (name, amount, message, tx, ts) shown on the public donor wall at /donate.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "return" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "return" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    Returns the running total raised (USD), the donor count, and the most recent settled donations (name, amount, message, tx, ts) shown on the public donor wall at /donate. No auth required. Args: { limit?: number (1-50, default 10) }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_forms_getThe whole definition of one form: every question, its `kind` (short | long | bool | choice | email | url), whether it is required, the exact `options` a `choice` answer must match,…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The whole definition of one form: every question, its `kind` (short | long | bool | choice | email | url), whether it is required, the exact `options` a `choice` answer must match, and a `why` saying what the answer is actually used for. THIS IS THE READ-BEFORE-YOU-WRITE TOOL — call it before ic_forms_submit so you answer well instead of guessing, and relay each `why` to your human rather than deciding for them what a question is really asking. `facts` carries the program's own terms (things like how long it runs and what it pays) as ordered label/value pairs — read them to your human BEFORE they commit to anything. `gates` names the questions whose 'no' decides most submissions on its own; a truthful no there is recorded rather than blocking, and beats a flattering yes. TWO DIFFERENT RINGS, and confusing them is the main way an agent misleads its human here: `audience` is the minimum ring to SUBMIT (often `public`, meaning anyone at all), while `approval_requires_tier` is the minimum ring to be APPROVED. Anyone may raise a hand on an open call; being taken can still require membership. Report both, and never tell your human they qualify on the strength of `can_submit` alone. `accepting_submissions` is live runtime state, not a property of the definition — a form can be closed between your read and your submit. Args: { form_id }. Returns: { ok, form, can_submit, accepting_submissions, cannot_submit_reason?, required_tier? }. No auth required. An unknown form and a form you may not see return the SAME not_found, on purpose — telling a stranger 'that exists but is not for you' is itself the disclosure.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_forms_listEvery form Immersive Commons is currently taking answers to, filtered by who you are.No findings

    Why it is in this group

    • The name "ic_forms_list" says "list": a word for reading.
    Description, as the server wrote it
    Every form Immersive Commons is currently taking answers to, filtered by who you are. START HERE — do not guess a form id. Each entry carries its `form_id`, title, summary, the membership ring it is open to, whether YOU can answer it right now, and if you cannot, the reason and the ring you would need. A form you can SEE but not answer is LISTED rather than hidden, because a program nobody outside can discover is a program nobody outside ever joins; a form you may not see at all is omitted, because a list of titles you cannot open is a disclosure with no upside. What a listing never contains is anyone's answers. Args: none. Returns: { ok, count, forms[{ form_id, title, summary, audience, can_submit, cannot_submit_reason?, required_tier?, question_count }] }. No auth required; sending a token narrows nothing and only lets `can_submit` be truthful about your human's actual ring.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_forms_my_submissionThe status of one submission — YOUR human's, never anybody else's.1 finding

    Why it is in this group

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

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...URLs and chat logs, and if an id were a credential every stranger's answers would be reada..."

      What this check looks for
    Description, as the server wrote it
    The status of one submission — YOUR human's, never anybody else's. No token required. Two ways in: a signed-in identity resolves its own record with no id at all, or `submission_id` plus the `claim_token` handed back once at submit time opens the record that token belongs to. An id ALONE never works: ids travel through URLs and chat logs, and if an id were a credential every stranger's answers would be readable by anyone who ever saw a link. A wrong id, a wrong token and an id that was never issued all return the same `found: false`, so this cannot be used to test which ids exist. What comes back is status, dates and failed gates — never the answers as stored, never the reviewer's private note. Args: { form_id, submission_id?, claim_token? }. Returns: { ok, found, submission? }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_member_card_getThe public card for one Immersive Commons member by handle, schema ic-member-card/1: { ok, card{ schema, handle, name, headline?, bio?, profile_url, card_url, member_of, links[{kin…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "inbox": it reads mail.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    The public card for one Immersive Commons member by handle, schema ic-member-card/1: { ok, card{ schema, handle, name, headline?, bio?, profile_url, card_url, member_of, links[{kind, url, handle?, label?, verified_at?}], reach[{channel ('book'|'call'|'agent_inbox'|'paid_message'|'direct'), label, how, auth ('none'|'ic-member'|'agent-token'|'x402'), page?, endpoint?, tool?, url?, kind?, member_id?, intents?}], capabilities{ book{available, endpoint, page, auth}, message, call, files, pay }, signature } }. links are the member's PUBLIC links in their order (verified_at = the last time IC's server got a 2xx/3xx from it). reach lists only the ways to reach them that work right now, best first; follow `how`. Each capability says available true/false and, when false, `why` and an `alternative` to use instead. `pay` lists CAIP-10 accounts (Base and Solana) and assets ONLY when the member chose to make their pay address public; otherwise available:false. When offerings are on, `pay.offerings[]` lists what the member sells, each with an x402_url that pays them directly, and `message` points at their pay-to-reach offering if they listed one. Before paying anyone, show your human the handle, name and address and get their explicit go: this card is authenticated only by being served from immersivecommons.com (signature is null until signed cards ship). Members are private by default, and an unknown, retired or private handle returns the SAME not_found, so this is not a membership oracle. The same JSON is served at https://www.immersivecommons.com/m/<handle>/agent.json. No auth required. Args: { handle }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_member_profile_getOne Immersive Commons member's public profile by handle, as data: { ok, handle, name, profile_url, card_url, profile_v2{ hero{display_name, availability, chips}, stats[{value, labe…Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One Immersive Commons member's public profile by handle, as data: { ok, handle, name, profile_url, card_url, profile_v2{ hero{display_name, availability, chips}, stats[{value, label, source_note?, source_url?, kind ('self_reported' = the member's own claim | 'computed' = derived by IC from GitHub)}], now[{label, text}], offers[{title, body?, cta, meeting_type, booking_page}], log[{id, lane, kind, date, title, body?, url?, url_label?, pinned, updated}] (newest first, <= 50), log_total, log_url, activity (the 12-month chart: weeks, lanes{building, events, writing}, milestones) | null, follow{feed, feed_by_lane, agent} } }. The same profile_v2 block as https://www.immersivecommons.com/m/<handle>/agent.json. Drafts never appear. Members are private by default, and an unknown, private, operator-hidden or retired handle all return the SAME { ok:false, error, error_kind:'not_found' }, so this is not a membership oracle; a retired handle of a public member is followed to the current one. Read-only. No auth required. Args: { handle }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_news_getReturns newagg's velocity-ranked AI news — each item carries url + velocity + summary (plus dek, beat, date, publishedAt, image, focal).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns newagg's velocity-ranked AI news — each item carries url + velocity + summary (plus dek, beat, date, publishedAt, image, focal). This is the RAW aggregator feed (the same firehose that drives the floor10 news kiosk), a DIFFERENT surface from ic_signal_* (which serves THE SIGNAL, the weekly editorial dispatch). Items come back ranked highest-velocity-first (ties keep the feed's own order). No auth required. Args: { limit?: number (1-25, default 20), min_velocity?: number (>=1, default 1 — keep only items corroborated by >= this many sources), q?: string (2-80 chars, case-insensitive substring over title + summary) }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_offerings_getWhat one Immersive Commons member sells, by handle: { ok, handle, count, offerings[{ id, slug, title, description, price{mode, amount_usdc, unit?}, networks, fulfillment_kind, audi…Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    What one Immersive Commons member sells, by handle: { ok, handle, count, offerings[{ id, slug, title, description, price{mode, amount_usdc, unit?}, networks, fulfillment_kind, audience, input_schema?, x402_url }], how_to_pay }. Only offerings the member LISTED and that are on sale; an unknown handle, a member with none listed, and a private member all return the same not_found. To buy: GET or POST x402_url (?amount= for pay_what_you_want, ?quantity= per unit). It answers HTTP 402 with x402 PaymentRequirements whose payTo is the member's OWN address (Base, and Solana when they take it); pay with a PAYMENT-SIGNATURE (or X-PAYMENT) header and get the result plus a receipt. Show your human the member, the price and what is promised before paying. No auth required. Args: { handle }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_plans_guest_getFor the GUEST of a plan, or the guest's own AI assistant.1 finding

    Why it is in this group

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

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...the t= token from the plan link is the credential, and a wrong token answers not_found ex..."

      What this check looks for
    Description, as the server wrote it
    For the GUEST of a plan, or the guest's own AI assistant. NO IC ACCOUNT NEEDED: the t= token from the plan link is the credential, and a wrong token answers not_found exactly as a missing plan does. Returns the options, windows, your own answer, the current proposal and next_step; never the other side's answer. Args: { plan_id, token }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_presentations_askSearches every Immersive Commons talk by meaning and returns the matching slides, the same as the search box on /presentations: talk title, series, speaker, the slide number, a sni…No findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.
    Description, as the server wrote it
    Searches every Immersive Commons talk by meaning and returns the matching slides, the same as the search box on /presentations: talk title, series, speaker, the slide number, a snippet, a deep link straight to that slide in the public deck, and the talk's page. Retrieval only, no generated answer: read the snippets and follow deep_link. At most 3 hits per talk. No auth required. Budget: 40 questions per hour per token, and one shared hourly budget for all anonymous agents, so pass a token if you have one. Args: { q: string (1-500 chars), k?: integer 3-25 (default 10) }. Returns { ok, q, count, results: [{ slug, talk_title, series, speaker, similarity, slide, snippet, deep_link, detail_link }], via }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_presentations_getFetch a single presentation by its session number (optionally disambiguated by series).No findings

    Why it is in this group

    • The name "ic_presentations_get" says "get": a word for reading.
    Description, as the server wrote it
    Fetch a single presentation by its session number (optionally disambiguated by series). Session numbers are VCN-only; non-VCN talks (ClawCamp, standalone Talks) have no session_no — discover those via ic_presentations_list (filter series='ClawCamp'). No auth required. Returns the full ingest-friendly record. Args: { session_no: number, series?: string }. Returns: { scaffold, presentation: { session_no, series, title, date, format, public_url, deployed, speaker?, event?, summary?, content? } } where `content` is the talk's full curated llms.txt distillation (present for decks that ship one — read it instead of fetching the deck). On a miss, an error listing the available { series #session_no } entries. If session_no alone is ambiguous across series, the newest match wins — pass `series` to target one exactly.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_presentations_listList the public archive of presentations given at Immersive Commons events, Vibe Coding Nights (VCN), ClawCamp, and other community talks — newest first, grouped by series.No findings

    Why it is in this group

    • The name "ic_presentations_list" says "list": a word for reading.
    Description, as the server wrote it
    List the public archive of presentations given at Immersive Commons events, Vibe Coding Nights (VCN), ClawCamp, and other community talks — newest first, grouped by series. No auth required. NOT to be confused with ic_resources_list (that lists bookable rooms). Use ic_presentations_get for one VCN session's detail. Args: { series?: string (e.g. 'VCN'|'ClawCamp'|'Talk'), format?: 'deck'|'slides'|'video'|'doc'|'link', limit?: number (max 200, default 100) }. Returns: { count, total, series: string[], scaffold, by_series: Array<{ series, presentations: P[] }>, presentations: P[] (flat) } where P = { session_no (number, VCN-only; null for non-VCN talks), series, title, date, format, public_url, deployed, speaker?, event?, summary? }. `scaffold:true` means placeholder data (real manifest not yet synced). `public_url` is a direct view/download link, null if unpublished (local-only).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_scheduling_list_meeting_typesWhat you may book with one IC member: every PUBLIC meeting type they publish, with its duration, location kind, notice window and booking horizon.Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "ic_scheduling_list_meeting_types" says "list" and "meeting": it reads calendars.
    • private-dataThe description's first sentence says "meeting": it reads calendars.
    Description, as the server wrote it
    What you may book with one IC member: every PUBLIC meeting type they publish, with its duration, location kind, notice window and booking horizon. START HERE — a slug guessed rather than read is the commonest way an availability call returns not_found. NO TOKEN REQUIRED, and that is the point: a visitor's agent must be able to discover a member's booking link without an IC account, exactly as a human opening the link can. Visibility is filtered in the scheduling service's own SQL — members_only, unlisted and deactivated types never reach this response and are not filtered here, so an empty meeting_types means this member publishes nothing public, NOT that a filter hid something. min_notice_minutes and horizon_days are the two policy fields that decide whether a slot you want can exist at all; read them before proposing times to your human. The same reads are served by the scheduling service itself at https://sched.skew.site; its protocol document is https://sched.skew.site/v1/.well-known/scheduling. Args: { handle }. Returns: { ok, member:{handle,display_name,tz}, meeting_types[{slug,title,description,duration_minutes,location_kind,min_notice_minutes,horizon_days,requires_approval}] }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_signal_get_issueFetch one issue by slug.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "ic_signal_get_issue" says "get" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Fetch one issue by slug. Returns the full tree: beats[] (code/label/kicker/storyIds), stories[] (headline/dek/body/image/feature/meta), datespan, classification, published. No auth required. Args: { slug: string (e.g. "issue-05") }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_signal_get_latestConvenience tool — returns the most-recent issue summary (same shape as one element of ic_signal_list_issues.issues[]).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Convenience tool — returns the most-recent issue summary (same shape as one element of ic_signal_list_issues.issues[]). No auth required. Args: { include_stories?: boolean (default false — when true the issue's story list is inlined as stories[] with id/title/dek, saving a follow-up ic_signal_get_issue round trip) }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_signal_get_storyFetch one story by (issue slug, story id).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Fetch one story by (issue slug, story id). The story id is the kebab-case slug stored on each story (e.g. "grok-build", "shai-hulud-2"). Returns the story tree including body paragraphs, feature card, image, and source citations. No auth required. Args: { slug: string, story_id: string }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_signal_list_issuesList issue summaries for THE SIGNAL, Immersive Commons' weekly AI intelligence dispatch.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "ic_signal_list_issues" says "list" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    List issue summaries for THE SIGNAL, Immersive Commons' weekly AI intelligence dispatch. Newest first. No auth required. Args: { limit?: number (max 50, default 10) }. Returns: { issues: Array<{ slug, number, label, classification, title, dek, datespan, published, story_count, beat_count, html_url, markdown_url }> }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_spatial_beta_statusWhere one application stands.1 finding

    Why it is in this group

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

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...URLs and chat logs and must not work as credentials. A wrong or missing token is answered e..."

      What this check looks for
    Description, as the server wrote it
    Where one application stands. Needs BOTH the application_id and the claim_token returned at submission: an id alone returns only public slot counts and never anyone's record, because ids travel through URLs and chat logs and must not work as credentials. A wrong or missing token is answered exactly like an unknown id, so this cannot be used to test whether an id exists. Args: { application_id, claim_token }. Returns: { ok, found, application?, cohort }. No auth required.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_vault_listList and filter the Immersive Commons Vault: procedures PROVEN to work, written so you clear them without exploring — agent-readiness playbooks and startup credit programs, same sc…Reads private dataNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe name "ic_vault_list" says "list" and "vault": it reads secrets.
    • private-dataThe description's first sentence says "list" and "vault": it reads secrets.
    Description, as the server wrote it
    List and filter the Immersive Commons Vault: procedures PROVEN to work, written so you clear them without exploring — agent-readiness playbooks and startup credit programs, same schema. No auth required. Filters: kind ('playbook'|'credit'), category, status ('proven'|'unproven'|'dead' — does the thing actually exist), evidence ('official'|'mixed'|'approx' — how well-sourced the facts are), verified_within_days (freshness), q (substring over title/summary/eligibility), sort, limit, offset. Returns: { ok, total, returned, offset, entries[], facets, notes }. Each entry carries `first_try_success_label`, which reads "not yet measured" — NOT "0%" — until an entry has enough real reports; `first_try_success` is null in that state and a client must not render it as a number. `facets` gives the live value counts per filter so you can narrow without guessing at the vocabulary. An unknown filter value is IGNORED and explained in `notes` rather than erroring. Use ic_vault_match to ask whether a specific company qualifies; use ic_vault_feedback_submit to report whether a recipe worked.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_whats_newReturns the "What's New at IC" changelog, newest first, the same list the /whats-new page shows.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns the "What's New at IC" changelog, newest first, the same list the /whats-new page shows. Without a token you get the public entries. With a token tied to a person you get every entry at or below their membership ring, and the ones unlocked at their ring carry relevant:true ("new for you"). No auth required. Args: { limit?: integer 1-100 }. Returns { ok, tier, signed_in, total, entries: [{ ..., min_tier, relevant }] }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • ic_workshop_statusReturns the A2A workshop room's public scoreboard, the same data the /workshop/live screen shows: how many people enrolled, how many of the room's skills are covered, the recipe, e…Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns the A2A workshop room's public scoreboard, the same data the /workshop/live screen shows: how many people enrolled, how many of the room's skills are covered, the recipe, every skill's public manifest, the winner (display name and time only) and the join URL. No auth required. Args: none. Returns { ok, workshop, enrolled, skills_count, skills_covered, recipe, skills[], winner|null, join_url }.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

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.

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

Can send data out1
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__floor10__ic_scheduling_get_availability"
    ]
  }
}

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:40 UTC, unchanged since Oct 29, 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
14
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.immersivecommons.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://www.immersivecommons.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

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

    Matched text

    https://www.immersivecommons.com/api/mcp: tools/list returned 36 tools to an anonymous client, including ic_forms_withdraw (destructive), ic_scheduling_get_availability (irreversible), ic_donate (write), ic_funko_catalog (write), ic_funko_levels (write) and 9 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 13 to 14

Findings

Matches of fixed checks, with the text they matched.

3 warn6 info
  • The server marks "ic_scheduling_get_availability" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ic_scheduling_get_availability" says "get": a word for reading.

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

    Matched text

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

    What this check looks for
  • The server marks "ic_workshop_crosstalk_feed" 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 "return": a word for reading.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...URLs and chat logs and must not work as credentials. A wrong or missing token is answered e..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...URLs and chat logs, and if an id were a credential every stranger's answers would be reada..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...— the booking's own cancel_token IS the credential, exactly as a form's claim token is for..."

    What this check looks for
Show 3 more findings

History

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

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 13 -> 14.View diff
    • Tools that change things, listed without credentials: 13 to 14
  3. Tools11 added, 11 changed.+11 added~11 changedView diff

Install

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

claude mcp add --transport http floor10 https://www.immersivecommons.com/api/mcp
claude mcp add --transport http floor10 https://www.immersivecommons.com/api/mcp

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__floor10__ic_signal_list_issues",
      "mcp__floor10__ic_signal_get_latest",
      "mcp__floor10__ic_donations_total",
      "mcp__floor10__ic_signal_get_issue",
      "mcp__floor10__ic_signal_get_story",
      "mcp__floor10__ic_signal_search",
      "mcp__floor10__ic_news_get",
      "mcp__floor10__ic_presentations_list",
      "mcp__floor10__ic_presentations_get",
      "mcp__floor10__ic_spatial_beta_status",
      "mcp__floor10__ic_forms_list",
      "mcp__floor10__ic_forms_get",
      "mcp__floor10__ic_forms_my_submission",
      "mcp__floor10__ic_scheduling_list_meeting_types",
      "mcp__floor10__ic_member_card_get",
      "mcp__floor10__ic_offerings_get",
      "mcp__floor10__ic_member_profile_get",
      "mcp__floor10__ic_plans_guest_get",
      "mcp__floor10__ic_vault_list",
      "mcp__floor10__ic_workshop_status",
      "mcp__floor10__ic_presentations_ask",
      "mcp__floor10__ic_whats_new"
    ],
    "ask": [
      "mcp__floor10__ic_donate",
      "mcp__floor10__ic_funko_catalog",
      "mcp__floor10__ic_funko_levels",
      "mcp__floor10__ic_spatial_beta_program",
      "mcp__floor10__ic_spatial_beta_slots",
      "mcp__floor10__ic_spatial_beta_apply",
      "mcp__floor10__ic_forms_submit",
      "mcp__floor10__ic_scheduling_get_availability",
      "mcp__floor10__ic_scheduling_manage_booking",
      "mcp__floor10__ic_plans_guest_answer",
      "mcp__floor10__ic_plans_guest_respond",
      "mcp__floor10__ic_vault_match",
      "mcp__floor10__ic_workshop_crosstalk_feed"
    ],
    "deny": [
      "mcp__floor10__ic_forms_withdraw"
    ]
  }
}

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 floor10. Review it before you use it.

Capability tags behind 15 rules
  • mcp__floor10__ic_signal_list_issues untrusted-input
  • mcp__floor10__ic_signal_get_latest untrusted-input
  • mcp__floor10__ic_donations_total private-data, untrusted-input
  • mcp__floor10__ic_signal_get_issue untrusted-input
  • mcp__floor10__ic_signal_get_story untrusted-input
  • mcp__floor10__ic_signal_search untrusted-input
  • mcp__floor10__ic_news_get untrusted-input
  • mcp__floor10__ic_forms_get private-data, untrusted-input
  • mcp__floor10__ic_scheduling_list_meeting_types private-data
  • mcp__floor10__ic_scheduling_get_availability private-data, outbound
  • mcp__floor10__ic_member_card_get private-data, untrusted-input
  • mcp__floor10__ic_offerings_get untrusted-input
  • mcp__floor10__ic_member_profile_get private-data, untrusted-input
  • mcp__floor10__ic_vault_list private-data
  • mcp__floor10__ic_workshop_status 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.immersivecommons/floor10/verify?hash=f97c9063e81482ebe98276d21ca0da3db2cb5dbbc4f210847fa25f3f666cdbc6" | jq -e '.changed == false'

Pinned hash f97c9063e814, from Nov 10, 2026, 18:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.immersivecommons/floor10/changes.xml

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

Badge

Anlyon Radar badge for com.immersivecommons/floor10
[![Anlyon Radar](https://radar.anlyon.com/badge/com.immersivecommons/floor10.svg)](https://radar.anlyon.com/servers/com.immersivecommons/floor10)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:56 UTC.

Immersive Commons MCP server: questions and answers

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

Is the Immersive Commons MCP server safe?

No scan can promise that. What its definitions show: 36 tools, 14 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 Immersive Commons MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: ic_forms_withdraw.

Can the Immersive Commons MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: ic_scheduling_get_availability.

What tools does the Immersive Commons MCP server have?

36 tools: 1 destructive, 1 irreversible, 12 write, 22 read. ic_forms_withdraw, ic_scheduling_get_availability, ic_donate, ic_funko_catalog, ic_funko_levels, ic_spatial_beta_program, ic_spatial_beta_slots, ic_spatial_beta_apply and 28 more.

Does the Immersive Commons MCP server need sign-in or OAuth?

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

Does the Immersive Commons MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): ic_scheduling_get_availability.

Has the Immersive Commons MCP server changed its tools?

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