Web Resurrect MCP Server

@web-resurrect/mcp npm v1.5.0

Published by @web-resurrect — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for the Web Resurrect API — resurrect expired domains via AI assistants

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 34

Each tool and what it can reach — statically extracted from the published source.

  • create_projectingests untrusted input
  • get_pageingests untrusted input
  • get_page_contentingests untrusted input
  • get_projectingests untrusted input
  • get_project_overviewingests untrusted input
  • rewrite_bulkingests untrusted input
  • rewrite_pageingests untrusted input
  • scrape_bulkingests untrusted input
  • scrape_pageingests untrusted input
  • wait_for_jobingests untrusted input
Show 24 more tools ↓
  • cancel_jobno sensitive capability
  • categorize_pagesno sensitive capability
  • delete_projectno sensitive capability
  • enrich_projectno sensitive capability
  • export_redirectsno sensitive capability
  • generate_imageno sensitive capability
  • generate_image_bulkno sensitive capability
  • get_creditsno sensitive capability
  • get_jobno sensitive capability
  • list_jobsno sensitive capability
  • list_pagesno sensitive capability
  • list_projectsno sensitive capability
  • push_redirects_addno sensitive capability
  • push_redirects_replace_allno sensitive capability
  • update_pageno sensitive capability
  • wordpress_authorsno sensitive capability
  • wordpress_categoriesno sensitive capability
  • wordpress_configureno sensitive capability
  • wordpress_get_mappingno sensitive capability
  • wordpress_plugin_checkno sensitive capability
  • wordpress_publishno sensitive capability
  • wordpress_publish_bulkno sensitive capability
  • wordpress_set_mappingno sensitive capability
  • wordpress_validateno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.0 latest A 95/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/web-resurrect-mcp/badge.svg)](https://mcptrustchecker.com/registry/web-resurrect-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/web-resurrect-mcp"><img src="https://mcptrustchecker.com/registry/web-resurrect-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/web-resurrect-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @web-resurrect/mcp --online

Use the free API → How scoring works

More in Web, Search & Scraping