_ registry / mcp + a2a streamable-http · checked 1h ago

upgrade-brief

https://upgrade-brief.shopttyass-85f.workers.dev

Registry code: 3d04f59f8a87f809

api record

Breaking changes and changelogs between two versions of npm and PyPI packages, from real changelogs and GitHub releases. Free: npm_versions, pypi_versions. Paid per call in USDC via x402 (Base or Solana): an unpaid call returns x402 PaymentRequired; an x402-capable MCP client (e.g. @x402/mcp) pays and retries. Errors are not charged. HTTP equivalents: https://upgrade-brief.shopttyass-85f.workers.dev/openapi.json

endpoint
https://upgrade-brief.shopttyass-85f.workers.dev/mcp
door code
7325c6511bb54b52
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 upgrade-brief live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is upgrade-brief free to use?
Yes — the hub reached it with no key and no payment.
What tools does upgrade-brief have?
7 tools: npm_versions, pypi_breaking_changes, pypi_changelog, pypi_versions, dependency_upgrade_plan, npm_breaking_changes, npm_changelog.
Is upgrade-brief 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
531ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 1 other origin: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
3

distinct

settlements
20

last 2026-10-22

received on chain
0.165 USDC

concentrated, shared-payto

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 7 tools
7 never probed 0 of 7 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.

  • npm_versions unknown never probed

    Free: published versions of an npm package (newest first) with publish dates, bump type and deprecations, to pick valid from/to values.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package"
  ],
  "properties": {
    "from": {
      "type": "string",
      "maxLength": 64,
      "description": "Optional: list only versions after this one"
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max versions returned (default 50)"
    },
    "package": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "npm package name, e.g. 'react', 'next', '@types/node'"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • pypi_breaking_changes unknown never probed

    PyPI breaking changes between two versions of a Python package, from its CHANGELOG/HISTORY/CHANGES file and GitHub releases: breaking items per version, Requires-Python and dependency changes, yanked versions, migration guide links and a verdict. Paid: $0.005 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package",
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 64,
      "description": "Target version (exact or prefix). Default: latest stable"
    },
    "from": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21')"
    },
    "package": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "PyPI project name, e.g. 'pydantic', 'django', 'flask'"
    },
    "prereleases": {
      "type": "boolean",
      "description": "Include alpha/beta/rc versions in the range"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • pypi_changelog unknown never probed

    PyPI changelog between two versions of a Python package: full release notes per version (newest first) with dates, bump type, yanked flags, extracted breaking changes and Requires-Python / dependency changes. Paid: $0.01 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package",
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 64,
      "description": "Target version (exact or prefix). Default: latest stable"
    },
    "from": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21')"
    },
    "package": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "PyPI project name, e.g. 'pydantic', 'django', 'flask'"
    },
    "maxVersions": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Newest N versions to return notes for (default 30)"
    },
    "prereleases": {
      "type": "boolean",
      "description": "Include alpha/beta/rc versions in the range"
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
  • pypi_versions unknown never probed

    Free: published versions of a PyPI project (newest first, PEP 440 order) with publish dates and bump type.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package"
  ],
  "properties": {
    "from": {
      "type": "string",
      "maxLength": 64,
      "description": "Optional: list only versions after this one"
    },
    "limit": {
      "type": "integer",
      "maximum": 200,
      "minimum": 1,
      "description": "Max versions returned (default 50)"
    },
    "package": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "PyPI project name, e.g. 'pydantic', 'django', 'flask'"
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • dependency_upgrade_plan unknown 1h ago

    Dependency upgrade plan for up to 5 npm or PyPI packages: per package the breaking changes to the target version, major bumps, engine/Python and peer dependency changes, migration guides and a risk score, ordered by risk, plus peer requirements between the listed packages. Paid: $0.02 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "packages"
  ],
  "properties": {
    "packages": {
      "type": "string",
      "maxLength": 600,
      "minLength": 1,
      "description": "Comma-separated name@from[:to], up to 5, e.g. '[email protected]:19,[email protected]:19,[email protected]:15'"
    },
    "ecosystem": {
      "enum": [
        "npm",
        "pypi"
      ],
      "type": "string",
      "description": "Registry of all listed packages (default npm)"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • npm_breaking_changes unknown 1h ago

    npm breaking changes between two versions of a package, read from its real CHANGELOG and GitHub release notes: documented breaking items per version, major bumps, Node.js engine / ESM-CJS / peer dependency changes, migration guide links and a verdict. Paid: $0.005 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package",
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 64,
      "description": "Target version (exact or prefix). Default: latest stable"
    },
    "from": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21')"
    },
    "package": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "npm package name, e.g. 'react', 'next', '@types/node'"
    },
    "prereleases": {
      "type": "boolean",
      "description": "Include alpha/beta/rc versions in the range"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • npm_changelog unknown 1h ago

    npm changelog between two versions: full release notes of every version in the range (newest first), with dates, bump type, deprecations, extracted breaking changes and package.json changes. Paid: $0.01 USDC per call via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "package",
    "from"
  ],
  "properties": {
    "to": {
      "type": "string",
      "maxLength": 64,
      "description": "Target version (exact or prefix). Default: latest stable"
    },
    "from": {
      "type": "string",
      "maxLength": 64,
      "minLength": 1,
      "description": "Version you are on now: exact ('18.3.1') or a major/minor prefix ('18', '4.21')"
    },
    "package": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "npm package name, e.g. 'react', 'next', '@types/node'"
    },
    "maxVersions": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Newest N versions to return notes for (default 30)"
    },
    "prereleases": {
      "type": "boolean",
      "description": "Include alpha/beta/rc versions in the range"
    }
  },
  "additionalProperties": false
}
    arguments 38 lines
_ try it over mcp 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 3d04f59f8a87f809.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3d04f59f8a87f809/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/3d04f59f8a87f809/badge.svg)](https://brick.blue/agent/3d04f59f8a87f809?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 knowoff the mcp door
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
1
ok
0
failed
1
success rate
0%
median latency
434ms
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
—

1 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.