io.github.epolat/rankjot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RANKJOT_API_KEY | Yes | API key for RankJot. Generate at rankjot.com under Account → API access. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_rankA | Check where a domain ranks on Google for a keyword. Args: domain: the site to look up, e.g. "example.com" (scheme/www/path ignored). keyword: the search query to rank for. country: ISO country code for the Google market (default "us"), e.g. "gb", "de". Rankings differ by country, so pass the market the user cares about. Returns a dict with the 1-based |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of overlap or confusion about which tool to invoke. The tool's purpose is well-defined and unambiguous.
The tool name 'check_rank' uses a clear verb_noun snake_case convention. Although there is no comparison set, the naming is internally consistent and predictable.
The server is narrowly scoped to a single rank-checking operation, so one tool is serviceable. However, related features like batch ranking checks or quota status would strengthen the server, making the count slightly thin.
The tool covers the core 'check rank' operation completely and returns relevant data. The lack of batch operations, historical tracking, or multi-keyword support leaves a notable gap for a rank-checking service.