Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Credit GPS — Canadian credit is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Canadian credit: statement-cycle and utilization math, plus bureau and reporting reference data.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http credit-gps-canadian-credit-mcp https://mcp.creditgps.ca/mcp
# 2 — ask your agent for something these tools do
# get_next_move, get_reported_snapshot, get_statement_calendar and 13 more
Credit GPS — Canadian credit costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
CRAll 1 server
creditgps1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http credit-gps-canadian-credit-mcp https://mcp.creditgps.ca/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 su
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| today | string | no | 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. |
| targetUtilization | number | no | Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band. |
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 fi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| today | string | no | 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. |
| targetUtilization | number | no | Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| today | string | no | 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. |
| count | integer | no | How many events to return. Default 8. |
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 acco
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| cardName | string | yes | Which card the payment goes on. Partial names are matched. |
| amount | number | yes | Payment amount in CAD, posting before that card's statement closes. |
| today | string | no | 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. |
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, fe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| amount | number | yes | Purchase amount in CAD. |
| targetUtilization | number | no | Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band. |
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; no
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| goal | string | yes | Which goal to plan for. |
| today | string | no | 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. |
| targetUtilization | number | no | Target utilization as a decimal. Defaults to 0.29 — one point under the 30% band. |
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | yes | The person's revolving credit accounts. Ask for limit, statement balance, and statement closing date per card — those three drive everything. |
| cardName | string | yes | Which card to pay off. Partial names are matched. |
| monthlyPayment | number | no | Fixed amount paid each month in CAD. Omit to use the card's minimum payment, if one was supplied. |
| today | string | no | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cards | array | no | The person's cards, if they have given them. Omit to get the mechanics and the Canadian rules without any numbers. |
| cardName | string | no | The card being considered for closure. Partial names are matched. Only meaningful alongside cards. |
| today | string | no | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | A single topic id. Omit to get all of them. |
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| homeCountry | string | no | Country the person is arriving from, in English. Determines whether the credit-import route is open. |
| monthsInCanada | integer | no | Roughly how long they have been in Canada, to focus the answer on the relevant phase. |
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 l
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tier | string | no | Filter to one credibility tier. Omit for all. |
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 filter
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dueDate | string | no | A known payment due date, yyyy-mm-dd. Supplying it produces a derived estimate of the closing date. |
| issuer | string | no | The issuer, if known, e.g. "TD". Only used to tailor the wording — there is no per-issuer date table, because none is published. |
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 refer
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| daysPastDue | integer | no | How many days past the due date the payment is, if known. Changes which part of the answer leads. |
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 calcul
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Credit GPS — Canadian credit or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 0.2.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest7525aa27b2f80da524ff25177cd0bc65bb91404da3aaa5057219eaab820cd648
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_next_move | untrusted-input | untrusted-input: keyword "fetch" |
| get_reported_snapshot | untrusted-input | untrusted-input: keyword "fetch" |
| get_statement_calendar | untrusted-input | untrusted-input: keyword "fetch" |
| simulate_paydown | untrusted-input | untrusted-input: keyword "fetch" |
| compare_cards_for_purchase | untrusted-input | untrusted-input: keyword "fetch" |
| get_credit_plan | untrusted-input | untrusted-input: keyword "fetch" |
| calculate_payoff_timeline | untrusted-input | untrusted-input: keyword "fetch" |
| estimate_close_card_impact | untrusted-input | untrusted-input: keyword "fetch" |
| explain_canadian_credit_mechanics | no tags | |
| get_newcomer_credit_path | no tags | |
| list_credit_building_products | no tags | |
| describe_credit_gps | no tags | |
| find_statement_close_date | no tags | |
| explain_when_issuers_report | no tags | |
| explain_missed_payment | no tags | |
| explain_retention_periods | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest7525aa27b2f80da5
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Credit GPS — Canadian credit can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.