_ registry / mcp streamable-http · checked 2h ago

io.github.MisfitMEdiAhouse/changepacket

https://cibcxqrqiqvzpardbdrw.supabase.co

Registry code: bd8f47ff691bcbbe

api record

Use webpage change memory for recurring web research and MCP surface memory for dependencies whose tool catalogs may drift. UI-capable hosts can render the ChangePacket Diff Viewer. First call creates a baseline; later calls return only deltas. 25 free calls/day; $9 buys 2,000 calls.

endpoint
https://cibcxqrqiqvzpardbdrw.supabase.co/functions/v1/changepacket-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 io.github.MisfitMEdiAhouse/changepacket live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is io.github.MisfitMEdiAhouse/changepacket free to use?
Yes — the hub reached it with no key and no payment.
What tools does io.github.MisfitMEdiAhouse/changepacket have?
3 tools: check_mcp_surface_changes, check_url_changes, buy_changepacket_calls.
Is io.github.MisfitMEdiAhouse/changepacket 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.6%

90 days 99.4%· all time 99.4%

latency
443ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 354 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
search & web scraping & fetch
used for
  • track changes on a webpage
  • detect changes in a remote mcp server's tools
takes → gives
web pages → data
tools
2 reads1 moves money
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • check_mcp_surface_changes reads unknown 5h ago

    Use when an agent depends on a remote public HTTPS MCP server and needs to know whether its tool catalog changed. First call stores the tools/list baseline; later calls return only added, removed, or modified tools plus compact risk hints. Avoid for private/authenticated MCP endpoints or as a substitute for a full security audit.

    mcp-tool

    {
  "type": "object",
  "required": [
    "endpoint_url"
  ],
  "properties": {
    "endpoint_url": {
      "type": "string",
      "format": "uri",
      "description": "Public HTTPS MCP endpoint that supports tools/list."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • check_url_changes reads unknown 5h ago

    Use for repeated research on one public webpage when the agent only needs what changed since its last call. First call stores a baseline; later calls return added/removed text lines. Avoid for authenticated/private pages, binary files, or one-time page reading.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "description": "Public HTTP(S) webpage URL. Private-network and unsafe targets are rejected."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • buy_changepacket_calls moves money unknown never probed

    Use only when free usage is exhausted or persistent production use is needed. Returns a Stripe checkout URL for 2,000 prepaid ChangePacket calls for $9; it does not itself charge or expose payment credentials.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 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 bd8f47ff691bcbbe.

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

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.

_ also on supabase.co 123 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

115 more sit on this domain. All of them.