AI Wave
REMOTE · AIWAVE.ELOPSTUDIO.COM · 2 COMPONENTS · SCANNED SEP 25
AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video.
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · aiwave.elopstudio.com
claude mcp add --transport http com-elopstudio-aiwave-ai-wave 'https://aiwave.elopstudio.com/api/mcp'
{
"mcpServers": {
"com-elopstudio-aiwave-ai-wave": {
"url": "https://aiwave.elopstudio.com/api/mcp"
}
}
} {
"servers": {
"com-elopstudio-aiwave-ai-wave": {
"type": "http",
"url": "https://aiwave.elopstudio.com/api/mcp"
}
}
} [mcp_servers.com-elopstudio-aiwave-ai-wave] url = "https://aiwave.elopstudio.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-elopstudio-aiwave-ai-wave": {
"type": "remote",
"url": "https://aiwave.elopstudio.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-elopstudio-aiwave-ai-wave --url 'https://aiwave.elopstudio.com/api/mcp' --transport streamable-http
mcp_servers:
com-elopstudio-aiwave-ai-wave:
url: "https://aiwave.elopstudio.com/api/mcp" {
"McpServers": {
"com-elopstudio-aiwave-ai-wave": {
"Transport": "http",
"Url": "https://aiwave.elopstudio.com/api/mcp"
}
}
} assistant mcp add com-elopstudio-aiwave-ai-wave -t streamable-http -u 'https://aiwave.elopstudio.com/api/mcp'
{
"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.
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 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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +1
- 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 security
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.0.3 functional
- “search_models” reworded the description of “mode” cosmetic
- “search_models” reworded the description of “outputs” cosmetic
- 15 Sept 26 0
- Schema quality: 762 → 1030 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “find_replacement” functional
- New tool “get_today” functional
- “search_models” added an optional parameter “mode” cosmetic
- “search_models” added an optional parameter “accepts” cosmetic
- “search_models” added an optional parameter “outputs” cosmetic
- 14 Sept 26 +38
- Injection markers: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
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://aiwave.elopstudio.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.elopstudio.com | CN=YE1,O=Let's Encrypt,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 529bd74ae02c1aae5bc1f3266af6cefe72c |
| SANs: *.elopstudio.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aiwave.elopstudio.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| elopstudio.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="AI Wave", resource_metadata="https://aiwave.elopstudio.com/.well-known/oauth-protected-resource"
Bearer realm="AI Wave", resource_metadata="https://aiwave.elopstudio.com/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://aiwave.elopstudio.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://aiwave.elopstudio.com/api/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aiwave.elopstudio.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://aiwave.elopstudio.com/api/mcp | HTTPS enforced | 308 | https://aiwave.elopstudio.com/api/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_models ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | 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). |
No output schema declared.
No examples provided.
estimate_cost ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | OpenRouter id or Hugging Face repo id |
| inputShare | number | – | 0-1, share of tokens that are input. Default 0.75 |
| monthlyMillionTokens | number | – | Default 10 |
No output schema declared.
No examples provided.
find_replacement ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | OpenRouter id or Hugging Face repo id |
No output schema declared.
No examples provided.
get_model ~51
Pricing, context length and catalog status for one model. Accepts an OpenRouter id (anthropic/claude-opus-5) or a Hugging Face repo id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_price_history ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | OpenRouter id or Hugging Face repo id |
No output schema declared.
No examples provided.
get_today ~77
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_model_changes ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
search_models ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.