RoomSplit
REMOTE · ROOM-SPLIT.MAGICTEAMS.AI
Split rent and utilities by room, settle up and generate roommate agreements. Free.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Finance and Payments
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 824 tokens (~206/item across 4 items; 4 tools + 0 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 Management48
- Stability check failed: schema churn in the 19 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 44 to 48.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 28 to 31.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 21 to 24.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 14 to 18.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 4 to 11.
- 10 Oct 26 −2
- Stability: 0.17 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “roommate_agreement” rewrote its description, which is the text the model reads security
- Tool “settle_up” rewrote its description, which is the text the model reads security
- Tool “split_rent” rewrote its description, which is the text the model reads security
- Tool “split_utilities” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “roommate_agreement” changed the type of “notice_period_months”: number → integer ▼ functional
- Schema quality: good → excellent functional
- “roommate_agreement” reworded the description of “deposit” cosmetic
- “roommate_agreement” reworded the description of “house_rules” cosmetic
- “roommate_agreement” reworded the description of “monthly_rent” cosmetic
- “roommate_agreement” reworded the description of “move_in_date” cosmetic
- “roommate_agreement” reworded the description of “notice_period_months” cosmetic
- “roommate_agreement” reworded the description of “property_address” cosmetic
- “roommate_agreement” reworded the description of “room_assignments” cosmetic
- “roommate_agreement” reworded the description of “tenants” cosmetic
- “roommate_agreement” reworded the description of “utilities_policy” cosmetic
- “settle_up” reworded the description of “costs” cosmetic
- “settle_up” reworded the description of “payments” cosmetic
- “split_rent” reworded the description of “method” cosmetic
- “split_rent” reworded the description of “rooms” cosmetic
- “split_rent” reworded the description of “total_rent” cosmetic
- “split_utilities” reworded the description of “bills” cosmetic
- “split_utilities” reworded the description of “people” cosmetic
- 9 Oct 26 +2
- First check of Tool coverage: 100 functional
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 23 Oct 2026 · Probed https://room-split.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 4 Oct 2026 | 2 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ec2ccf2d1543f0b60ea6f60f412f0de3 |
| SANs: magicteams.ai, room-split.magicteams.ai, *.room-split.magicteams.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of room-split.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://room-split.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://room-split.magicteams.ai/mcp | HTTPS enforced | 301 | https://room-split.magicteams.ai/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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
roommate_agreement Roommate agreement ~303
Draft a plain-language shared-living agreement (parties, term, equal rent shares, deposit, utilities, house rules, notice, signature lines) plus a pre-signing checklist. Use when housemates want house terms in writing. Not legal advice. Do NOT use to compute unequal rent (use split_rent) or bill shares (use split_utilities).
| Name | Type | Req | Description |
|---|---|---|---|
| deposit | number | yes | Total deposit amount, 0 or more (0 = no deposit) |
| house_rules | array | – | Custom house rules, one sentence each; default covers quiet hours, guests, cleaning rota and shared supplies |
| monthly_rent | number | yes | Total monthly rent for the home, positive; split equally between tenants in the text |
| move_in_date | string | yes | Move-in date YYYY-MM-DD, e.g. 2026-11-01 |
| notice_period_months | integer | – | Notice period in whole months, default 1 |
| property_address | string | yes | Street address of the shared home, e.g. '12 Elm Street, Flat 3' |
| room_assignments | array | – | Optional: who sleeps in which room, one room per tenant; names must match tenants |
| tenants | array | yes | Unique names of all tenants (at least 2), e.g. ["Asha","Dev"] |
| utilities_policy | string | – | One sentence on how utilities are shared; default: split equally between tenants unless agreed otherwise |
| Name | Type | Req | Description |
|---|---|---|---|
| agreement | string | yes | Full agreement text, numbered sections and signature lines |
| checklist | array | yes | Practical steps to complete before signing |
| disclaimer | string | yes | Not-legal-advice disclaimer for the template |
No examples provided.
settle_up Settle up ~147
Split shared costs equally between housemates, compare with what each already paid, and compute balances plus the fewest payments that settle everyone. Use after people fronted money for the group. Computes only; moves no money. Do NOT use for usage-weighted bills (use split_utilities).
| Name | Type | Req | Description |
|---|---|---|---|
| costs | array | yes | Shared costs, split equally between everyone in payments (names must be unique), e.g. [{"name":"Groceries","amount":140}] |
| payments | array | yes | Every housemate sharing the costs and what they already paid (include people who paid 0), e.g. [{"name":"Asha","paid":150},{"name":"Mira","paid":0}] |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | Summary of how many payments settle the group |
| people | array | yes | Per-housemate paid, owed and balance |
| total_costs | number | yes | Sum of all shared costs |
| transfers | array | yes | Fewest payments that settle all balances (empty when settled) |
No examples provided.
split_rent Split rent ~177
Split a fixed monthly rent across rooms, equally or weighted by room size, and divide a shared room's rent equally between its occupants. Use when deciding who pays how much rent. Do NOT use for utility bills (use split_utilities) or to settle who already paid what (use settle_up).
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | 'equal' (same rent per room) or 'by_size' (proportional to size). Default: by_size when every room has a size, else equal |
| rooms | array | yes | Every room that pays rent (room names must be unique), e.g. [{"name":"Master","size":20,"occupants":["Asha","Dev"]}] |
| total_rent | number | yes | Monthly rent for the whole home, positive number in any currency, e.g. 2400 |
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | yes | Split method actually applied |
| note | string | yes | Plain-language explanation of how the rent was split |
| rooms | array | yes | Per-room rent shares, in input order; they sum to total_rent |
| total_rent | number | yes | Total monthly rent that was split, rounded to cents |
No examples provided.
split_utilities Split utilities ~146
Split utility and household bills across housemates, each bill equally, by occupants, or by usage weight, and total what each person owes. Use for recurring shared bills such as electricity, gas or internet. Do NOT use for rent (use split_rent) or to settle who already paid (use settle_up).
| Name | Type | Req | Description |
|---|---|---|---|
| bills | array | yes | Bills to split (names must be unique), e.g. [{"name":"Electricity","amount":120,"split":"by_usage"}] |
| people | array | yes | Housemates sharing the bills (names must be unique), e.g. [{"name":"Asha","usage_weight":2},{"name":"Dev","usage_weight":1}] |
| Name | Type | Req | Description |
|---|---|---|---|
| bills | array | yes | Each bill with its per-person shares (shares sum to the bill amount) |
| grand_total | number | yes | Sum of all bill amounts |
| note | string | yes | Plain-language explanation of the totals |
| totals | array | yes | Total each person owes across all bills |
No examples provided.
How do I install the RoomSplit MCP server?
RoomSplit is a hosted endpoint at https://room-split.magicteams.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · room-split.magicteams.ai
claude mcp add --transport http everyai-com-room-split 'https://room-split.magicteams.ai/mcp'
What is the RoomSplit MCP server?
RoomSplit is an MCP server listed in the public MCP registry as io.github.everyai-com/room-split. Split rent and utilities by room, settle up and generate roommate agreements. Free. This page covers its hosted endpoint (https://room-split.magicteams.ai/mcp).
Is the RoomSplit MCP server safe to use?
RoomSplit scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RoomSplit MCP server expose?
RoomSplit exposes 4 tools: split_rent, split_utilities, settle_up, roommate_agreement. Their descriptions and schemas cost roughly 773 tokens of context every time the server is loaded.
Does the RoomSplit MCP server require authentication?
No. We connected to RoomSplit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RoomSplit MCP server still maintained?
RoomSplit is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.