{"id":"marnunez-splitwise-mcp-server","name":"splitwise-mcp-server","af_score":57.8,"security_score":57.2,"reliability_score":22.5,"what_it_does":"Provides a Rust-based MCP (Model Context Protocol) server and an optional HTTP JSON-RPC endpoint that exposes Splitwise account functionality (users, groups, expenses, friends, and utilities like currencies/categories) to AI agents. Supports local stdio MCP usage and a remote HTTP deployment protected by a bearer token.","best_when":"You want an agent to manage Splitwise data through structured tool calls (MCP stdio or remote HTTP) and you can securely host the service with appropriate tokens.","avoid_when":"You need fine-grained authorization per operation/user, or you cannot enforce HTTPS and token hygiene for remote access.","last_evaluated":"2026-04-04T21:23:04.044128+00:00","has_mcp":true,"has_api":true,"auth_methods":["Bearer token (MCP_AUTH_TOKEN) for HTTP server","Direct API key usage server-side for Splitwise (SPLITWISE_API_KEY)"],"has_free_tier":false,"known_gotchas":["Remote HTTP endpoint requires Authorization bearer token; agents may omit headers unless configured.","Create/update/delete operations may not be idempotent; repeated calls on retries could create duplicate expenses unless the implementation includes safeguards (not documented).","Rate limiting is mentioned only at a high level; agents may need guidance to throttle or cache."],"error_quality":0.0}