IIS Rescue
REMOTE · IISRESCUE.COM · SCANNED SEP 28
Legacy IIS, classic ASP and SQL Server migration: paths, FAQ, end-of-support dates, fit assessment.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1270 tokens (~158/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the IIS Rescue MCP server?
IIS Rescue is a hosted endpoint at https://iisrescue.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · iisrescue.com
claude mcp add --transport http com-iisrescue-iis-rescue 'https://iisrescue.com/mcp'
{
"mcpServers": {
"com-iisrescue-iis-rescue": {
"url": "https://iisrescue.com/mcp"
}
}
} {
"servers": {
"com-iisrescue-iis-rescue": {
"type": "http",
"url": "https://iisrescue.com/mcp"
}
}
} [mcp_servers.com-iisrescue-iis-rescue] url = "https://iisrescue.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-iisrescue-iis-rescue": {
"type": "remote",
"url": "https://iisrescue.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-iisrescue-iis-rescue --url 'https://iisrescue.com/mcp' --transport streamable-http
mcp_servers:
com-iisrescue-iis-rescue:
url: "https://iisrescue.com/mcp" {
"McpServers": {
"com-iisrescue-iis-rescue": {
"Transport": "http",
"Url": "https://iisrescue.com/mcp"
}
}
} assistant mcp add com-iisrescue-iis-rescue -t streamable-http -u 'https://iisrescue.com/mcp'
{
"mcpServers": {
"com-iisrescue-iis-rescue": {
"type": "http",
"url": "https://iisrescue.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 65
First indexed and scored.
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 28 Sept 2026 · Probed https://iisrescue.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=iisrescue.com | CN=YE2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6bbe24c0db42718912c07480e424de8af0e |
| SANs: *.iisrescue.com, iisrescue.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of iisrescue.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| iisrescue.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://iisrescue.com/mcp | Verified | 200 | |
| http (plaintext) | http://iisrescue.com/mcp | HTTPS enforced | 301 | https://iisrescue.com/mcp |
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 →
get_contact ~41
How to start an engagement with IIS Rescue: the consultation URL and how the process works. Returns a pointer only — it never books anything or collects any personal data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_eol_facts ~58
Microsoft end-of-support dates for Windows Server and SQL Server versions, with the source URL for each, plus the Extended Security Updates cutoff.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | – | Optional substring, e.g. "2012" or "SQL". |
No output schema declared.
No examples provided.
get_faq ~64
Published questions and answers about legacy IIS, classic ASP and SQL Server website migration, reproduced verbatim from the website.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum entries to return (default 10). |
| query | string | – | Optional case-insensitive substring to filter questions and answers. |
No output schema declared.
No examples provided.
get_migration_paths ~39
The three routes off a legacy IIS server — Rehost, Rebuild, Replace — each with what it involves and the situation it best fits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_offering ~39
The public offering of IIS Rescue: the three migration paths, the promises made on every project, the pricing model, and who the service is for.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_partner_channel ~163
How IIS Rescue works with MSPs and independent IT contractors: MSPs bringing it in for legacy IIS, classic ASP and SQL Server migrations they would rather not own, and contractors subcontracting a migration or referring it. Covers the arrangements, what stays with the partner — the client, the brand, anything outside the migration scope — and the published FAQ for each audience. Carries no price: a partner migration is quoted at a fixed price exactly like a direct one. Use this for questions about white-label delivery, subcontracting or referring a legacy Windows Server migration, or whether IIS Rescue works with MSPs or contractors.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Which partner audience to return. Default "all". |
| section | string | – | Which part to return. Default "all". |
No output schema declared.
No examples provided.
get_pathfinder_questions ~65
The questions the IIS Rescue two-minute assessment asks in order to recommend a migration path, with the allowed answers for each. Ask these of the user, then pass the answers to run_pathfinder. "unknown" is a valid answer to every question and never breaks the result.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_pathfinder ~663
Recommend a migration path — Rehost, Rebuild or Replace — for a specific legacy IIS website, from answers to the two-minute assessment questions. Returns the recommendation, a confidence level, the alternatives and when they would apply, what pushes the price up or down, the specific risks these answers imply, and the reasoning behind the call. This is the same deterministic engine, over the same data, that iisrescue.com/two-minute-assessment runs for a human visitor: identical answers give an identical result. It is an estimate and not a quote, and it returns no price figure — IIS Rescue publishes no rate card.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | What is the website built with? "classic-asp" = Classic ASP — .asp pages, VBScript; "webforms" = ASP.NET Web Forms — .aspx pages; "mvc" = ASP.NET MVC, or a newer .NET application; "brochure" = Mostly… |
| components | string | – | Are there COM objects, custom IIS modules, ISAPI filters or scheduled tasks? "none" = No — it is a plain site; "some" = One or two we know about; "many" = Several, or nobody is sure what they all do;… |
| db | string | – | What holds the data? "sqlold" = SQL Server 2012 or older; "sqlmid" = SQL Server 2014 or 2016; "sqlnew" = SQL Server 2017 or newer; "files" = Access, flat files, or something homegrown; "none" = No da… |
| goal | string | – | What do you need from the site going forward? "asis" = Just get it off the dying server — it does its job; "improve" = Keep it working, but we will want to change things; "modern" = It needs to be a… |
| mode | string | – | Voice of the result. "direct" addresses the site owner; "referral" returns the same finding phrased as third-person talking points for an MSP or IT provider assessing a client site. Default "direct". |
| server | string | – | What is it running on? "older" = Something older than Windows Server 2012; "ws2012" = Windows Server 2012 or 2012 R2; "ws2016" = Windows Server 2016; "ws2019" = Windows Server 2019 or newer; "unknown… |
| source | string | – | Do you have the source code? "full" = Yes — source code and some documentation; "codeonly" = Source code, but no documentation; "partial" = Some of it, we think; "none" = No — whatever is on the serv… |
No output schema declared.
No examples provided.
What is the IIS Rescue MCP server?
IIS Rescue is an MCP server listed in the public MCP registry as com.iisrescue/iis-rescue. Legacy IIS, classic ASP and SQL Server migration: paths, FAQ, end-of-support dates, fit assessment. This page covers its hosted endpoint (https://iisrescue.com/mcp).
Is the IIS Rescue MCP server safe to use?
IIS Rescue scores 68 out of 100 on VerifyMCP. 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 IIS Rescue MCP server expose?
IIS Rescue exposes 8 tools: get_offering, get_faq, get_eol_facts, get_migration_paths, get_contact, and 3 more. Their descriptions and schemas cost roughly 1,132 tokens of context every time the server is loaded.
Does the IIS Rescue MCP server require authentication?
No. We connected to IIS Rescue without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the IIS Rescue MCP server still maintained?
IIS Rescue is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.