Rapid URL Indexer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPID_INDEXER_API_KEY | Yes | Your Rapid URL Indexer API key |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_urlsA | Submit URLs for Google indexing via Rapid URL Indexer. Each URL costs 1 credit (or 3 in Apex Mode for faster indexing). URLs are tracked to prevent duplicate submissions. |
| submit_sitemapA | Parse and submit URLs from a sitemap.xml file. Automatically deduplicates against previously submitted URLs. Supports filtering by regex pattern. |
| check_balanceA | Get current Rapid URL Indexer credit balance. |
| list_projectsB | List all indexing projects from the Rapid URL Indexer API. |
| get_project_statusC | Get detailed status for a specific indexing project. |
| get_reportA | Download indexing report for a project showing which URLs were indexed. |
| get_historyA | Get submission history from local tracking. Shows summary stats, per-app breakdowns, and recent submissions. |
| get_statsB | Get overall statistics and usage tracking. Includes projections toward 50k/year goal. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Submission History | Full submission history across all apps |
| Tracked Apps | List of all tracked apps with summary stats |
TDQS
Scored across 8 tools
Each tool targets a distinct function: submitting URLs, submitting sitemaps, checking balance, managing projects, and retrieving reports/history/stats. There is no overlap or ambiguity between tool purposes.
All tools follow a consistent verb_noun pattern (e.g., submit_urls, get_report, list_projects). No mixed conventions or irregular naming.
8 tools is well-scoped for the service, covering submission, monitoring, and reporting without unnecessary bloat or missing essentials.
The tool set covers the full lifecycle: submit individual URLs or sitemaps, check credits, list and inspect projects, download reports, and review local history/stats. No obvious dead ends or critical missing operations for the stated purpose.