ai.askmiles/catalog
REMOTE · API.ASKMILES.AI · SCANNED SEP 25
Miles' public credit-card catalog: facts, transfer partners, valuations. Keyless, read-only.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 903 tokens (~180/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
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
claude mcp add --transport http ai-askmiles-catalog 'https://api.askmiles.ai/mcp'
{
"mcpServers": {
"ai-askmiles-catalog": {
"url": "https://api.askmiles.ai/mcp"
}
}
} {
"servers": {
"ai-askmiles-catalog": {
"type": "http",
"url": "https://api.askmiles.ai/mcp"
}
}
} [mcp_servers.ai-askmiles-catalog] url = "https://api.askmiles.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-askmiles-catalog": {
"type": "remote",
"url": "https://api.askmiles.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-askmiles-catalog --url 'https://api.askmiles.ai/mcp' --transport streamable-http
mcp_servers:
ai-askmiles-catalog:
url: "https://api.askmiles.ai/mcp" {
"McpServers": {
"ai-askmiles-catalog": {
"Transport": "http",
"Url": "https://api.askmiles.ai/mcp"
}
}
} assistant mcp add ai-askmiles-catalog -t streamable-http -u 'https://api.askmiles.ai/mcp'
{
"mcpServers": {
"ai-askmiles-catalog": {
"type": "http",
"url": "https://api.askmiles.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 25 Sept 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. | present | 3799 | 8 | Verified |
| askmiles.ai. | absent | 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 |
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 →
compare_card_facts Compare cards side by side ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| card_names | array | yes | Card names, matched loosely. |
No output schema declared.
No examples provided.
estimate_point_value What a point is worth ~120
Miles' own estimate of a loyalty point's value in cents, optionally multiplied by a balance. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| points | number | – | A balance to value, in points. |
| program | string | – | Loyalty program, e.g. 'World of Hyatt'. Matched loosely. Omit to list all. |
No output schema declared.
No examples provided.
find_transfer_routes Which transfer routes exist ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_program | string | – | Source currency, e.g. 'Chase Ultimate Rewards'. |
| include_inactive | boolean | – | Include routes that have been discontinued. |
| limit | number | – | Routes to return. Default 100, maximum 200. |
| only_with_bonus | boolean | – | Only routes with a transfer bonus running. |
| to_program | string | – | 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 One card's catalog record ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| card_name | string | yes | Card name, e.g. 'Amex Platinum' or 'Venture X'. |
No output schema declared.
No examples provided.
search_card_catalog Search the 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.
| Name | Type | Req | Description |
|---|---|---|---|
| benefit | string | – | 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_type | string | – | Personal or Business. |
| has_free_night_certificate | boolean | – | Only cards granting a free night certificate. |
| has_lounge_access | boolean | – | Only cards carrying at least one lounge network. |
| issuer | string | – | Exact issuer name. |
| limit | number | – | Rows to return. Default 10, maximum 25. |
| max_annual_fee | number | – | Highest annual fee in dollars, inclusive. |
| network | string | – | Payment network. |
| no_foreign_transaction_fee | boolean | – | Only cards with no foreign transaction fee. |
| rewards_currency | string | – | Loyalty currency the card earns, e.g. 'Chase Ultimate Rewards'. Matched loosely. |
No output schema declared.
No examples provided.
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 76 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 719 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 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.