Immersive Commons

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Immersive Commons": {
      "url": "https://www.immersivecommons.com/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (31)

• ic_signal_list_issues read-only

  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 }> }.

  Parameters:

  • limit — integer — How many issues to return, newest first (1-50).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_signal_get_latest read-only

  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) }.

  Parameters:

  • include_stories — boolean — true inlines the issue's stories (id, title, dek). Default false.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_donate

  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) }.

  Parameters:

  • tier — string — A tier label, case-insensitive. Narrows tiers[] to that tier and adds selected_tier with the exact USDC amount to sign.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_donations_total read-only

  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) }.

  Parameters:

  • limit — integer — How many recent donations to return (1-50, default 10).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_signal_get_issue read-only

  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") }.

  Parameters:

  • slug (required) — string — Issue slug, from ic_signal_list_issues.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_signal_get_story read-only

  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 }.

  Parameters:

  • slug (required) — string — Issue slug, from ic_signal_list_issues.
  • story_id (required) — string — Story id within that issue, from ic_signal_get_issue.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_signal_search read-only

  Substring search across every published SIGNAL issue. Matches on issue title + dek, beat label + kicker, story headline + dek + body. Case-insensitive. Returns ranked hits with a snippet + the slug + (when matched in a story) story_id. No auth required. Args: { q: string (2-120 chars), limit?: number (max 50, default 10) }.

  Parameters:

  • q (required) — string — Text to search issues and stories for (2-120 chars).
  • limit — integer — Most results to return (1-50).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_news_get read-only

  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) }.

  Parameters:

  • q — string — Case-insensitive text to find in title and summary (2-80 chars).
  • limit — integer — How many items to return (1-25, default 20).
  • min_velocity — integer — Keep only items corroborated by at least this many sources (default 1).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_presentations_list read-only

  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).

  Parameters:

  • limit — integer — Default 100; max 200. Applied to the flat newest-first list before grouping.
  • format — string — Optional filter to one artifact kind.
  • series — string — Optional filter to one series/program (case-insensitive), e.g. 'VCN', 'ClawCamp', 'Talk'. See the `series` array in a prior response for the live set.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_presentations_get read-only

  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.

  Parameters:

  • session_no (required) — integer — The session number within its series (from ic_presentations_list).
  • series — string — Optional series to disambiguate when the same session_no exists in multiple programs (e.g. a VCN #1 and a ClawCamp #1).

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_funko_catalog read-only

  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.

  Parameters:

  • kind — string — Optional filter — return only unlocks of this kind.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_funko_levels read-only

  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.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_spatial_beta_program read-only

  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.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_spatial_beta_apply

  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 }.

  Parameters:

  • full_name (required) — string — Applicant's full name. Required.
  • email (required) — string — Email they actually read. Required.
  • nda_ack (required) — boolean — Will they sign the strict NDA before their first session? Required. A false is honest and is recorded as a failed gate rather than blocked.
  • commit_5_weeks (required) — boolean — Can they commit to the full 5 weeks? Required.
  • in_person_sf (required) — boolean — Can they get to Frontier Tower, San Francisco in person regularly? Required. The hardware never leaves the building.
  • profile (required) — string — Exactly one of: AI founder | Prompt engineer | Computational designer | Vibe coder | Spatial UI/UX tinkerer | XR developer | Researcher | Other. Required.
  • building_now (required) — string — What they are building right now, in their own words. Required.
  • xr_experience (required) — string — Exactly one of: None - total newcomer | Tried a few times | Regular user | I build for headsets. Required. Newcomers are WANTED - do not inflate this to make an application look stronger.
  • availability (required) — string — Exactly one of: Weekday daytime | Weekday evenings | Weekends | Flexible / most times. Required.
  • handle — string — Telegram or X handle. Optional.
  • heard_via — string — How they heard about it. Optional.
  • project_link — string — https URL to a project, GitHub or portfolio. Optional.
  • accessibility — string — Access needs or anything affecting headset use. Optional, accommodated, never used to screen anyone out.
  • anything_else — string — Anything else. Optional.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_spatial_beta_status read-only

  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.

  Parameters:

  • application_id (required) — string — The sb_ id returned at submission.
  • claim_token (required) — string — The sbc_ token returned once at submission.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_forms_list read-only

  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.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_forms_get read-only

  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.

  Parameters:

  • form_id (required) — string — From ic_forms_list. Do not invent one.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_forms_submit

  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.

  Parameters:

  • form_id (required) — string — From ic_forms_list.
  • answers (required) — object — Keyed by question id, exactly as ic_forms_get returned them. Booleans may be sent as true/false or as the strings 'true'/'false'/'yes'/'no'. Omit an optional question rather than sending an empty string.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_forms_my_submission read-only

  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.

  Parameters:

  • form_id (required) — string — Which form.
  • claim_token — string — The one-time token returned at submit. Must be sent WITH submission_id; either alone does nothing.
  • submission_id — string — Needed only when reading by claim token rather than by identity.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_forms_withdraw destructive

  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.

  Parameters:

  • form_id (required) — string — Which form.
  • claim_token — string — The one-time token returned at submit. Must be sent WITH submission_id; either alone withdraws nothing.
  • submission_id — string — Needed only when the submitter has no IC account. A signed-in submitter needs neither this nor the token.

  Hints: read-only no · destructive yes · idempotent no · open-world no

• ic_scheduling_list_meeting_types read-only

  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.

  Parameters:

  • handle (required) — string — The member's booking handle, lowercase — the segment in their booking link. Matches ^[a-z0-9][a-z0-9._-]{0,63}$.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_scheduling_get_availability read-only

  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.

  Parameters:

  • handle (required) — string — The member's booking handle.
  • meeting_type (required) — string — The meeting-type slug from ic_scheduling_list_meeting_types. Do not guess it.
  • to — string — ISO-8601 end of the window. Defaults to the member's horizon; a longer request is clamped and the horizon block says so.
  • tz — string — IANA zone the BOOKER is in, e.g. Europe/Berlin. Echoed as viewer_tz. An unknown zone is rejected, never silently accepted. A raw UTC offset is NOT a zone and cannot survive a DST boundary.
  • from — string — ISO-8601 start of the window to search, e.g. 2026-09-12T00:00:00Z. Defaults to now.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_scheduling_manage_booking

  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.

  Parameters:

  • booking_id (required) — string — The booking's id, from the confirm response's booking.id.
  • cancel_token (required) — string — From booking.cancel_token on the confirm response, or the manage link inside the .ics your human saved. It is the only credential for this booking.
  • action (required) — string — read is safe and repeatable. cancel and reschedule change a real person's calendar — confirm with your human first.
  • start — string — Required for action:reschedule. An ISO-8601 slot start from a FRESH ic_scheduling_get_availability call — the old response is stale the moment anyone else books.
  • reason — string — Optional, for action:cancel. The member sees it; it is the difference between a cancellation and a ghosting.
  • idempotency_key — string — 8-128 chars of [A-Za-z0-9._:-]. Required by the service on a reschedule; minted here if you omit it. Bring your own and reuse it on retry.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_member_card_get read-only

  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 }.

  Parameters:

  • handle (required) — string — The member's IC handle, as in https://www.immersivecommons.com/m/<handle>.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_offerings_get read-only

  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 }.

  Parameters:

  • handle (required) — string — The member's IC handle, as in https://www.immersivecommons.com/m/<handle>.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_member_profile_get read-only

  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 }.

  Parameters:

  • handle (required) — string — The member's IC handle, as in https://www.immersivecommons.com/m/<handle>.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_plans_guest_get

  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.

  Parameters:

  • plan_id (required) — string — The plan id (pl_...), from ic_plans_create or ic_plans_list.
  • token (required) — string — The guest link token: the t= value in the plan link the guest was sent.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_plans_guest_answer

  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.

  Parameters:

  • plan_id (required) — string — The plan id (pl_...), from ic_plans_create or ic_plans_list.
  • token (required) — string — The guest link token: the t= value in the plan link the guest was sent.
  • answer (required) — object — Verdicts and ranks only. There is no field for a reason: never put preferences anywhere.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_plans_guest_respond

  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.

  Parameters:

  • plan_id (required) — string — The plan id (pl_...), from ic_plans_create or ic_plans_list.
  • token (required) — string — The guest link token: the t= value in the plan link the guest was sent.
  • leave — boolean — true leaves the plan, which ends it for both.
  • accept — boolean — true accepts the current proposal, false passes.

  Hints: read-only no · destructive no · idempotent no · open-world no

• ic_vault_list read-only

  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.

  Parameters:

  • q — string — Case-insensitive substring over id, title, summary, category and eligibility prose.
  • kind — string — 'playbook' = a multi-step procedure with per-step verification and traps. 'credit' = a credit / discount / perk program with one or more offer tiers.
  • sort — string — 'recent' (default) = most recently verified first. 'status' = proven first.
  • limit — integer — Default 100, max 200.
  • offset — integer — Default 0.
  • status — string — Does the thing WORK / EXIST. 'proven' = someone ran it end to end. 'dead' = the named program does not exist and the entry is kept only so nobody chases it. This is a DIFFERENT axis from `evidence`.
  • category — string — Exact category string, case-insensitive. Read the live set from `facets.category` in any response rather than guessing — a miss returns an empty list plus the real values in `notes`.
  • evidence — string — How well-sourced the FACTS are. 'official' = from the vendor's own page; 'approx' = aggregator/blog-sourced, verify before quoting. Orthogonal to `status`: a well-sourced entry about a dead program is official + dead.
  • verified_within_days — integer — Freshness gate: keep only entries re-checked within N days. Note this is `last_verified` (when someone last looked), not `last_changed` (when the program last moved) — the two are deliberately not the same field.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

• ic_vault_match read-only

  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.

  Parameters:

  • kind — string — Same filter as ic_vault_list.
  • as_of — string — YYYY-MM-DD for deadline checks. Defaults to today.
  • holds — array — Vault entry ids you already hold — used for prerequisite checks (e.g. holding NVIDIA Inception unlocks downstream offers).
  • stage — string — Funding stage label. Distinct from the raised amount — some programs gate on one, some on the other.
  • status — string — Same filter as ic_vault_list.
  • qualify — string — Return only matches with this verdict. OMIT IT to see all three — asking only for 'eligible' hides the 'indeterminate' set, which is usually where the real options are.
  • category — string — Same filter as ic_vault_list.
  • evidence — string — Same filter as ic_vault_list.
  • headcount — integer — People on the team. Checked against any entry that gates on team size.
  • domain_tags — array — 'ai-native' is stricter than 'ai': the model is the product, not a feature. The corpus draws that line itself.
  • affiliations — array — Affiliations some programs REQUIRE (an academic grant, a 501(c)(3) discount).
  • jurisdiction — string — ISO-3166 alpha-2 of the operating entity, e.g. 'US'.
  • business_types — array — Types some programs EXCLUDE. Declaring one may disqualify you from those.
  • cash_balance_usd — number — Cash on hand, USD. Orthogonal to funding raised.
  • has_domain_email — boolean — Company-domain email. A gmail address fails these gates.
  • has_web_presence — boolean — Live website + active socials a reviewer will look at.
  • company_age_years — number — Years since incorporation.
  • funding_raised_usd — number — Total raised, USD. 0 means bootstrapped.
  • has_working_product — boolean — Shipped something real, as opposed to still evaluating.
  • prior_participation — array — Vault entry ids whose program you have already taken. Distinct from being a customer.
  • existing_customer_of — array — Vault entry ids you are already a paying customer of — for 'new customers only' gates.
  • partner_affiliations — array — Investors / accelerators you are affiliated with. An EXPLICIT empty array is a statement (no affiliations ⇒ you cannot be on anyone's approved list) and fails referral gates; OMITTING the field is 'unknown' and does not.
  • verified_within_days — integer — Same filter as ic_vault_list.
  • months_since_last_round — number — Months since the most recent round CLOSED. Some programs require 'funded within 12 months' — a Series A from 3 years ago fails that while passing a stage gate.
  • has_institutional_backing — boolean — Somebody institutional wrote a cheque. Says nothing about WHO — that is `partner_affiliations`.

  Hints: read-only yes · destructive not declared · idempotent not declared · open-world no

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.