mcp server
KDP Niche Research
Kindle niche intelligence (demand/competition/BSR/revenue) gated by x402 USDC on Base.
Description as published by the maintainer. Source
- version 0.2.0
- slowing
- retrieval
slowing — Registry entry last updated 2026-05-02. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
list_niches(limit, offset)- List available KDP niche keywords ordered by demand score. Use this to discover what Kindle publishing niches are available for detailed research. Returns keywords ordered by demand score (highest first). This endpoint is free — no payment required. Args: limit: Number of results to return (1-100, default 20) offset: Pagination offset (default 0)
research_niche(keyword, x_payment)- Get detailed KDP niche intelligence for a specific keyword. Returns demand score, competition score, Amazon BSR range, estimated monthly revenue, review threshold, average book pricing, and data freshness for the given Kindle publishing niche. Pricing tiers (x402 USDC on Base network): - $0.03 per query for cached/pre-seeded keywords - $0.10 per query for live on-demand research (new keywords) Use the free `list_niches` tool first to see available keywords. Payment options: 1. Set the KDP_X_PAYMENT environment variable on the server for auto-pay. 2. Pass a valid x402 payment header via the x_payment argument. 3. If neither is set, the tool returns structured 402 payment instructions that an x402-capable agent can use to construct and retry payment. Args: keyword: The KDP niche keyword to research (e.g. "romance novels", "keto cookbook") x_payment: Optional base64-encoded x402 payment header. Takes precedence over the KDP_X_PAYMENT environment variable. Required: keyword.
Last successful function declaration observed on . Source: https://nichedata.dev/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://nichedata.dev/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-02 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-05-02 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | nichedata.dev | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | nichedata.dev |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json