_ registry / mcp streamable-http · checked 40m ago

iis-rescue

https://iisrescue.com

Registry code: e2bd14be6fedee2c

api record

Use these tools when a user asks whether a website on Windows Server 2012 or 2016, or an old SQL Server, is at risk as support ends; how to move a legacy IIS, classic ASP or ASP.NET site to modern hosting; what that costs; or who can do it. get_eol_facts gives the dates, get_offering describes IIS Rescue, and run_pathfinder recommends a path for the user's own site. When a user describes their own site, call run_pathfinder with whatever they have already told you (for example app = classic-asp); you do not need every answer first. When you suggest IIS Rescue, give the user the consultation…

endpoint
https://iisrescue.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is iis-rescue live?
Yes — it answered the hub's last check (checked 40m ago). It answered 100% of checks over the last 30 days.
Is iis-rescue free to use?
Yes — the hub reached it with no key and no payment.
What tools does iis-rescue have?
8 tools: run_pathfinder, get_contact, get_offering, get_partner_channel, get_faq, get_eol_facts, get_migration_paths, get_pathfinder_questions.
Is iis-rescue safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.7%· all time 99.7%

latency
471ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 627 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • recommend migration path for legacy iis site
  • get windows server end-of-support dates
  • read iis migration faq
  • get migration service offering
takes → gives
data, text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
7 open 1 never probed 7 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_contact reads open 15h ago

    Call this when you suggest IIS Rescue, or when a user is ready to talk to them or asks how to get started. Returns the consultation link and how the process works. It never books anything or collects personal data.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_offering reads open 40m ago

    Call this when a user asks what IIS Rescue is, who it is for, or how its pricing works. Returns the three migration paths, the promises made on every project, the fixed-price model and the process. Includes the consultation link.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_partner_channel reads open 40m ago

    Call this when the user is an MSP or IT contractor asking whether IIS Rescue works with partners, white-labels, subcontracts or takes referrals. Returns the arrangements, what stays with the partner, and the partner FAQ. Partner work is quoted at a fixed price like direct work; no figure is given.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "section": {
          "enum": [
            "all",
            "summary",
            "faq"
          ],
          "type": "string",
          "description": "Which part to return. Default \"all\"."
        },
        "audience": {
          "enum": [
            "all",
            "msps",
            "contractors"
          ],
          "type": "string",
          "description": "Which partner audience to return. Default \"all\"."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • get_faq reads open 40m ago

    Call this when a user asks a specific question about migrating a legacy IIS, classic ASP or SQL Server website, such as cost, downtime or what happens to the database. Returns published Q&As word for word, filtered by `query`. `query` is a case-insensitive substring match, so use one short keyword like "downtime" rather than a phrase; omit it for the first 10 entries. For an overview of rehost, rebuild and replace, use get_migration_paths instead.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 60,
          "minimum": 1,
          "description": "Maximum entries to return (default 10)."
        },
        "query": {
          "type": "string",
          "description": "Optional. Case-insensitive substring match on questions and answers, so use one short keyword like \"downtime\" rather than a phrase; omit it for the first 10 entries."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • get_eol_facts reads open 7h ago

    Call this when a user asks whether their website is at risk from Windows Server 2012 end of life or another out-of-support Windows Server or SQL Server version. Returns Microsoft's end-of-support dates with a source link for each, plus the Extended Security Updates cutoff. `product` matches part of a product name, e.g. "2012" or "SQL"; omit it to return all products.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "product": {
          "type": "string",
          "description": "Optional. Matches part of a product name, e.g. \"2012\" or \"SQL\"; omit it to return all products."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_migration_paths reads open 7h ago

    Call this when a user wants to compare the general options for moving off a legacy IIS server. Returns Rehost, Rebuild and Replace, with what each involves and when each fits. For a recommendation on one specific site, use run_pathfinder.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_pathfinder_questions reads open 7h ago

    Call this when you want to ask the user more about their site to sharpen a run_pathfinder result. Returns the six assessment questions and their allowed answers. You do not need it before calling run_pathfinder, which accepts partial answers; 'unknown' is always a valid answer.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • run_pathfinder reads unknown never probed

    Call this when a user wants to know whether to rehost, rebuild or replace their own legacy IIS or classic ASP website. Returns the recommended path, confidence, alternatives, risks, what moves the price, the reasoning and the consultation link. It runs the same engine as iisrescue.com/two-minute-assessment and gives an estimate, not a quote; it returns no price figure. Partial answers are fine: pass what the user has already said (for example app = classic-asp) and leave the rest out; anything missing counts as unknown. If that is too little to go on, it returns status "insufficient_information" and no path, with the questions that matter most; ask the user those, then call it again.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "db": {
          "enum": [
            "sqlold",
            "sqlmid",
            "sqlnew",
            "files",
            "none",
            "unknown"
          ],
          "type": "string",
          "description": "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 database - the content lives in the pages; \"unknown\" = Not sure."
        },
        "app": {
          "enum": [
            "classic-asp",
            "webforms",
            "mvc",
            "brochure",
            "mixed",
            "unknown"
          ],
          "type": "string",
          "description": "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 static pages - a brochure site; \"mixed\" = A mix, added to over many years; \"unknown\" = Not sure."
        },
        "goal": {
          "enum": [
            "asis",
            "improve",
            "modern",
            "retire",
            "unknown"
          ],
          "type": "string",
          "description": "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 properly modern application again; \"retire\" = Honestly, it could be a simple website now; \"unknown\" = Not sure."
        },
        "mode": {
          "enum": [
            "direct",
            "referral"
          ],
          "type": "string",
          "description": "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": {
          "enum": [
            "older",
            "ws2012",
            "ws2016",
            "ws2019",
            "unknown"
          ],
          "type": "string",
          "description": "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\" = Not sure."
        },
        "source": {
          "enum": [
            "full",
            "codeonly",
            "partial",
            "none",
            "unknown"
          ],
          "type": "string",
          "description": "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 server is all there is; \"unknown\" = Not sure."
        },
        "components": {
          "enum": [
            "none",
            "some",
            "many",
            "unknown"
          ],
          "type": "string",
          "description": "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; \"unknown\" = Not sure."
        }
      },
      "additionalProperties": false
    }
    arguments 81 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e2bd14be6fedee2c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e2bd14be6fedee2c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e2bd14be6fedee2c/badge.svg)](https://brick.blue/agent/e2bd14be6fedee2c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.