Immersive Commons
REMOTE · WWW.IMMERSIVECOMMONS.COM · SCANNED AUG 3
Members-run AI builder space on Floor 10, Frontier Tower SF. 138 tools: events, news, directory.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (ic_admin_reject_highlight). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 28837 tokens (~181/item across 159 items; 156 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.immersivecommons.com
claude mcp add --transport http com-immersivecommons-floor10 https://www.immersivecommons.com/api/mcp
[mcp_servers.com-immersivecommons-floor10] url = "https://www.immersivecommons.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-immersivecommons-floor10": {
"type": "remote",
"url": "https://www.immersivecommons.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-immersivecommons-floor10 --url https://www.immersivecommons.com/api/mcp --transport streamable-http
mcp_servers:
com-immersivecommons-floor10:
url: "https://www.immersivecommons.com/api/mcp" {
"mcpServers": {
"com-immersivecommons-floor10": {
"type": "http",
"url": "https://www.immersivecommons.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
- Tool coverage: 87% → 80% ▼ functional
- New tool “ic_hack_results” functional
- New tool “ic_hack_roster” functional
- New tool “ic_hack_sign_nda” functional
- New tool “ic_hack_submit” functional
- New tool “ic_hack_team_create” functional
- New tool “ic_hack_team_join” functional
- New tool “ic_hack_team_leave” functional
- New tool “ic_hack_team_list” functional
- New tool “ic_hack_admin_phase” functional
- New tool “ic_hack_admin_role” functional
- New tool “ic_hack_bounty_post” functional
- New tool “ic_hack_checkin” functional
- New tool “ic_hack_get” functional
- New tool “ic_hack_judge_list” functional
- New tool “ic_hack_judge_score” functional
- New tool “ic_hack_me” functional
- New tool “ic_hack_register” functional
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
- Tool “ic_capabilities” rewrote its description, which is the text the model reads security
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://www.immersivecommons.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.immersivecommons.com | CN=YR2,O=Let's Encrypt,C=US | 17 Jul 2026 | 15 Oct 2026 | RSA 2048 | SHA256-RSA | 51bcfabe885190c599674b4558583ad229d |
| SANs: www.immersivecommons.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC secure
Validation of www.immersivecommons.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| immersivecommons.com. | present | 15019 | 8 | Verified |
| www.immersivecommons.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.immersivecommons.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.immersivecommons.com/api/mcp | HTTPS enforced | 308 | https://www.immersivecommons.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
ic_startup_request_ownership Request to be bound as founder of a startup (member) ~333
File a PENDING request to be bound as the FOUNDER of a seeded startup slug. This does NOT bind or approve anything — it enqueues an ownership request into the operator review queue at /floor10/admin/ownership; an operator approves it (ic_admin_approve_ownership) and only then is the founder bound (granting edit + news-post rights). Mirrors POST /api/startups/[slug]/claim exactly. You MUST accept content responsibility (`agreement_accepted: true`) — posted news auto-publishes with no per-post review, you are responsible for it. Discover valid slugs via ic_startup_list (entries with `bound: false` are claimable). The slug must already exist (seeded from data/startups.ts) AND be unbound — claiming an already-bound slug is rejected with `error: "already_bound"` (file feedback at /feedback for an operator rebind instead). Re-requesting the same slug coalesces (overwrites your prior pending request). Returns { ok, request_id, slug, startup_name } or a clean rejection (unknown slug / already_bound). Required scope: startup:edit (ic-member+). A signature is NOT required (unlike the founder write tools).
| Name | Type | Req | Description |
|---|---|---|---|
| agreement_accepted | boolean | — | Content-responsibility acceptance. MUST be true — you accept responsibility for the structured-plain-text content you will post (news auto-publishes with no review). A request without it is rejected. |
| slug | string | yes | Immutable startup slug to claim (seeded from data/startups.ts). Must already exist. |
No output schema declared.
No examples provided.
ic_startup_update_profile Update your startup's public page (owner or operator) ~301
Read-modify-write your startup's public profile: name (<=100), tagline (<=160), website (URL — refreshes the favicon fallback), public_visible, and/or the full news list (<=8 STRUCTURED PLAIN TEXT items, newest-first; replaces the list). NO HTML anywhere — text is plain-text defanged, not HTML-sanitized. The slug is immutable + must already exist (seeded from data/startups.ts). Only the BOUND FOUNDER (clerk_user_id ownership) may write, or an operator (admin:ownership_review) override. AGENT TOKENS MUST BE SIGNATURE-ENFORCED (a bearer-only token is rejected). Omitted fields are left unchanged. Returns { ok, profile }. Required scope: startup:edit.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | — | Display name (<=100 chars, plain text). |
| news | array | — | Replacement news list, newest-first (<=8 items). Replaces the existing list. Omit to leave news unchanged. |
| public_visible | boolean | — | Whether the startup is listed on the public /startups surface. |
| slug | string | yes | Immutable startup slug (seeded from data/startups.ts). Must already exist. |
| tagline | string | — | One-line tagline (<=160 chars, plain text). Empty string clears it. |
| website | string | — | Homepage URL (normalized; refreshes the favicon fallback). Empty string clears it. |
No output schema declared.
No examples provided.
ic_transcribe_get Get a finished transcript (member) ~146
Fetch the result of a DONE transcription job: the markdown + JSON transcript file ids (download with ic_files_get) plus metadata (language, num_speakers, duration, segments). Small markdown transcripts (<=50KB) are inlined as text. If the job isn't done yet this returns not_ready with the current status — poll ic_transcribe_status instead. You must be the submitter (or an operator). Args: { job_id }. Returns: { ok, job_id, result, transcript_md? }. Required scope: transcribe:read (ic-member+).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job id (tj_...) from ic_transcribe_submit. |
No output schema declared.
No examples provided.
ic_transcribe_list List your transcription jobs (member) ~81
List YOUR recent transcription jobs, newest first (expired jobs are pruned). Args: { limit? (max 20, default 20) }. Returns: { ok, count, jobs }. Required scope: transcribe:read (ic-member+).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | How many jobs to return (max 20, default 20). |
No output schema declared.
No examples provided.
ic_transcribe_status Check a transcription job's status (member) ~119
Get one transcription job by id: its status (queued / processing / done / error), source, timing, attempts, and — when done — the result file ids + metadata (also fetchable with ic_transcribe_get). You must be the submitter (or an operator). Poll no more than once per minute. Args: { job_id }. Returns: { ok, job }. Required scope: transcribe:read (ic-member+).
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job id (tj_...) from ic_transcribe_submit. |
No output schema declared.
No examples provided.
ic_transcribe_submit Submit audio for transcription + diarization (member) ~283
Queue an audio file for offline transcription + speaker diarization by IC's GPU worker. Provide EXACTLY ONE source: a file_id you uploaded via ic_files_put (audio <=25MB) OR an https audio_url. Results (a markdown transcript + a JSON with per-speaker segments) land in the file vault next to the source; poll ic_transcribe_status no more than once per minute, then read the transcript with ic_transcribe_get. Args: { file_id?, audio_url?, language? (BCP-47 hint, e.g. 'en'), num_speakers_hint? (1..10) }. Returns: { ok, id, status: 'queued', queue_position }. Rate: 5 submissions per token per UTC day. Required scope: transcribe:submit (ic-member+).
| Name | Type | Req | Description |
|---|---|---|---|
| audio_url | string | — | An https URL to the audio. Mutually exclusive with file_id. No private/loopback hosts. |
| file_id | string | — | A vault file id (f_...) from ic_files_put. Mutually exclusive with audio_url. |
| language | string | — | Optional BCP-47 language hint (e.g. 'en', 'es'). Omit to auto-detect. |
| num_speakers_hint | integer | — | Optional hint for how many speakers to diarize (1..10). |
No output schema declared.
No examples provided.