D

npm:mcp-server-indexforge

https://www.npmjs.com/package/mcp-server-indexforge
67/100 · MCP Trust Grade · checked 2h ago · MCP 1.0.2

What it offers — 11 tools · Cloud & DevOps

indexing_status

Get an overview of your IndexForge account — total domains, URLs, how many are indexed, how many are submitted, and how many are dead (404). Also show

list_domains

List all domains managed in your IndexForge account with their URL counts, indexing stats, and last scan dates.

add_domain

Add a new domain to IndexForge for indexing management. Optionally provide a custom sitemap URL (defaults to /sitemap.xml). Returns the domain ID need

remove_domain

Remove a domain from IndexForge. Use list_domains first to get the domain ID.

scan_sitemap

Scan a domain

submit_urls

Submit pending URLs to Google (via Indexing API, 200/day limit) and to Bing/Yandex/10+ search engines (via IndexNow, unlimited). Only submits URLs tha

check_404s

Check all URLs in a domain for broken links (404s). Sends HEAD requests to every URL and categorizes them as live, redirect, dead, or error.

check_index_status

Check which URLs are actually indexed by Google using the URL Inspection API (requires Google service account credentials uploaded for this domain).

list_urls

List URLs for a domain with their submission status, index status, and HTTP status. Paginated — use page and limit parameters for large domains.

push_to_index

One-shot command: scan the sitemap for new URLs, then immediately submit everything to Google and IndexNow. Use this after deploying a website or publ

submission_history

View recent submission history — which domains were submitted, how many URLs went to Google vs IndexNow, and when.

Spec / packaging20%100
Security (OWASP MCP)30%25
Maintenance / popularity20%75
Tool hygiene15%70
Transparency / provenance15%90

Findings

WARNMCP08 References sensitive file paths / environment secrets.
INFO Static analysis of npm package mcp-server-indexforge@1.0.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:mcp-server-indexforge on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:mcp-server-indexforge grade D
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade D · wmcp.sh
[![MCP Trust Grade D](https://wmcp.sh/mcp/grade/npm%3Amcp-server-indexforge/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Amcp-server-indexforge)
<a href="https://wmcp.sh/mcp/grade/npm%3Amcp-server-indexforge"><img src="https://wmcp.sh/mcp/grade/npm%3Amcp-server-indexforge/badge.svg" alt="MCP Trust Grade D · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.