Rank by Ouroboros
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | listen port, default 44721 | 44721 |
| APP_BASE_URL | No | public origin; determines the Google redirect URI | http://127.0.0.1:44721 |
| DATABASE_URL | No | postgres backend | |
| STORAGE_FILE | No | file backend path | ./data/rank-store.json |
| RANK_TEST_HOOKS | No | Set to 1 to let tests complete MCP login without Google. The process refuses to start when that is set and NODE_ENV=production. | |
| STORAGE_BACKEND | No | memory, file, or postgres | |
| GOOGLE_CLIENT_ID | Yes | Google sign-in and Search Console | |
| STRIPE_SECRET_KEY | Yes | Checkout and the billing portal | |
| STRIPE_PRICE_YEARLY | Yes | yearly Checkout price id | |
| GOOGLE_CLIENT_SECRET | Yes | Google token exchange | |
| STRIPE_PRICE_MONTHLY | Yes | monthly Checkout price id | |
| TOKEN_ENCRYPTION_KEY | Yes | encrypting refresh tokens and signing the browser session | |
| STRIPE_WEBHOOK_SECRET | Yes | Stripe webhook signatures |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_propertiesA | List the Search Console properties on the connected Google account. Returns siteUrl and permissionLevel exactly as the sites.list API returned them. |
| top_queriesA | Top search queries for one property and date range. clicks, impressions, ctr, and position are copied from Search Console. ctr is a fraction from 0 to 1, not a percent. Omit dates to use the default 28-day window. |
| top_pagesB | Top pages for one property and date range. Metrics are copied from Search Console rows. ctr is the API fraction from 0 to 1. Omit dates to use the default 28-day window. |
| performance_trendsB | Daily clicks, impressions, ctr, and position for a property. Each row is a date Search Console returned. Missing dates are not filled in, and ctr is the API fraction. |
| compare_periodsB | Compare two date ranges using the Search Console totals for a property (no dimension grouping). Reports both API metric objects. Differences are labeled as derived from those returned numbers. Omit compare dates to use the previous window of the same length. |
| quick_winsA | Queries with high impressions and low ctr in Search Console. Defaults are at least 100 impressions and ctr at or below 0.02 (the API fraction, so 0.02 is 2%). Does not estimate missed clicks. |
| dropped_pagesB | Pages whose Search Console position got worse, whose clicks fell, or that disappeared from the current response. Does not invent zeros for pages the current response omitted. |
| inspect_urlB | URL Inspection status for one URL on a property you can access. Returns the Search Console inspection response, including verdict, coverage, and last crawl fields when the API sent them. |
| account_statusA | Whether Google Search Console is connected, when the 14-day trial ends, and whether Pro access is active. Does not query Search Console and does not include a price. |
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 9 tools
Each tool targets a distinct analysis or resource: listing properties, top queries/pages, URL inspection, trends, period comparison, quick wins, dropped pages, and account status. The purposes are clearly differentiated with no overlap, so an agent can easily select the right tool.
All tool names follow a consistent snake_case pattern, using noun compounds or adjective_noun structures (e.g., top_queries, inspect_url, performance_trends). The naming is predictable and readable throughout.
With 9 tools, the set is well-scoped for a Google Search Console analysis server, covering core reporting and inspection tasks without redundancy. Each tool earns its place and the count is within the ideal 3-15 range.
The tools provide strong coverage for common GSC analysis: listing properties, top queries/pages, trends, comparisons, quick wins, dropped pages, and account status. Minor gaps exist, such as the ability to filter or segment queries/pages by device or country, but the core lifecycle is well addressed.