Is com.immersivecommons/floor10 up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | immersive-commons-floor10 1.41.0 |
| Answered in | 368 ms |
| Endpoint checked | https://www.immersivecommons.com/api/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Published, does not validate: supportedInterfaces[0].protocolBinding is required (and 4 more). A2A 1.0 shape; 16 skills./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (HTTP 401).https://www.immersivecommons.com/api/mcp/server-card |
| MCP server card (SEP-1649 location) | Published, does not validate: `$schema` is required (and 2 more). SEP-2127 shape; immersive-commons-floor10 1.41.0./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Published, does not validate: served as application/jwk-set+json, not application/http-message-signatures-directory+json (ยง5.5.1) (and 2 more). 1 key (Ed25519); the response is not signed./.well-known/http-message-signatures-directory |
Read at https://www.immersivecommons.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 24 tools: ic_donate, ic_donations_total, ic_forms_get, ic_forms_list, ic_forms_my_submission, ic_forms_submit, ic_forms_withdraw, ic_funko_catalog, ic_member_card_get, ic_news_get, ic_offerings_get, ic_presentations_get, ic_presentations_list, ic_scheduling_get_availability, ic_scheduling_list_meeting_types, ic_scheduling_manage_booking, ic_signal_get_issue, ic_signal_get_latest, ic_signal_get_story, ic_signal_list_issues, ic_signal_search, ic_spatial_beta_apply, ic_spatial_beta_program, ic_spatial_beta_status.
Its tools changed between 2026-09 and 2026-10:
- Added (2):
ic_member_card_get,ic_offerings_get ic_scheduling_manage_booking: description changedic_spatial_beta_apply: description changedic_spatial_beta_program: description changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.immersivecommons/floor10 |
|---|---|
| Title | Immersive Commons |
| Description | RSVP to San Francisco AI events, book a room, borrow a VR headset, submit a 3D print, find members. |
| Endpoint | https://www.immersivecommons.com/api/mcp |
| Publisher repository | https://github.com/immersive-commons/ic-skills |
| Version | 1.1.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt