# ai.askmiles/catalog (remote · api.askmiles.ai)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.askmiles.ai`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ai-askmiles-catalog/api.md), [page](https://verifymcp.io/servers/ai-askmiles-catalog/api)

## Channel facts

- Endpoint: `https://api.askmiles.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http ai-askmiles-catalog 'https://api.askmiles.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-askmiles-catalog": {
      "url": "https://api.askmiles.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-askmiles-catalog": {
      "type": "http",
      "url": "https://api.askmiles.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-askmiles-catalog]
url = "https://api.askmiles.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-askmiles-catalog": {
      "type": "remote",
      "url": "https://api.askmiles.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-askmiles-catalog --url 'https://api.askmiles.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-askmiles-catalog:
    url: "https://api.askmiles.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-askmiles-catalog": {
      "Transport": "http",
      "Url": "https://api.askmiles.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-askmiles-catalog -t streamable-http -u 'https://api.askmiles.ai/mcp'
```

### Other

```json
{
  "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.

## 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-25 (score 76, 0)

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

### 2026-09-24 (score 76, +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.

### 2026-09-22 (score 75, +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.

### 2026-09-20 (score 74, +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.

### 2026-09-18 (score 73, +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.

### 2026-09-16 (score 72, +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.

### 2026-09-14 (score 71, +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.

### 2026-09-11 (score 70, +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.

## MCP tools (5)

### `search_card_catalog` (~258 tokens)

Search the card catalog

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.

Input parameters:

- `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.

### `get_card_facts` (~96 tokens)

One card's catalog record

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.

Input parameters:

- `card_name` (string, required): Card name, e.g. 'Amex Platinum' or 'Venture X'.

### `compare_card_facts` (~67 tokens)

Compare cards side by side

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.

Input parameters:

- `card_names` (array, required): Card names, matched loosely.

### `find_transfer_routes` (~178 tokens)

Which transfer routes exist

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.

Input parameters:

- `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.

### `estimate_point_value` (~120 tokens)

What a point is worth

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.

Input parameters:

- `points` (number): A balance to value, in points.
- `program` (string): Loyalty program, e.g. 'World of Hyatt'. Matched loosely. Omit to list all.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-askmiles-catalog/api#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 75
- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 73
- 2026-09-18: 73
- 2026-09-17: 72
- 2026-09-16: 72
- 2026-09-15: 71
- 2026-09-14: 71
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 70
- 2026-09-10: 69
- 2026-09-09: 69
- 2026-09-08: 68
- 2026-09-07: 68
- 2026-09-06: 67
- 2026-09-05: 67
- 2026-09-04: 66
- 2026-09-03: 66
- 2026-09-02: 65
- 2026-09-01: 65
- 2026-08-31: 64
- 2026-08-30: 64
- 2026-08-29: 63
- 2026-08-28: 63
- 2026-08-27: 63

## 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 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.

## Links

- Remote endpoint: https://api.askmiles.ai/mcp
- Website: https://askmiles.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-askmiles-catalog/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-askmiles-catalog/api.json
- HTML version of this page: https://verifymcp.io/servers/ai-askmiles-catalog/api