SLXD AI API Pricing
REMOTE · AIAPIPRICING.SLXD.APP
Look up, compare and track AI model API prices from an AI assistant. No sign-in needed.
Available components
Last scanned (18 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 22 Oct 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 Security51
- 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 1 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 912 tokens (~91/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "run_tool" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 60
First indexed and scored.
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 22 Oct 2026 · Probed https://aiapipricing.slxd.app/mcp/aiapipricing
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=slxd.app | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 486aa0d1a50c153f135023f07299d598 |
| SANs: slxd.app, *.slxd.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aiapipricing.slxd.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| slxd.app. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://plausible.studiolxd.com; style-src 'self' 'sha256-skqujXORqzxt1aE0NNXxujEanPTX6raoqSscTV/Ww/Y='; style-src-attr 'unsafe-inline'; img-src 'self' data: blob: https:; media-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://plausible.studiolxd.com https://o4510682524876800.ingest.de.sentry.io https://911681542fbe663ac3964973432d1d2f.r2.cloudflarestorage.com https://account.slxd.app; frame-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aiapipricing.slxd.app/mcp/aiapipricing | Verified | 200 | |
| http (plaintext) | http://aiapipricing.slxd.app/mcp/aiapipricing | Inconclusive | 406 |
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 Compare models ~82
Returns the current prices of several models side by side. Amounts in credits are never converted to money, so a credit-billed model is not comparable to a token-billed one. Two dimensions can share a label, so the ones that would collide carry their qualifiers, e.g. 'Web search (context size: high)'.
| Name | Type | Req | Description |
|---|---|---|---|
| models | array | yes | – |
No output schema declared.
No examples provided.
data_sources Data sources and their health ~49
Explains where the prices come from: which sources are consulted, their weight and licence, when each last succeeded, and whether any is currently failing. Use this to judge how much to trust a price.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_tools Find tools ~95
Searches the full catalogue of available tools by keyword and returns the matching tool names with a short description. Use it when no directly-listed tool fits the task — many tools are available but not listed. Then call tool_schema for the one you picked, and run_tool to execute it.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Space-separated keywords, e.g. 'invoice pdf export'. Matched against tool names and descriptions; any term may match. |
No output schema declared.
No examples provided.
get_model_price Get a model's prices ~181
Returns every current price for one model — input, output, cached reads, batch and priority tiers, context brackets — with the confidence level and which sources agree. By default these are the maker's own prices; pass `channel` to get what a reseller charges for the same model instead. Two dimensions can share a label, so the ones that would collide carry their qualifiers, e.g. 'Web search (context size: high)'.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Sales channel to price. Omit for the maker's own price. `direct` is the maker, the rest resell the same model at their own rate; a channel that does not sell this model returns the model with no pric… |
| model | string | yes | Model id as `provider/slug`, e.g. `anthropic/claude-sonnet-4-5`. |
No output schema declared.
No examples provided.
list_providers List providers ~75
Lists every provider in the catalogue and how many models each has. These are the houses that MAKE the models: a reseller (Vertex, Bedrock, Azure, OpenRouter, a subscription plan) is a sales channel, not a provider — ask `get_model_price` with a `channel` for what one of those charges.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
price_history Price history ~171
Returns a model's price over time. Each point is [date, amount] with the date as YYYY-MM-DD. The series holds only the points where the price CHANGED — prices are step functions, so a stable model is one point, not one per day; when a price changed twice on one day, both points are returned with the same date, in order. One series per price dimension: two dimensions can share a label, so the ones that would collide carry their qualifiers, e.g. 'Web search (context size: high)'.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO date, inclusive. |
| model | string | yes | Model id as `provider/slug`, e.g. `anthropic/claude-sonnet-4-5`. |
| to | string | – | ISO date, inclusive. |
No output schema declared.
No examples provided.
recent_changes Recent price changes ~40
Lists recent price increases, decreases, additions and removals across the catalogue, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
run_tool Run a tool ~97
Executes a tool by name with the given arguments. Use it for tools that are not directly listed — look them up with find_tools and check their arguments with tool_schema first. Prefer a directly-listed tool whenever one fits. If the action is destructive, ask the user to confirm before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | Arguments object matching the tool's schema. |
| name | string | yes | Exact tool name, as returned by find_tools. |
No output schema declared.
No examples provided.
search_models Search models ~72
Searches the catalogue of AI models and returns their current prices, with a confidence level and the sources backing each price.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| provider | string | – | Restrict to one provider slug, e.g. `openai`. |
| query | string | – | Free text matched against name and id. |
No output schema declared.
No examples provided.
tool_schema Get a tool's schema ~50
Returns the full input schema of a single tool, including which arguments are required. Call it after find_tools and before run_tool.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Exact tool name, as returned by find_tools. |
No output schema declared.
No examples provided.
How do I install the SLXD AI API Pricing MCP server?
SLXD AI API Pricing is a hosted endpoint at https://aiapipricing.slxd.app/mcp/aiapipricing, 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 · aiapipricing.slxd.app
claude mcp add --transport http app-slxd-aiapipricing 'https://aiapipricing.slxd.app/mcp/aiapipricing'
What is the SLXD AI API Pricing MCP server?
SLXD AI API Pricing is an MCP server listed in the public MCP registry as app.slxd/aiapipricing. Look up, compare and track AI model API prices from an AI assistant. No sign-in needed. This page covers its hosted endpoint (https://aiapipricing.slxd.app/mcp/aiapipricing).
Is the SLXD AI API Pricing MCP server safe to use?
SLXD AI API Pricing scores 61 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 SLXD AI API Pricing MCP server expose?
SLXD AI API Pricing exposes 10 tools: search_models, get_model_price, compare_models, price_history, recent_changes, and 5 more. Their descriptions and schemas cost roughly 912 tokens of context every time the server is loaded.
Does the SLXD AI API Pricing MCP server require authentication?
No. We connected to SLXD AI API Pricing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SLXD AI API Pricing MCP server still maintained?
SLXD AI API Pricing is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.