# Credit GPS — Canadian credit (remote · mcp.creditgps.ca)

Canadian credit: statement-cycle and utilization math, plus bureau and reporting reference data.

- Trust score: 72/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.creditgps.ca`: 72/100 (this document), [markdown](https://verifymcp.io/servers/ca-creditgps-canadian-credit/mcp.md), [page](https://verifymcp.io/servers/ca-creditgps-canadian-credit/mcp)

## Channel facts

- Endpoint: `https://mcp.creditgps.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3188 tokens (~199/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability check failed: schema churn in the 27 days we've observed: 14 tool removals, 0 breaking changes, 0 auth/transport breaks, 14 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Credit GPS — Canadian credit MCP server?

Credit GPS — Canadian credit is a hosted endpoint at https://mcp.creditgps.ca/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.

### Claude

```bash
claude mcp add --transport http ca-creditgps-canadian-credit 'https://mcp.creditgps.ca/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ca-creditgps-canadian-credit": {
      "url": "https://mcp.creditgps.ca/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ca-creditgps-canadian-credit": {
      "type": "http",
      "url": "https://mcp.creditgps.ca/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ca-creditgps-canadian-credit]
url = "https://mcp.creditgps.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ca-creditgps-canadian-credit": {
      "type": "remote",
      "url": "https://mcp.creditgps.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ca-creditgps-canadian-credit --url 'https://mcp.creditgps.ca/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ca-creditgps-canadian-credit:
    url: "https://mcp.creditgps.ca/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ca-creditgps-canadian-credit": {
      "Transport": "http",
      "Url": "https://mcp.creditgps.ca/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ca-creditgps-canadian-credit -t streamable-http -u 'https://mcp.creditgps.ca/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ca-creditgps-canadian-credit": {
      "type": "http",
      "url": "https://mcp.creditgps.ca/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-08 (score 72, −7)

- [security regression] Stability: 0.47 → fail
- [security regression] Tool “about_credit_gps” was removed
- [security regression] Tool “canadian_credit_mechanics” was removed
- [security regression] Tool “close_card_impact” was removed
- [security regression] Tool “credit_plan” was removed
- [security regression] Tool “credit_product_landscape” was removed
- [security regression] Tool “how_long_it_stays” was removed
- [security regression] Tool “missed_payment_guide” was removed
- [security regression] Tool “newcomer_credit_path” was removed
- [security regression] Tool “next_move” was removed
- [security regression] Tool “payoff_timeline” was removed
- [security regression] Tool “purchase_impact” was removed
- [security regression] Tool “reported_snapshot” was removed
- [security regression] Tool “statement_calendar” was removed
- [security regression] Tool “when_issuers_report” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “find_statement_close_date” rewrote its description, which is the text the model reads
- [security] Tool “simulate_paydown” rewrote its description, which is the text the model reads
- [functional] Server version: 0.2.0 → 0.3.1
- [functional] New tool “calculate_payoff_timeline”
- [functional] New tool “compare_cards_for_purchase”
- [functional] New tool “describe_credit_gps”
- [functional] New tool “estimate_close_card_impact”
- [functional] New tool “explain_canadian_credit_mechanics”
- [functional] New tool “explain_missed_payment”
- [functional] New tool “explain_retention_periods”
- [functional] New tool “explain_when_issuers_report”
- [functional] New tool “get_credit_plan”
- [functional] New tool “get_newcomer_credit_path”
- [functional] New tool “get_next_move”
- [functional] New tool “get_reported_snapshot”
- [functional] New tool “get_statement_calendar”
- [functional] New tool “list_credit_building_products”
- [cosmetic] Tool “simulate_paydown” changed its title: Simulate a paydown → What a payment does to reported utilization

### 2026-09-07 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-03 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-01 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-26 (score 73, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (16)

### `get_next_move` (~203 tokens)

Next move

Use this when someone asks what to pay first, what to do next, or how to lower utilization before it is reported. Returns the single highest-priority action from the card figures given in the conversation: which card, how much, and by which date. The calculation uses the supplied statement closing date as a planning assumption; actual issuer reporting dates can differ. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `targetUtilization` (number): Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `assumptions` (array)
- `currentUtilization` (number)
- `disclosure` (string)
- `forecast` (null): No validated score prediction is available.
- `move` (object)

### `get_reported_snapshot` (~200 tokens)

Calculate utilization from supplied balances

Use this when someone asks how their cards look, where they stand, or which card is the problem. Returns utilization from supplied balances, days to the supplied closing date, and a hypothetical payment to reach the target. It does not determine future bureau-reported balances. This is the difference between today's balance and the figure the issuer transmits. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `targetUtilization` (number): Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `assumptions` (array)
- `band` (string)
- `blendedUtilization` (number)
- `cards` (array)
- `disclosure` (string)
- `isEmpty` (boolean)
- `totalLimit` (number)
- `totalReported` (number)

### `get_statement_calendar` (~173 tokens)

Statement calendar

Use this when someone asks about timing, what is coming up, or why the closing date differs from the due date. Returns the upcoming dates in order: when to pay, when each statement closes (the bureau read), and when each payment is due (the delinquency line). Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `count` (integer): How many events to return. Default 8.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `assumptions` (array)
- `disclosure` (string)
- `events` (array)

### `simulate_paydown` (~204 tokens)

What a payment does to reported utilization

Use this when someone asks what happens if they pay a particular amount, or wants to compare two amounts. Returns a what-if for a specific payment on a specific card before it closes: reported utilization before and after, per card and blended. No score change is predicted. It is a calculation only; no payment is made. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `amount` (number, required): Payment amount in CAD, posting before that card's statement closes.
- `cardName` (string, required): Which card the payment goes on. Partial names are matched.
- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `amount` (number)
- `assumptions` (array)
- `blendedAfter` (number)
- `blendedBefore` (number)
- `cardBandAfter` (string)
- `cardBandBefore` (string)
- `cardName` (string)
- `cardUtilizationAfter` (number)
- `cardUtilizationBefore` (number)
- `disclosure` (string)
- `forecast` (null): No validated score prediction is available.
- `payBeforeDate` (string)

### `compare_cards_for_purchase` (~169 tokens)

Which card for this purchase

Use this when someone asks which card to put a purchase on. Returns two answers for the amount given: the card that reports the least utilization impact, the card that is cheapest to carry, and the trade-off when those differ, because the card the bureaus notice least is often not the card with the lowest rate. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `amount` (number, required): Purchase amount in CAD.
- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `targetUtilization` (number): Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band.

Output parameters:

- `amount` (number)
- `bestForReporting`
- `blendedBefore` (number)
- `cheapestToCarry`
- `disclosure` (string)
- `noCardFits` (boolean)
- `optionsDisagree` (boolean)

### `get_credit_plan` (~232 tokens)

Multi-step credit plan

Use this when someone wants more than the next single action. Returns an ordered plan for one of three goals: raise_score, pay_down_balances, or build_credit. Safety steps come first (anything overdue, then imminent minimums), then goal steps, each with the specific action, the mechanism behind it, and a date. The plan is returned as text and structured data for the person to act on themselves; nothing is scheduled or executed. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `goal` (string, required): Which goal to plan for.
- `targetUtilization` (number): Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `assumptions` (array)
- `disclosure` (string)
- `generatedForDate` (string)
- `goal` (string)
- `steps` (array)

### `calculate_payoff_timeline` (~256 tokens)

How long to pay this card off

Use this for "if I pay $200 a month, when is this paid off?" or "what happens if I only pay the minimum?". Returns how long a card takes to clear at a fixed monthly payment and the interest paid over that time. This is a cost question, not a reporting one: it does not change what the bureaus see, so use get_reported_snapshot or simulate_paydown for that. Requires the card's purchase APR; without it no timeline is returned, because the rate decides the answer. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `cardName` (string, required): Which card to pay off. Partial names are matched.
- `cards` (array, required): The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything.
- `monthlyPayment` (number): Fixed amount paid each month in CAD. Omit to use the card's minimum payment, if one was supplied.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `aprBps`
- `aprUnknown` (boolean)
- `assumptions` (array)
- `atMinimum`
- `balance` (number)
- `cardName` (string)
- `disclosure` (string)
- `monthlyPayment` (number)
- `months`
- `neverShrinks` (boolean)
- `totalInterest`

### `estimate_close_card_impact` (~237 tokens)

What closing a card does to utilization

Use this for "should I cancel the credit card I never use", "is it bad to close a card", or any question about cancelling, downgrading, or consolidating cards. It does not close, cancel, or change any card; it only explains and calculates. With no card figures it returns general closure considerations and retention information. Supply figures for a hypothetical paid-off closure calculation. Supply cards and cardName as well and it additionally computes the exact utilization before and after, the limit leaving the denominator, and whether it crosses a band upward. Calculates scenarios from supplied figures; does not make payments, change accounts, fetch external data, or retain tool inputs.

Input parameters:

- `cardName` (string): The card being considered for closure. Partial names are matched. Only meaningful alongside cards.
- `cards` (array): The person's cards, if they have given them. Omit to get the mechanics and the Canadian rules without any numbers.
- `today` (string): Today's date in the person's local timezone, yyyy-mm-dd. Pass it — the server otherwise falls back to UTC, which is a day ahead for Canadian evenings.

Output parameters:

- `alwaysTrue` (array)
- `assumptions` (array)
- `balanceOnCard`
- `bandAfter`
- `bandBefore`
- `blendedAfter`
- `blendedBefore`
- `cardName`
- `computed` (boolean)
- `crossesBandUp`
- `disclosure` (string)
- `isOnlyRevolvingAccount`
- `limitRemoved`
- `remainingLimit`

### `explain_canadian_credit_mechanics` (~142 tokens)

How Canadian credit reporting actually works

Use this for a requested explanation of Canadian credit scores, reports, utilization, or reporting timing. Returns the Canada-specific mechanics of credit reporting, each entry leading with the correction to the common United States-based answer: the 300-900 scale and two-bureau market, statement-close versus due-date reporting, provincial rather than federal regulation, soft pulls and free-report rights, how utilization is read, and why open banking does not open up bureau data. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Input parameters:

- `topic` (string): A single topic id. Omit to get all of them.

Output parameters:

- `asOf` (string)
- `disclosure` (string)
- `topics` (array)

### `get_newcomer_credit_path` (~187 tokens)

Building a Canadian credit file from zero

Use this for any question about building credit as an immigrant, newcomer, international student, or temporary resident in Canada. Returns the ordered path for someone new to Canada: what to do before a SIN arrives, whether their home-country history can be imported and at which banks, how to get a first tradeline, and what accumulates after that. Supply the home country for a specific answer on credit import; coverage is partial, and several of the largest source countries for Canadian newcomers are not covered at all. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Input parameters:

- `homeCountry` (string): Country the person is arriving from, in English. Determines whether the credit-import route is open.
- `monthsInCanada` (integer): Roughly how long they have been in Canada, to focus the answer on the relevant phase.

Output parameters:

- `asOf` (string)
- `bankPrograms` (array)
- `creditImport` (object)
- `disclosure` (string)
- `steps` (array)

### `list_credit_building_products` (~142 tokens)

Canadian credit-building products

Use this to retrieve dated reference examples of Canadian secured cards and credit-building products. Confirm current terms and reporting arrangements with the provider. Returns the products available in Canada, grouped by how established they are, with which bureau each reports to. Single-bureau reporting is the detail most often missed: several well-known products report to Equifax only, which leaves the TransUnion file empty. Also flags the warning signs on upfront-fee credit repair and advertised-certainty lending. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Input parameters:

- `tier` (string): Filter to one credibility tier. Omit for all.

Output parameters:

- `asOf` (string)
- `caveat` (string)
- `disclosure` (string)
- `products` (array)
- `sources` (array)

### `describe_credit_gps` (~95 tokens)

About Credit GPS

Use this when someone asks what Credit GPS is, who made this, whether their data is stored, or why an answer stopped short. Also explains how to obtain free Canadian bureau reports and manually enter their figures in the Credit GPS application for score tracking. This tool provides instructions; it cannot save entries or retrieve score history. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Output parameters:

- `disclosure` (string)
- `limits` (array)
- `manualReportGuide` (array)
- `privacy` (array)
- `product` (string)
- `sources` (array)
- `what` (string)

### `find_statement_close_date` (~206 tokens)

Find your statement closing date

Use this whenever someone does not know their statement closing date, or gives a payment due date and asks what to pay. Returns the ways to find the closing date of a Canadian credit card, the date every other tool here depends on and the one most people have never been shown. Give a payment due date and it also derives an estimate, because federally regulated issuers must allow at least a 21-day interest-free grace period measured from the close. It looks nothing up on any account; the estimate is arithmetic on the date supplied. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Input parameters:

- `dueDate` (string): A known payment due date, yyyy-mm-dd. Supplying it produces a derived estimate of the closing date.
- `issuer` (string): The issuer, if known, e.g. "TD". Only used to tailor the wording — there is no per-issuer date table, because none is published.

Output parameters:

- `asOf` (string)
- `derivedCloseDate`
- `derivedFromDueDate`
- `disclosure` (string)
- `graceDays` (number)
- `methods` (array)

### `explain_when_issuers_report` (~112 tokens)

When issuers actually send data to the bureaus

Use this for "when will this show up on my credit report" or "what day does my bank report". Returns how the monthly reporting cadence works in Canada, how long a change takes to appear on a file, and why an Equifax file and a TransUnion file for the same person differ. This bundled reference has no verified per-issuer transmission calendar and returns no exact reporting day. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Output parameters:

- `asOf` (string)
- `disclosure` (string)
- `general` (array)
- `notPublished` (array)
- `sources` (array)

### `explain_missed_payment` (~174 tokens)

Missing a payment, and what happens after

Use this for a missed, late, or nearly-late payment, or for "how long will this hurt me". Returns what happens when a Canadian credit card payment is missed: the roughly 30-day gap before it is reported at all, the Canadian R1-R9 rating scale a tradeline actually carries, and how long a reported late payment stays on the file. The Canadian answer differs from the American one on both the scale and the duration, and the 30-day gap is frequently actionable, because a payment caught inside it often never reaches the file. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Input parameters:

- `daysPastDue` (integer): How many days past the due date the payment is, if known. Changes which part of the answer leads.

Output parameters:

- `afterwards` (array)
- `asOf` (string)
- `daysPastDue`
- `disclosure` (string)
- `ratingScale` (array)
- `sources` (array)
- `threshold` (array)
- `withinReportingWindow`

### `explain_retention_periods` (~95 tokens)

How long things stay on a Canadian credit file

Use this for any "how long will this stay on my credit report" question. Returns retention periods on a Canadian credit file: closed accounts, late payments, collections, hard inquiries, bankruptcy, consumer proposals, judgments. Durations differ by information type, bureau, and province. Returns those distinctions and source links. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.

Output parameters:

- `asOf` (string)
- `caveat` (string)
- `disclosure` (string)
- `items` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ca-creditgps-canadian-credit/mcp#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 72
- 2026-09-07: 79
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 75
- 2026-08-30: 75
- 2026-08-29: 75
- 2026-08-28: 74
- 2026-08-27: 74
- 2026-08-26: 73
- 2026-08-25: 71
- 2026-08-24: 64

## Common questions

### What is the Credit GPS — Canadian credit MCP server?

Credit GPS — Canadian credit is an MCP server listed in the public MCP registry as ca.creditgps/canadian-credit. Canadian credit: statement-cycle and utilization math, plus bureau and reporting reference data. This page covers its hosted endpoint (https://mcp.creditgps.ca/mcp).

### Is the Credit GPS — Canadian credit MCP server safe to use?

Credit GPS — Canadian credit scores 72 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 Credit GPS — Canadian credit MCP server expose?

Credit GPS — Canadian credit exposes 16 tools: get_next_move, get_reported_snapshot, get_statement_calendar, simulate_paydown, compare_cards_for_purchase, and 11 more. Their descriptions and schemas cost roughly 2,827 tokens of context every time the server is loaded.

### Does the Credit GPS — Canadian credit MCP server require authentication?

No. We connected to Credit GPS — Canadian credit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Credit GPS — Canadian credit MCP server still maintained?

Credit GPS — Canadian credit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.creditgps.ca/mcp
- Repository: https://github.com/creditgps/CreditGPS
- Website: https://creditgps.ca/
- Changelog RSS feed: https://verifymcp.io/servers/ca-creditgps-canadian-credit/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ca-creditgps-canadian-credit/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ca-creditgps-canadian-credit/mcp