StableDomains

Find expiring domains

find_dropping_domains

Read-onlyIdempotent

Find expiring, pending-delete and just-dropped domains ranked by a verified quality score (0-100) built from sampled Wayback snapshots (real site vs parked/for-sale), Common Crawl presence, dictionary/brandability and spam heuristics; Majestic referring subnets only count when the archive shows a real site. Parked and spam names are hidden by default; each item includes quality_reasons. Free tier returns top 25; status=available names can be bought immediately with create_order. For presets, estimated value, multi-TLD and keyword filters use drop_radar.

Input Schema

Name	Required	Description
`q`	No
`tld`	No
`sort`	No
`limit`	No	max 25 on the free tier
`order`	No	sort direction; default depends on sort
`cursor`	No	next_cursor from the previous call
`status`	No
`max_len`	No
`min_age`	No	min years of archive history
`min_len`	No
`max_price`	No
`min_brand`	No
`no_digits`	No
`no_hyphen`	No
`min_quality`	No
`show_parked`	No	include names whose archive shows only parked/for-sale pages (hidden by default)
`include_spam`	No	include spammy names (hidden by default)
`min_backlinks`	No
`available_only`	No	only names registrable now
`drops_within_days`	No	pending-delete names dropping within N days

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 30, 2026

addedInput schema / properties / available_only

Added value: +{
+  "description": "only names registrable now",
+  "type": "boolean"
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "next_cursor from the previous call",
+  "type": "string"
+}

addedInput schema / properties / drops_within_days

Added value: +{
+  "description": "pending-delete names dropping within N days",
+  "type": "integer"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "max 25 on the free tier",
+  "type": "integer"
+}

addedInput schema / properties / min_quality
```
Added value: +{
+  "type": "integer"
+}
```

addedInput schema / properties / order

Added value: +{
+  "description": "sort direction; default depends on sort",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}

addedInput schema / properties / show_parked

Added value: +{
+  "description": "include names whose archive shows only parked/for-sale pages (hidden by default)",
+  "type": "boolean"
+}

changedInput schema / properties / sort / enum

Previous value: -[
-  "score",
-  "backlinks",
-  "brand",
-  "new",
-  "drops",
-  "length"
-]New value: +[
+  "quality",
+  "value",
+  "price",
+  "length",
+  "drops",
+  "new",
+  "brand",
+  "backlinks",
+  "domain",
+  "score"
+]

First observedOct 28, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds substantial context beyond the annotations: default hiding of parked and spam names, inclusion of quality_reasons, free-tier top-25 limits, and the archive-based quality scoring model. With readOnlyHint and idempotentHint already covering safety, this is strong behavioral context, though it does not discuss pagination or full return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and primary scope are front-loaded in the first sentence, followed by defaults, tier limits, and sibling routing. The description is dense but generally earns its space, though the detailed scoring heuristic could be slightly tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a complex 20-parameter search tool with no output schema, the description covers the critical concepts: ranking, quality reasons, hidden defaults, tier limits, purchase path, and when to use drop_radar instead. It is not fully complete because many filter parameters lack semantic guidance.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains several important semantics: quality score range and composition, default hiding of parked/spam names, status=available purchasability, and the free-tier limit. However, schema description coverage is only 40% across 20 parameters, and many filters such as q, tld, min_age, min_brand, no_digits and no_hyphen remain undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: find expiring, pending-delete and just-dropped domains. It also distinguishes the tool from siblings by naming drop_radar for presets, estimated value, multi-TLD and keyword filters, and create_order for immediate purchases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly directs agents to drop_radar for preset-driven, valuation, multi-TLD and keyword-filter use cases. It also clarifies that status=available results can be bought immediately with create_order, giving a clear next-step alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All StableDomains tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?