SLXD MCP server

Which servers in the official MCP registry are SLXD's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to SLXD

Whose server it is

Registry nameapp.slxd/aiapipricingverified in the MCP registry

The registry name sits under slxd.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools10
Server calls itselfAI API Pricing
Server version1.0.0
Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 1800 ms.

Measured dailydaily checks: 2, the first on 2026-10-19

Answeredmeasuring2 of the 7 daily checks it takes to print a share
Median first answer598 ms
Space in an agent's context≈ 1,370 tokensthe definitions of all its tools (10), which an agent carries on every turn
Tool definitionsA · 95 of 100

Parameters without a description: in 3 of 10

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-10-19

search_models
Searches the catalogue of AI models and returns their current prices, with a confidence level and the sources backing each price.
get_model_price
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…
compare_models
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…
price_history
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…
recent_changes
Lists recent price increases, decreases, additions and removals across the catalogue, newest first.
list_providers
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`…
data_sources
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.
find_tools
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…
tool_schema
Returns the full input schema of a single tool, including which arguments are required. Call it after find_tools and before run_tool.
run_tool
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "aiapipricing": {
      "type": "http",
      "url": "https://aiapipricing.slxd.app/mcp/aiapipricing"
    }
  }
}

Other servers listed as SLXD's

app.slxd/creatoraddress differs per installverified in the MCP registry
app.slxd/financeaddress differs per installverified in the MCP registry
app.slxd/lmsmcpnot asked yetverified in the MCP registry
app.slxd/lrsnot asked yetverified in the MCP registry
app.slxd/peoplenot asked yetverified in the MCP registry
app.slxd/projectsnot asked yetverified in the MCP registry
app.slxd/sharescormnot asked yetverified in the MCP registry
app.slxd/tendernot asked yetverified in the MCP registry
app.slxd/trainingnot asked yetverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.