Lunoo Rankings

Consensus rankings for 75,000+ products across 2,600+ niches.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
100%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~638Tokens (tool definitions)
~980 BTypical response size
Minimal attention impact (0.50% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "rankings": {
      "url": "https://lunoo.com/mcp"
    }
  }
}

Remote endpoints

https://lunoo.com/mcpstreamable-http

What it can do

Tool inventory

Tools (3)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢find_niche(query)

Resolve a natural-language ranking request to one or more verified Lunoo niche slugs. Pass the user's request instead of guessing a slug. It handles common aliases, typos, and use-case terms, and returns item counts, match explanations, confidence, and tracked Lunoo URLs. Unsupported or unclear requests return an error instead of an unrelated fallback. Choose the closest returned slug, then call get_rankings with that exact slug. Never invent a niche slug or ranking.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "minLength": 1,
      "maxLength": 240,
      "description": "Natural-language ranking request, for example \"anime\", \"coffee makers\", or \"best laptop for video editing\". Use the user's request rather than a guessed slug."
    }
  },
  "required": [
    "query"
  ]
}
🟢get_rankings(niche, limit)

Fetch ranked Lunoo results for a verified niche slug or natural-language request. It returns rank, score, description, confidence, and a canonical Lunoo URL for every item, plus the selected niche and resolution explanation. Prefer calling find_niche first, but this tool can resolve natural language itself. Cite the returned ranking URL and do not invent items, scores, or slugs.

Input Schema

{
  "type": "object",
  "properties": {
    "niche": {
      "type": "string",
      "minLength": 1,
      "maxLength": 240,
      "description": "Exact niche slug returned by find_niche, or a natural-language request such as \"best laptop for video editing\". Examples: \"anime\" or \"japanese-city\"."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 50,
      "description": "Number of ranked items to return, from 1 to 50. Defaults to 10.",
      "default": 10
    }
  },
  "required": [
    "niche"
  ]
}
🟢get_item(slug)

Use this after a ranking result when the user wants details about one item. Pass the exact item slug from a Lunoo result or URL. It returns the canonical Lunoo URL for the item and public structured metadata. This is read-only and must not be used to invent rankings that were not returned by get_rankings.

Input Schema

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "minLength": 1,
      "maxLength": 160,
      "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
      "description": "Exact item slug from a Lunoo ranking result or item URL, for example \"frieren-beyond-journeys-end\"."
    }
  },
  "required": [
    "slug"
  ]
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded3 tools
verifiedversion not recorded3 tools