IIS Rescue
com.iisrescue/iis-rescue · 1.1.1
Legacy IIS, classic ASP and SQL Server migration: paths, FAQ, end-of-support dates, fit assessment.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://iisrescue.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 8 tools.
- Protocol
- 2025-06-18
- Calls itself
- iis-rescue 1.1.1
- Handshake time
- 542 ms
- HTTP status
- 200
The tools it lists (8, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_offeringThe public offering of IIS Rescue: the three migration paths, the promises made on every project, the pricing model, and who the service is for.
get_faqPublished questions and answers about legacy IIS, classic ASP and SQL Server website migration, reproduced verbatim from the website.
get_eol_factsMicrosoft end-of-support dates for Windows Server and SQL Server versions, with the source URL for each, plus the Extended Security Updates cutoff.
get_migration_pathsThe three routes off a legacy IIS server — Rehost, Rebuild, Replace — each with what it involves and the situation it best fits.
get_contactHow 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.
get_partner_channelHow 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 I
get_pathfinder_questionsThe 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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.iisrescue/iis-rescue, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 16 days ago. The registry entry · iisrescue.com