Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.askmiles/catalog

REMOTE · API.ASKMILES.AI

Miles' public credit-card catalog: facts, transfer partners, valuations. Keyless, read-only.

Available components

−1 this week 75 Trust /100

Last scanned (15 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 938 tokens (~187/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "find_transfer_routes" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “compare_card_facts” rewrote its description, which is the text the model reads security
    • Tool “estimate_point_value” rewrote its description, which is the text the model reads security
    • Tool “find_transfer_routes” rewrote its description, which is the text the model reads security
    • Tool “get_card_facts” rewrote its description, which is the text the model reads security
    • Tool “search_card_catalog” rewrote its description, which is the text the model reads security
    • “estimate_point_value” reworded the description of “points” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.askmiles.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=askmiles.ai CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 2f1ec5ef7b1b980213a162fd98c93a10
SANs: askmiles.ai, *.askmiles.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.askmiles.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
askmiles.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.askmiles.ai/mcp Verified 200
http (plaintext) http://api.askmiles.ai/mcp HTTPS enforced 301 https://api.askmiles.ai/mcp
MCP tools · 5 exposed · ~754 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_card_facts ~67

The same catalog record for 2-5 cards at once, for comparing fees, networks and which benefits each carries. Card facts only: no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes.

NameTypeReqDescription
card_namesarrayyesCard names, matched loosely.

No output schema declared.

No examples provided.

estimate_point_value ~155

Miles' own estimate of a loyalty point's value in cents, optionally multiplied by a balance. A cash balance such as Uber Cash is valued as a share of face value (0.9 is 90%). Call with no arguments to list every program Miles values, with the exact spelling to use. These are Miles' estimates, not market prices. Attribute them. Card facts only: no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes.

NameTypeReqDescription
pointsnumber–A balance to value, in points, or in dollars for a cash balance such as Uber Cash.
programstring–Loyalty program, e.g. 'World of Hyatt'. Matched loosely. Omit to list all.

No output schema declared.

No examples provided.

find_transfer_routes ~178

Which loyalty programs a currency transfers to, or which currencies reach a destination, and whether a transfer bonus is running. This is the route graph only. It does not carry transfer ratios, bonus sizes, expiry dates, or which route is worth taking. Card facts only: no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes.

NameTypeReqDescription
from_programstring–Source currency, e.g. 'Chase Ultimate Rewards'.
include_inactiveboolean–Include routes that have been discontinued.
limitnumber–Routes to return. Default 100, maximum 200.
only_with_bonusboolean–Only routes with a transfer bonus running.
to_programstring–Destination program, e.g. 'World of Hyatt'. Matched loosely; call with neither argument to list every source.

No output schema declared.

No examples provided.

get_card_facts ~96

Everything the public catalog holds on one card: issuer, annual fee, network, foreign transaction fee, rewards currency, and the names of its statement credits, lounge networks and protections. Card name is matched loosely. Card facts only: no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes.

NameTypeReqDescription
card_namestringyesCard name, e.g. 'Amex Platinum' or 'Venture X'.

No output schema declared.

No examples provided.

search_card_catalog ~258

Find credit cards open to new applicants by issuer, annual fee, network, rewards currency, or a benefit they carry. Returns a short row per card; call get_card_facts for one card's full record. Card facts only: no earning rates, welcome-offer amounts, transfer ratios, or bonus sizes.

NameTypeReqDescription
benefitstring–Words to look for in a card's statement credits, lounge networks, or purchase/travel protections, e.g. 'Global Entry', 'Priority Pass', 'trip delay'.
card_typestring–Personal or Business.
has_free_night_certificateboolean–Only cards granting a free night certificate.
has_lounge_accessboolean–Only cards carrying at least one lounge network.
issuerstring–Exact issuer name.
limitnumber–Rows to return. Default 10, maximum 25.
max_annual_feenumber–Highest annual fee in dollars, inclusive.
networkstring–Payment network.
no_foreign_transaction_feeboolean–Only cards with no foreign transaction fee.
rewards_currencystring–Loyalty currency the card earns, e.g. 'Chase Ultimate Rewards'. Matched loosely.

No output schema declared.

No examples provided.

Install

How do I install the ai.askmiles/catalog MCP server?

ai.askmiles/catalog is a hosted endpoint at https://api.askmiles.ai/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.

remote · api.askmiles.ai

# add to Claude Code
claude mcp add --transport http ai-askmiles-catalog 'https://api.askmiles.ai/mcp'
Common questions

What is the ai.askmiles/catalog MCP server?

ai.askmiles/catalog is an MCP server listed in the public MCP registry as ai.askmiles/catalog. Miles' public credit-card catalog: facts, transfer partners, valuations. Keyless, read-only. This page covers its hosted endpoint (https://api.askmiles.ai/mcp).

Is the ai.askmiles/catalog MCP server safe to use?

ai.askmiles/catalog scores 75 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 ai.askmiles/catalog MCP server expose?

ai.askmiles/catalog exposes 5 tools: search_card_catalog, get_card_facts, compare_card_facts, find_transfer_routes, estimate_point_value. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.

Does the ai.askmiles/catalog MCP server require authentication?

No. We connected to ai.askmiles/catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.askmiles/catalog MCP server still maintained?

ai.askmiles/catalog is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ai.askmiles/catalog MCP server?

VerifyMCP ran 12 checks on ai.askmiles/catalog, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about ai.askmiles/catalog: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.