io.github.joepangallo/mcp-server-indexforge
NPM · MCP-SERVER-INDEXFORGE · SCANNED SEP 20
Submit URLs to Google and Bing for indexing, scan sitemaps, check index status.
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. 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 202 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability85
- 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 Management93
- Stability observed for 28 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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_domain" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.joepangallo/mcp-server-indexforge server?
io.github.joepangallo/mcp-server-indexforge runs locally as an npm package, launched with npx -y mcp-server-indexforge. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-indexforge
claude mcp add joepangallo-mcp-server-indexforge -- npx -y mcp-server-indexforge
{
"mcpServers": {
"joepangallo-mcp-server-indexforge": {
"command": "npx",
"args": [
"-y",
"mcp-server-indexforge"
]
}
}
} {
"servers": {
"joepangallo-mcp-server-indexforge": {
"command": "npx",
"args": [
"-y",
"mcp-server-indexforge"
]
}
}
} codex mcp add joepangallo-mcp-server-indexforge -- npx -y mcp-server-indexforge
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joepangallo-mcp-server-indexforge": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-server-indexforge"
],
"enabled": true
}
}
} openclaw mcp add joepangallo-mcp-server-indexforge --command npx --arg -y --arg mcp-server-indexforge
mcp_servers:
joepangallo-mcp-server-indexforge:
command: "npx"
args: ["-y", "mcp-server-indexforge"] {
"McpServers": {
"joepangallo-mcp-server-indexforge": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-server-indexforge"
]
}
}
} assistant mcp add joepangallo-mcp-server-indexforge -t stdio -c npx -a -y mcp-server-indexforge
{
"mcpServers": {
"joepangallo-mcp-server-indexforge": {
"command": "npx",
"args": [
"-y",
"mcp-server-indexforge"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/mcp-server-indexforge@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to add (e.g. 'example.com') |
| sitemap_url | string | – | Custom 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The 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).
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The domain ID |
| limit | number | – | URLs per page (default: 50, max: 500) |
| page | number | – | Page 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain_id | string | yes | The domain ID to submit URLs for |
No output schema declared.
No examples provided.
What is the io.github.joepangallo/mcp-server-indexforge server?
io.github.joepangallo/mcp-server-indexforge is listed in the public MCP registry as io.github.joepangallo/mcp-server-indexforge. Submit URLs to Google and Bing for indexing, scan sitemaps, check index status. This page covers its npm package (mcp-server-indexforge).
Is the io.github.joepangallo/mcp-server-indexforge server safe to use?
io.github.joepangallo/mcp-server-indexforge scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.joepangallo/mcp-server-indexforge server expose?
io.github.joepangallo/mcp-server-indexforge exposes 11 tools: indexing_status, list_domains, add_domain, remove_domain, scan_sitemap, and 6 more. Their descriptions and schemas cost roughly 616 tokens of context every time the server is loaded.
Is the io.github.joepangallo/mcp-server-indexforge server still maintained?
io.github.joepangallo/mcp-server-indexforge is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.joepangallo/mcp-server-indexforge server under?
io.github.joepangallo/mcp-server-indexforge declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.