_ registry / mcp http-sse · checked 1h ago

eolwatch

https://eolwatch.dev

Registry code: 6d3f62adfbfc38d7

api record

EOL Watch tracks cloud service retirements, end of support dates and infrastructure as code breaking changes for Azure, AWS, GCP, and OCI, and every date in it comes from the source linked with it. A value the source does not state is null in the data and reads "Not stated by vendor" or "Not stated in the source" in text, and an item without a date reads "Date not announced": never estimate such a value. An answer that counts days says for which UTC day it counted (as_of), and a date whose precision is month, quarter or year is a period, not a day.

endpoint
https://eolwatch.dev/mcp
protocol
http-sse ·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 eolwatch live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is eolwatch free to use?
Yes — the hub reached it with no key and no payment.
What tools does eolwatch have?
6 tools: get_item, list_services, get_provider_changes, search_items, list_providers, recent_changes.
Is eolwatch 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
100%

90 days 100%· all time 100%

latency
399ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 6 tools
3 open 3 never probed 3 of 6 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.

  • search_items open 1h ago

    Lists published items of EOL Watch: retirements, end of support dates and breaking changes. Filter by cloud, kind of change, category, service, search text and effective date. Without status it lists upcoming items only, soonest first. To list ended items, breaking changes in effect or every item, send status ended, in_effect or all. Use it for questions such as what retires in the next 90 days or what is due for one service. It returns one page of compact rows as a Markdown table and as structured data, with the UTC day the countdowns were counted for (as_of). Call get_item for the full text of one item. This tool does not check an estate: that check runs in the reader's browser only.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 100,
          "description": "Search text of at most 100 characters. Every word must occur in the title, the summary, the service, the slug or an affected version."
        },
        "to": {
          "type": "string",
          "format": "date",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Latest effective_date to include (YYYY-MM-DD). An item without a date never matches. A month, quarter or year is compared by its first day; use within_days for what is due or what ended."
        },
        "dir": {
          "enum": [
            "asc",
            "desc"
          ],
          "type": "string",
          "description": "asc (the default) or desc. The added order ignores it."
        },
        "from": {
          "type": "string",
          "format": "date",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Earliest effective_date to include (YYYY-MM-DD). An item without a date never matches. A month, quarter or year is compared by its first day; use within_days for what is due or what ended."
        },
        "sort": {
          "enum": [
            "date",
            "added",
            "service"
          ],
          "type": "string",
          "description": "date (the default): by effective_date, items without a date last; a list of ended items or of changes in effect (status=ended, status=in_effect) is ordered by the last day of each effective period. added: newest first by created_at, then by the later announcement date (items without one last), then by the soonest effective date, then by title. service: by service name."
        },
        "type": {
          "type": "array",
          "items": {
            "enum": [
              "retirement",
              "end_of_support",
              "breaking_change"
            ],
            "type": "string"
          },
          "description": "Kinds of change to include. Leave it out for every kind."
        },
        "cloud": {
          "type": "array",
          "items": {
            "enum": [
              "azure",
              "aws",
              "gcp",
              "oci",
              "multi"
            ],
            "type": "string"
          },
          "description": "Clouds to include. Leave it out for every cloud."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Most items in one answer: 1 to 100, 25 by default."
        },
        "offset": {
          "type": "integer",
          "maximum": 100000,
          "minimum": 0,
          "description": "Number of matching items to skip. Send the next_offset of an answer to get the next page."
        },
        "status": {
          "enum": [
            "upcoming",
            "ended",
            "in_effect",
            "all"
          ],
          "type": "string",
          "description": "upcoming (the default): items whose effective period is not over, including items without a date. ended: retirements and end of support dates whose whole period is over. in_effect: breaking changes whose date has passed (a breaking change takes effect, it does not end, so it is never in ended). all: every item."
        },
        "service": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 80,
          "description": "Service slug of at most 80 characters, as in the service_slug field. Two clouds can use the same slug, so send cloud with it."
        },
        "category": {
          "enum": [
            "services",
            "features",
            "kubernetes",
            "runtimes",
            "databases",
            "compute-skus",
            "os-images",
            "apis-sdks",
            "iac",
            "other"
          ],
          "type": "string",
          "description": "Category group, as in the address of a category page."
        },
        "within_days": {
          "type": "integer",
          "maximum": 3650,
          "minimum": 1,
          "description": "Only items at most this many days from the as_of day (1 to 3650). With status upcoming: items due in the next N days, including an item whose month, quarter or year has started and is not over. With status ended or in_effect: items that ended or took effect in the last N days. With status all: all of these. Cannot be combined with from or to."
        }
      },
      "additionalProperties": false
    }
    arguments 117 lines
  • list_providers open 1h ago

    Lists the infrastructure as code providers, tools and modules whose releases are read for breaking changes, each with its newest tracked release. Use it to find the key that get_provider_changes takes.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • recent_changes open 1h ago

    Returns one page of the changelog of EOL Watch, newest first: items added, effective dates changed, items updated and items withdrawn. Use it to see what changed since you last read the data.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 10000,
          "minimum": 1,
          "description": "Page of the changelog, from 1. One page holds 50 changes, and a page past the end is the last page."
        },
        "cloud": {
          "enum": [
            "azure",
            "aws",
            "gcp",
            "oci",
            "multi"
          ],
          "type": "string",
          "description": "Only changes to items of this cloud."
        },
        "change": {
          "enum": [
            "added",
            "date_changed",
            "updated",
            "withdrawn"
          ],
          "type": "string",
          "description": "Only this kind of change: added, date_changed, updated or withdrawn."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • get_item unknown never probed

    Returns one published item in full: its dates, summary, impact, migration path, replacement, affected versions and sources, as Markdown and as structured data. Use it with the slug of a row that search_items returned; the address of the item page or its short address works too. An unknown slug is answered as an error, and so is a withdrawn item, with the notice that it was withdrawn.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "Slug of the item, as in the slug field of a row. The address of the item page, of its Markdown or JSON form, or its short address is accepted too."
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • list_services unknown never probed

    Lists every service that has a published item, with its number of items, how many of them are upcoming and the date of the next one. Use it to find the slug of a service before you filter search_items by service, or to see what is tracked for one cloud.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "q": {
          "type": "string",
          "maxLength": 100,
          "description": "Search text of at most 100 characters. Every word must occur in the name or the slug of the service."
        },
        "cloud": {
          "enum": [
            "azure",
            "aws",
            "gcp",
            "oci",
            "multi"
          ],
          "type": "string",
          "description": "Only the services of this cloud."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • get_provider_changes unknown never probed

    Returns what the page of one provider, tool or module shows: the range of releases that is tracked, the summary sentence, the notices and the breaking changes of each release that lists any. Send from with the version in use to get only the releases above it. Read the notices before you call a range clear: they say which releases were not tracked or whose release notes were not read.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "provider"
      ],
      "properties": {
        "from": {
          "type": "string",
          "maxLength": 64,
          "description": "The version in use, or a version constraint, of at most 64 characters. Only releases newer than that version are in the answer. For a constraint, that version is the lowest one the constraint allows. Leave it out for every tracked release whose release notes were read and list a breaking change."
        },
        "provider": {
          "enum": [
            "azurerm",
            "azapi",
            "aws",
            "oci",
            "bicep",
            "avm-res-network-virtualnetwork",
            "avm-res-storage-storageaccount",
            "avm-res-network-networksecuritygroup",
            "avm-res-compute-virtualmachine",
            "avm-res-resources-resourcegroup",
            "avm-res-managedidentity-userassignedidentity",
            "avm-res-network-privatednszone",
            "avm-res-operationalinsights-workspace",
            "avm-res-network-routetable",
            "avm-res-network-natgateway",
            "avm-res-network-publicipaddress",
            "avm-res-cognitiveservices-account",
            "avm-res-network-firewallpolicy",
            "avm-res-containerregistry-registry",
            "avm-res-containerservice-managedcluster",
            "avm-res-network-privateendpoint",
            "avm-res-web-site",
            "avm-res-network-loadbalancer",
            "avm-res-dbforpostgresql-flexibleserver",
            "avm-res-network-bastionhost"
          ],
          "type": "string",
          "description": "Key of the provider, tool or module, as in the key field of list_providers."
        }
      },
      "additionalProperties": false
    }
    arguments 46 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 6d3f62adfbfc38d7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6d3f62adfbfc38d7/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/6d3f62adfbfc38d7/badge.svg)](https://brick.blue/agent/6d3f62adfbfc38d7?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.