Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.joepangallo/mcp-server-indexforge

NPM · MCP-SERVER-INDEXFORGE · SCANNED AUG 3

Submit URLs to Google and Bing for indexing, scan sitemaps, check index status.

+24 this week 64 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 154 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 616 tokens (~56/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · mcp-server-indexforge

# add to Claude Code
claude mcp add joepangallo-mcp-server-indexforge -- npx -y mcp-server-indexforge
# add to Codex CLI
codex mcp add joepangallo-mcp-server-indexforge -- npx -y mcp-server-indexforge
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "joepangallo-mcp-server-indexforge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-indexforge"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add joepangallo-mcp-server-indexforge --command npx --arg -y --arg mcp-server-indexforge
# ~/.hermes/config.yaml
mcp_servers:
  joepangallo-mcp-server-indexforge:
    command: "npx"
    args: ["-y", "mcp-server-indexforge"]
// mcp.json
{
  "mcpServers": {
    "joepangallo-mcp-server-indexforge": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-indexforge"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +33
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.27 functional
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • Licence: MIT functional
  • 2 Aug 26 +2
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified functional
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Licence: MIT functional
  • 1 Aug 26 +29
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
    • Maintenance: unverified → pass functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 31 Jul 26 −18
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −22
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 27 Jul 26 40

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 11 exposed · ~616 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
add_domain ~81

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

NameTypeReqDescription
domainstringyesThe domain to add (e.g. 'example.com')
sitemap_urlstringCustom sitemap URL (default: https://domain/sitemap.xml)

No output schema declared.

No examples provided.

check_404s ~56

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.

NameTypeReqDescription
domain_idstringyesThe domain ID to check

No output schema declared.

No examples provided.

check_index_status ~46

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

NameTypeReqDescription
domain_idstringyesThe domain ID to inspect

No output schema declared.

No examples provided.

indexing_status ~48

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 shows your current plan and limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_domains ~30

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_urls ~82

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

NameTypeReqDescription
domain_idstringyesThe domain ID
limitnumberURLs per page (default: 50, max: 500)
pagenumberPage number (default: 1)

No output schema declared.

No examples provided.

push_to_index ~61

One-shot command: scan the sitemap for new URLs, then immediately submit everything to Google and IndexNow. Use this after deploying a website or publishing new content. This is the most common operation.

NameTypeReqDescription
domain_idstringyesThe domain ID to push

No output schema declared.

No examples provided.

remove_domain ~38

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

NameTypeReqDescription
domain_idstringyesThe domain ID to remove

No output schema declared.

No examples provided.

scan_sitemap ~72

Scan a domain's sitemap to discover new URLs. This fetches and parses the sitemap XML (including gzipped and sitemap index files) and adds any new URLs to the domain. Run this after deploying new content.

NameTypeReqDescription
domain_idstringyesThe domain ID to scan (use list_domains to find it)

No output schema declared.

No examples provided.

submission_history ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

submit_urls ~71

Submit pending URLs to Google (via Indexing API, 200/day limit) and to Bing/Yandex/10+ search engines (via IndexNow, unlimited). Only submits URLs that haven't been submitted yet or that need resubmission.

NameTypeReqDescription
domain_idstringyesThe domain ID to submit URLs for

No output schema declared.

No examples provided.