AI Wave

com.elopstudio.aiwavePublished by aiwave.elopstudio.comOfficial publisherv1.1.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableData & AnalyticsAI & ML

Overview

AI-generated overview

AI Wave tracks AI model releases, price changes and deprecations in one feed, letting an assistant check what changed, compare models and estimate costs.

What you can do
Track model changes: list new releases, price moves, API changes and deprecations since a given time, or get a one-call daily digest of top models and recent changes. Look up models: get price, context length and catalog status for one model by OpenRouter or Hugging Face id, and see its price history. Choose a model: search by budget, context and capability with benchmark scores, or compare several models side by side. Plan costs: estimate a monthly bill at a given token volume in USD and KRW. Find fallbacks: rank replacement models by closeness in measured performance when a model is gone.
When to use it
Useful when you depend on specific AI models and need to know whether anything changed, such as new releases, price moves or withdrawals. Also suited to picking a model for a task, comparing candidates, or budgeting token spend.
Requirements
Runs as a remote streamable HTTP endpoint or as a local npm package started with npx, which wraps the remote endpoint. An API key is optional: without one you get 100 calls per day per IP; with one, 1,000 calls per day. The key is supplied as AIWAVE_API_KEY for the local package or as an Authorization bearer header for the remote endpoint. Network access is required.
Before you install
The API key is a secret; keep it out of shared configuration and logs. Without a key, usage is limited per IP address. The server reports on third-party model catalogs and vendor notes, so figures such as prices and benchmark scores should be checked against the original sources before relying on them.

Installation

In SourceWeft

  1. Open AI Wave in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.elopstudio.aiwave%2Fai-wave/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

@elopstudio/ai-wave-mcp

MCP server for AI Wave — a normalized feed of AI model releases, price changes, API changes and deprecations, assembled from vendor release notes, Hugging Face, the OpenRouter catalog and GitHub.

Why

Picking a model? Call the OpenRouter catalog directly — it is free and public.

This is for the other question: did anything I depend on change? New releases, price moves, and models being withdrawn, in one feed, deduplicated per model, each marked official or pending review.

Setup

Get a key at https://aiwave.elopstudio.com/member, then:

json
{  "mcpServers": {    "ai-wave": {      "command": "npx",      "args": ["-y", "@elopstudio/ai-wave-mcp"],      "env": { "AIWAVE_API_KEY": "aiw_live_..." }    }  }}

If your client supports remote MCP, prefer that — no install, always current:

json
{  "mcpServers": {    "ai-wave": {      "type": "http",      "url": "https://aiwave.elopstudio.com/api/mcp",      "headers": { "Authorization": "Bearer aiw_live_..." }    }  }}

Tools

ToolWhat it answers
list_model_changesWhat changed since I last checked? Poll with since, feed back latest.
get_modelPrice, context and catalog status for one model (OpenRouter or Hugging Face id).
search_modelsWhich models fit this budget and context, ordered by current attention?

Limits

Free tier: 1,000 calls/day. Remaining calls come back in x-ratelimit-remaining.

This package is a thin stdio wrapper around the remote endpoint — tool definitions live on the server, so you get new tools without updating it.

Source: README.md at commit a9433d5

Tools

8

list_model_changes

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.

Parameterstypelimitmodelsince

get_model

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

Parametersidrequired

get_price_history

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.

Parametersidrequired

search_models

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.

ParametersmodelimitsortByvendoracceptsoutputsminContextmaxInputPriceminIntelligence

compare_models

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.

ParametersidsrequiredmonthlyMillionTokens

estimate_cost

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.

ParametersidrequiredinputSharemonthlyMillionTokens

get_today

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.

Takes no parameters.

find_replacement

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.

Parametersidrequired

Version history

2
  1. v1.1.0LatestOct 13, 2026
  2. v1.0.3Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts