Home / MCP registry index / io.github.switchwize/switchwize-mcp

SwitchWize MCP

io.github.switchwize/switchwize-mcp in the official MCP registry. Endpoint https://www.switchwize.com/api/mcp. Source: github.com/switchwize/switchwize-mcp.

The registry describes it as: Sixteen read-only US rate, savings-gap, Fed, card and CD tools with sources and freshness.

We read its 16 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_top_rates get_top_hysa_rates get_bank_gap compare_switch_savings get_rate_freshness get_index_dataset get_bank_gap_index get_reality_score get_card_offers get_transfer_bonuses get_card_changes get_reward_valuations best_move_this_week get_cd_rollover_rules get_card_downgrade_path get_fed_hike_pass_through

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-switchwize-switchwize-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-switchwize-switchwize-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.