AI Wave
REMOTE · AIWAVE.ELOPSTUDIO.COM · 2 COMPONENTS
AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video.
Available components
Last scanned (14 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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 8 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1046 tokens (~130/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 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=YE2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5a45c3d690aacf1f82a4fc7da32b3462cb4 |
| SANs: *.elopstudio.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | DS published | 19718 | 13 | Verified |
| elopstudio.com. | No DS | 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://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.
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'
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 74 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?
No. We connected to AI Wave without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AI Wave MCP server?
VerifyMCP ran 12 checks on AI Wave, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AI Wave: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.