mcp-server-indexnow

Created By
zizzfizzixa year ago
A Model Context Protocol (MCP) server allowing URL indexing requests via the IndexNow protocol. This server acts as a bridge, enabling MCP-compatible clients (like IDEs or AI assistants) to submit URLs to search engines using the IndexNow protocol for potentially faster content discovery and indexing.
Overview

What is Mcp Server Indexnow?

Mcp Server Indexnow is a server that allows URL indexing requests via the IndexNow protocol, acting as a bridge for MCP-compatible clients to submit URLs to search engines for faster content discovery and indexing.

How to use Mcp Server Indexnow?

To use the server, set up an IndexNow key for your website, configure the server with the key, and then interact with your MCP client to submit URLs for indexing.

Key features of Mcp Server Indexnow?

  • Submits single or multiple URLs to the IndexNow API.
  • Facilitates interaction with the IndexNow protocol through MCP clients.
  • Minimal configuration required after setting up the IndexNow key.

Use cases of Mcp Server Indexnow?

  1. Quickly notify search engines of new content on your website.
  2. Update search engines about changes to existing content.
  3. Remove URLs from search engine indexing when content is deleted.

FAQ from Mcp Server Indexnow?

  • How do I set up the IndexNow key?

You need to generate a key and place a specific text file on your web server to verify ownership.

  • Is there any specific installation required?

No specific installation is needed when using uvx; you can run it directly from the client app.

  • Can I submit multiple URLs at once?

Yes, you can submit multiple URLs in a single request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zizzfizzix
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago