splitwise-mcp-server (svarun115/splitwise-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 27 tools. No publisher has claimed this listing.

D
Caution
50/100

splitwise-mcp-server

Model Context Protocol server for Splitwise API

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

svarun115

Source: Glama · also listed on github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: SPLITWISE_CONSUMER_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 15 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 3 credentials: SPLITWISE_ACCESS_TOKEN, SPLITWISE_CONSUMER_KEY, SPLITWISE_CONSUMER_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes27 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

splitwise_get_current_user

Get information about the currently authenticated Splitwise user, including their ID, name, email, notification settings, and default currency.

splitwise_get_user

Get information about another Splitwise user by their user ID.

splitwise_update_user

Update information for a Splitwise user. Can update first name, last name, email, password, locale, and default currency.

splitwise_get_groups

List all groups for the current user. Groups represent collections of users who share expenses together (e.g., household, trip, etc.).

splitwise_get_group

Get detailed information about a specific group, including members, balances, and settings.

splitwise_create_group

Create a new group. Can add users by providing their email/name or user_id. User fields should be in the format users__0__email, users__0__first_name, etc.

splitwise_delete_group

Delete a group. This destroys all associated records including expenses.

splitwise_restore_group

Restore a deleted group.

splitwise_add_user_to_group

Add a user to an existing group. Provide either user_id or email/first_name/last_name.

splitwise_remove_user_from_group

Remove a user from a group. Note: This only succeeds if the user has a zero balance in the group.

splitwise_get_friends

List all friends of the current user, including balance information.

splitwise_get_friend

Get detailed information about a specific friend, including shared groups and balances.

splitwise_add_friend

Add a new friend. If the user exists, first_name and last_name are ignored. If creating a new user, first_name is required.

splitwise_add_friends

Add multiple friends at once. Provide users array with email/first_name/last_name for each.

splitwise_remove_friend

Remove a friend connection. This breaks off the friendship between the current user and the specified user.

splitwise_get_expenses

List expenses with optional filters. Can filter by group, friend, date range, or update time.

splitwise_get_expense

Get detailed information about a specific expense, including all users involved and their shares.

splitwise_create_expense

Create a new expense. Can split equally among group members or specify custom shares for each user. For custom shares, provide users array with paid_share and owed_share for each user.

splitwise_update_expense

Update an existing expense. Only include fields that are changing. If users array is provided, all shares will be overwritten.

splitwise_delete_expense

Delete an expense permanently.

splitwise_restore_expense

Restore a deleted expense.

splitwise_get_comments

Get all comments for a specific expense.

splitwise_add_comment

Add a comment to an expense.

splitwise_delete_comment

Delete a comment from an expense.

splitwise_get_notifications

Get recent notifications/activity for the user account. Returns expenses added/updated/deleted, comments, group changes, friend changes, etc.

splitwise_get_currencies

Get a list of all currencies supported by Splitwise. Returns ISO 4217 currency codes.

splitwise_get_categories

Get a list of all expense categories supported by Splitwise. Use subcategory IDs when creating expenses.

// known CVEs in dependencies1 critical15 high6 medium15 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@2.1.9GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

high@modelcontextprotocol/sdk@1.21.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.21.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.21.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.13.1GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretSPLITWISE_ACCESS_TOKEN
configSPLITWISE_API_BASE_URL
🔐 secretSPLITWISE_CONSUMER_KEY
🔐 secretSPLITWISE_CONSUMER_SECRET
configSPLITWISE_TOKENS_DIR
configWS_BACKEND_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

27/27 tools missing one or more hints — splitwise_get_current_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); splitwise_get_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); splitwise_update_user (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +24 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 0/27 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 call in production code run through a shell (src/get-token.ts:180)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not logged

1 secret value sent to log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 15 high severity in production deps — @modelcontextprotocol/sdk@1.21.0 (high), @modelcontextprotocol/sdk@1.21.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/svarun115/splitwise-mcp-server?variant=verified)](https://m8ven.ai/mcp/svarun115/splitwise-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 6adda8f2bff7bed50d2ee3b7625e70193ea09b69
code hash: 9666119a7ffbed6dfade2260d4143fa210dba8dab19816632f56af571696beee
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client