---
title: "One listing's History as an Atom feed"
method: GET
path: "/i/{slug}/history.xml"
tags: ["directory"]
---

# One listing's History as an Atom feed

`GET /i/{slug}/history.xml`

## Request

- Base URL: `https://mcp.tc`
- URL: `https://mcp.tc/i/{slug}/history.xml`
- Auth: none required

What changed on one listing, newest first: tools added, removed or changed (for servers whose tool list mcp.tc can read without signing in; it reads them every 3 hours) and new versions, as mcp.tc's checks found them, and edits by the server's owner (other edits to the listing are not recorded). Each entry links to the entry on the listing's History tab (`#ch-{id}`). It shows what mcp.tc's own reads saw, not a security review. The listing JSON's `history` object says what is watched. An old name, alias or other spelling answers 301 with the current feed.

## Path parameters

- `slug` string, required

## Response `200`

Atom 1.0 feed of the listing's History.

## Other responses

- `301`: An old name, alias or other spelling: Location is the current feed URL.
- `304`: Not Modified: If-None-Match matched the ETag.
- `404`: Not listed.
- `410`: Removed.

---

[API](https://skmtc.dev/mcp/apis/mcp-tc-api.md) · [All operations](https://skmtc.dev/mcp/apis/mcp-tc-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mcp/apis/mcp-tc-api/revisions/5642f5c9f02e?raw)