Home / MCP registry index / ca.creditgps/canadian-credit
Credit GPS — Canadian credit
ca.creditgps/canadian-credit in the official MCP registry.
Endpoint https://mcp.creditgps.ca/mcp. Source: github.com/creditgps/CreditGPS.
The registry describes it as: Canadian credit: statement-cycle and utilization math, plus bureau and reporting reference data.
We read its 16 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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_next_move get_reported_snapshot get_statement_calendar simulate_paydown compare_cards_for_purchase get_credit_plan calculate_payoff_timeline estimate_close_card_impact explain_canadian_credit_mechanics get_newcomer_credit_path list_credit_building_products describe_credit_gps find_statement_close_date explain_when_issuers_report explain_missed_payment explain_retention_periods
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ca-creditgps-canadian-credit)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.