# AI Wave (remote · aiwave.elopstudio.com)

AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video.

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

## Components

- remote · `aiwave.elopstudio.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/api-mcp.md), [page](https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/api-mcp)
- npm · `@elopstudio/ai-wave-mcp`: 39/100, [markdown](https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/elopstudio-ai-wave-mcp.md), [page](https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/elopstudio-ai-wave-mcp)

## Channel facts

- Endpoint: `https://aiwave.elopstudio.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## 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**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1035 tokens (~129/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the AI Wave MCP server?

AI Wave is a hosted endpoint at https://aiwave.elopstudio.com/api/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 com-elopstudio-aiwave-ai-wave 'https://aiwave.elopstudio.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-elopstudio-aiwave-ai-wave": {
      "url": "https://aiwave.elopstudio.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-elopstudio-aiwave-ai-wave": {
      "type": "http",
      "url": "https://aiwave.elopstudio.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-elopstudio-aiwave-ai-wave]
url = "https://aiwave.elopstudio.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-elopstudio-aiwave-ai-wave": {
      "type": "remote",
      "url": "https://aiwave.elopstudio.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-elopstudio-aiwave-ai-wave --url 'https://aiwave.elopstudio.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-elopstudio-aiwave-ai-wave:
    url: "https://aiwave.elopstudio.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-elopstudio-aiwave-ai-wave": {
      "Transport": "http",
      "Url": "https://aiwave.elopstudio.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-elopstudio-aiwave-ai-wave -t streamable-http -u 'https://aiwave.elopstudio.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-elopstudio-aiwave-ai-wave": {
      "type": "http",
      "url": "https://aiwave.elopstudio.com/api/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 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-22 (score 75, +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-09-20 (score 74, +1)

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

### 2026-09-16 (score 72, +1)

- [security] Tool “find_replacement” rewrote its description, which is the text the model reads
- [security] Tool “get_price_history” rewrote its description, which is the text the model reads
- [security] Tool “get_today” rewrote its description, which is the text the model reads
- [security] Tool “search_models” rewrote its description, which is the text the model reads
- [security] Tool “list_model_changes” rewrote its description, which is the text the model reads
- [security] Tool “compare_models” rewrote its description, which is the text the model reads
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.0.0 → 1.0.3
- [cosmetic] “search_models” reworded the description of “mode”
- [cosmetic] “search_models” reworded the description of “outputs”

### 2026-09-15 (score 71, 0)

- [functional regression] Schema quality: 762 → 1030
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “find_replacement”
- [functional] New tool “get_today”
- [cosmetic] “search_models” added an optional parameter “mode”
- [cosmetic] “search_models” added an optional parameter “accepts”
- [cosmetic] “search_models” added an optional parameter “outputs”

### 2026-09-14 (score 71, +38)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 82
- [functional] First check of Schema quality: fail

## MCP tools (8)

### `list_model_changes` (~141 tokens)

Changes across AI models: new releases, price changes, API changes and deprecations. Normalized from vendor release notes, Hugging Face, the OpenRouter catalog, GitHub and the LiteLLM price map, deduplicated per model, each marked official or pending review. Poll with `since` (unix seconds) and feed the returned `latest` back next time.

Input parameters:

- `limit` (number): 1-100, default 20
- `model` (string): Vendor slug, e.g. claude
- `since` (number): Unix seconds. Only changes detected after this, oldest first.
- `type` (string)

### `get_model` (~51 tokens)

Pricing, context length and catalog status for one model. Accepts an OpenRouter id (anthropic/claude-opus-5) or a Hugging Face repo id.

Input parameters:

- `id` (string, required)

### `get_price_history` (~81 tokens)

Price history for one model: when the price changed and to what. The public catalog only exposes the current price, so this answers 'was this cheaper last month?'. Each entry holds until the next one. History starts when AI Wave began recording, not when the model launched.

Input parameters:

- `id` (string, required): OpenRouter id or Hugging Face repo id

### `search_models` (~269 tokens)

Shortlist models by budget, context and capability, ranked by measured performance. Use this to answer 'which model should I use for X': it returns benchmark scores alongside price so the trade-off is visible in one call. Sort by a subject (math, coding, science, reading) to find a model good at one thing.

Input parameters:

- `accepts` (string): What the model must be able to take in, e.g. image for vision tasks.
- `limit` (number): 1-50, default 10
- `maxInputPrice` (number): USD per 1M input tokens
- `minContext` (number)
- `minIntelligence` (number): Lowest acceptable overall index. Leaders sit near 53; the median is 16.
- `mode` (string): What the model does. Non-chat modes are priced in other units: check price.unit.
- `outputs` (string): What the model produces. A model that accepts video but writes text is 'text', not 'video': filter on what you need made, not what it can read.
- `sortBy` (string): Ranking basis. Default 'intelligence' (overall). 'buzz' is popularity, not skill.
- `vendor` (string): OpenRouter namespace, e.g. anthropic

### `compare_models` (~135 tokens)

Put two or more models side by side: price, context, benchmark scores per subject, and what each costs per month at a given volume. Use this instead of calling get_model repeatedly: it aligns the fields and marks which subjects a model has not been tested on, so a missing score is not read as a low one.

Input parameters:

- `ids` (array, required): 2-6 OpenRouter ids, e.g. ['anthropic/claude-opus-5','openai/gpt-5.2']
- `monthlyMillionTokens` (number): Volume for the cost estimate. Default 10 (10M tokens a month).

### `estimate_cost` (~115 tokens)

What one model costs per month at a given token volume, in USD and KRW. Token prices are per million and hard to reason about directly; this turns them into a monthly bill. Input and output are mixed 75/25 unless you pass your own split.

Input parameters:

- `id` (string, required): OpenRouter id or Hugging Face repo id
- `inputShare` (number): 0-1, share of tokens that are input. Default 0.75
- `monthlyMillionTokens` (number): Default 10

### `get_today` (~77 tokens)

Today in one call: the top 5 models, which ones climbed, whose pricing changed in the last 24h, and what was newly listed in the last 7 days. Use this instead of paging list_model_changes and re-deriving the summary: price changes are already collapsed to one per model, with the raw count kept.

### `find_replacement` (~102 tokens)

What to switch to when a model is gone or you need a fallback. Ranked by closeness in measured performance, not by vendor or price: what you usually need to preserve first is the quality of the output. Candidates whose context window is less than half the original are excluded. Returns the score, price and context deltas so you can judge; we do not pick for you.

Input parameters:

- `id` (string, required): OpenRouter id or Hugging Face repo id

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/api-mcp#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: 33
- 2026-09-12: 33
- 2026-09-11: 33

## Common questions

### What is the AI Wave MCP server?

AI Wave is an MCP server listed in the public MCP registry as com.elopstudio.aiwave/ai-wave. AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video. This page covers its hosted endpoint (https://aiwave.elopstudio.com/api/mcp).

### Is the AI Wave MCP server safe to use?

AI Wave 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 Wave MCP server expose?

AI Wave exposes 8 tools: list_model_changes, get_model, get_price_history, search_models, compare_models, and 3 more. Their descriptions and schemas cost roughly 971 tokens of context every time the server is loaded.

### Does the AI Wave MCP server require authentication?

Yes. AI Wave asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AI Wave MCP server still maintained?

AI Wave 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://aiwave.elopstudio.com/api/mcp
- Authorisation metadata: https://aiwave.elopstudio.com/.well-known/oauth-protected-resource/api/mcp
- Repository: https://github.com/elopstudio/ai-wave-mcp
- Website: https://aiwave.elopstudio.com/api-docs
- Changelog RSS feed: https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-elopstudio-aiwave-ai-wave/api-mcp