ChangePacket

What the ChangePacket MCP server does

The ChangePacket MCP server is described as web-change memory for AI agents. Its core behavior is incremental comparison: an agent stores a baseline representation of web content, then later requests receive only the lines that differ from that baseline. This can help an agent track updates without repeatedly processing unchanged material.

The available description does not identify a particular website, crawler, database schema, or external service beyond the supplied Supabase function URL. It also does not list named MCP tools or define the format of a baseline, the returned changed lines, or the rules used to compare content.

How it works

The intended workflow has two stages. First, the agent saves an initial baseline. After that, the agent makes later calls against the stored state. Those calls return the lines that changed since the baseline rather than returning the entire source again.

This design fits recurring monitoring tasks, where an agent needs to notice edits to web content while reducing repeated context. The listing does not state whether baselines are scoped by URL, user, session, or another identifier, so callers should not assume how multiple tracked sources are separated.

Setup and configuration

The provided source is a Supabase-hosted function endpoint:

https://cibcxqrqiqvzpardbdrw.supabase.co/functions/v1/deltafeed

No README or configuration reference is available. As a result, the required installation method, MCP transport, request shape, authentication requirements, baseline identifiers, and optional settings cannot be confirmed from the supplied material. Before integrating the ChangePacket MCP server, inspect the endpoint or its accompanying documentation to determine how an MCP client should connect and which arguments its operations accept.

No environment variables are documented for this listing.

Tools and capabilities

The documented capability is limited to the following workflow:

• Store a baseline of web content.
• Compare later content with that stored baseline.
• Return only changed lines to the requesting agent.

The source does not provide tool names, input schemas, output schemas, error behavior, deletion or reset operations, scheduling, authentication details, or support for a particular web platform. Those details should be verified before building an automated workflow around them.

Limitations and notes

The ChangePacket MCP server’s description establishes the baseline-and-delta behavior, but it does not establish broader database features despite the current category label. The category should therefore not be treated as evidence that the server exposes general database queries or mutations.

Client compatibility is also undocumented. No specific MCP clients are named, and the available material does not confirm whether the Supabase endpoint uses a client-compatible MCP transport. Treat the endpoint, protocol, and access requirements as integration details that require confirmation from the service owner.