# Rapid URL Indexer MCP > Rapid URL Indexer is an MCP Server for submitting specific URLs to search engines for indexing. Your AI client uses this server to monitor campaigns, check credit balances, and automate SEO pinging jobs. It handles the full lifecycle of tracking content visibility from submission through reporting. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** indexing, search-engine-optimization, link-building, url-submission, seo-monitoring, web-crawling ## Description You need your URLs indexed fast? You gotta get 'em submitted directly to search engines. The Rapid URL Indexer MCP Server handles that whole process—from kicking off a campaign to pulling the final report. It's how you automate SEO pinging jobs so you don't wanna spend hours manually tracking every single link submission. Before you even start, you gotta check your wallet. You use `get_credit_balance` to instantly pull up your remaining quota or credit balance for running index jobs. This tells you if you got enough budget locked down to run the campaign you're planning. It’s a quick look at your account credits so you don't get stuck halfway through a big job because you ran out of gas. When you're ready, you kick things off with `create_project`. You submit a whole batch of new URLs—you can drop one or fifty—and the server immediately starts an indexing campaign under a unique project ID. That unique ID is your key; it's how you track everything that follows. This tool takes all those links and spins up the initial job, making sure the process gets moving right away. Once the job is running, you gotta keep tabs on it. You can use `list_projects` to pull a rundown of every single indexing project—both the ones that are active and the ones that are already done—and get their current status IDs in your account list. This gives you a master view of everything you've got going. If you need more info on just one job, you use `retrieve_project`. You plug in the specific project ID you know about, and this tool pulls up all the detailed status, parameters, and metadata for that single campaign. You can see exactly what the server thinks is happening with those URLs right now. When it’s time to call it quits on a job, you need the final score. That's where `get_project_report` comes in. This tool retrieves the full, finalized report detailing precisely which submitted URLs were indexed successfully. You get the metrics; you see what worked and what didn't. Think of the whole cycle: First, check your funds with `get_credit_balance`. Then, use `create_project` to submit that big batch of links under a new project ID. While it runs, keep an eye on things by using `list_projects` for an overview or `retrieve_project` if you wanna deep-dive into one specific job's details and parameters. When the dust settles, you pull everything together with `get_project_report`. You never gotta worry about tracking visibility again; this server handles the whole lifecycle for you. ## Tools ### create_project Submits a batch of new URLs, kicking off an indexing campaign under a unique project ID. ### get_credit_balance Checks and reports your remaining quota or credit balance for running index jobs. ### get_project_report Retrieves the full, finalized report detailing which submitted URLs were indexed successfully. ### list_projects Lists all existing indexing projects and their current status IDs in your account. ### retrieve_project Gets the detailed status, parameters, and metadata for a specific project ID you already know. ## Prompt Examples **Prompt:** ``` Check my remaining Rapid URL Indexer credits. ``` **Response:** ``` You currently have 1,450 credits remaining in your account. ``` **Prompt:** ``` Submit the URL 'https://example.com/new-post' for indexing. ``` **Response:** ``` The URL has been successfully submitted for indexing. Campaign ID is 9981. ``` **Prompt:** ``` Check the status of indexing campaign 9981. ``` **Response:** ``` Campaign 9981 is 100% processed. 1 out of 1 link was successfully pushed to Google. ``` ## Capabilities ### Submit New Indexing Jobs The agent creates a new project and submits one or more URLs for immediate indexing. ### Check Account Credits You instantly retrieve your remaining indexing credits to ensure you have enough budget for the campaign. ### List All Projects The agent pulls a list of all past and active URL indexing projects by ID. ### Get Project Details You fetch the specific status, metadata, and current state for one defined project ID. ### View Final Reports The server generates a detailed report containing the indexing outcomes and metrics for a completed job. ## Use Cases ### Launching a New Content Pillar A content manager writes 50 new articles. Instead of manually submitting them one by one to the search console, they ask their agent: 'Submit these 50 URLs for indexing.' The agent runs `create_project`, and you get an immediate Campaign ID for tracking. ### Pre-Launch SEO Audit A developer is about to launch a major site section. They first run `list_projects` to see what's already indexed, then use `create_project` on the new URLs, and finally call `get_project_report` in a week to prove visibility. ### Troubleshooting Link Failures A marketing team suspects some old links aren't getting indexed. They check their budget with `get_credit_balance`, run `retrieve_project` on the suspected campaign, and get a detailed status report to pinpoint the failure. ### Scaling Link Building Campaigns Instead of running small, manual ping jobs, you feed 100 URLs into the system. The agent runs `create_project`, monitors the job via its ID, and when finished, pulls a comprehensive report using `get_project_report`. ## Benefits - **Immediate Visibility:** Instead of waiting for manual pinging, use `create_project` to submit URLs and get a confirmed Campaign ID instantly. You know the job started right away. - **Budget Control:** Use `get_credit_balance` to track your spending before running any large campaign. You won't waste credits on a job that’s already maxed out. - **Full Audit Trail:** Need proof of what was submitted? Call `list_projects` to see every indexing job you've ever run, making auditing simple. - **Deep Status Checks:** Don't guess if a project is done. Use `retrieve_project` with a specific ID to get the current status and last update timestamp. - **Actionable Reports:** The `get_project_report` tool doesn't just say 'done'; it provides metrics on how many links were successfully pushed, giving you real data. ## How It Works The bottom line is: your AI client handles the sequence—checking credits, starting the job, and pulling the report—in a single conversational flow. 1. First, check your budget by calling `get_credit_balance` to confirm you have enough credits. 2. Next, submit the URLs using `create_project`, specifying the target links and running a new campaign ID. 3. Finally, use `list_projects` to get the new Campaign ID, then call `get_project_report` with that ID to pull the final results. ## Frequently Asked Questions **How do I check my remaining credits using Rapid URL Indexer?** Call the `get_credit_balance` tool. It immediately tells you your available quota, preventing you from starting a campaign that will fail halfway through. **What is the difference between `list_projects` and `retrieve_project`?** `list_projects` gives you an overview of all job IDs in your account. You use `retrieve_project` when you have a specific ID and need to know its deep, current status or parameters. **Can I submit URLs for indexing using only the URL list?** No. You must first call `create_project`. This tool accepts your list of URLs and handles the submission logic; you can't just dump them into a single API endpoint. **How do I get the final results after using Rapid URL Indexer?** After the campaign is complete, use `get_project_report` and provide the specific Project ID. This tool pulls the metrics you need to see success rates. **If I use `create_project` with bad or inaccessible URLs, how does Rapid URL Indexer report failures?** The system flags all failed submissions. When you run `get_project_report`, the results explicitly list which submitted URLs failed and give a specific error code for each one (like 404 or access denied). **Are there rate limits when I use the Rapid URL Indexer tools?** Yeah, usage is primarily controlled by your credit balance. Running out of credits stops submissions until you acquire more. Always check your limit first using `get_credit_balance`. **What do I need to connect my agent securely to the Rapid URL Indexer MCP?** You'll need a valid API key and account credentials. Your AI client uses these keys for authorization on every tool call, including when you use `list_projects`. **After I run `retrieve_project`, how can I tell if the indexing process is fully complete?** The status output gives a percentage and a completion marker. You must see 100% processed before assuming the project is finished; then you can pull the final data using `get_project_report`. **How do I submit a new URL to be indexed?** Simply tell the agent to 'Index this URL: https://...', and it will dispatch the request using your available credits. **Can I check my remaining account credits?** Yes, ask the agent for your current balance and it will retrieve the exact credit amount from the API. **Can I track the status of my indexing campaigns?** Absolutely. Query the agent with your Campaign ID to see the progress and success rate of your submitted links.