Platform Changes
REMOTE · CHANGES.BROMPUTERS.CO.UK
Live, sourced changes feed: Apple, Google Play, Android, GitHub, Vercel, Cloudflare, Firebase, more.
Available components
Last scanned (21 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 666 tokens (~133/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (60% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “recent_changes” rewrote its description, which is the text the model reads security
- Tool “weekly_digest” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 11 Oct 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://changes.bromputers.co.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=changes.bromputers.co.uk | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 10 Oct 2026 | 25 Apr 2027 | RSA 2048 | SHA256-RSA | b3879d74365b2e119631a1a86d1bd2c |
| SANs: changes.bromputers.co.uk | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of changes.bromputers.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| co.uk. | present | 11810 | 8 | Verified |
| bromputers.co.uk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://changes.bromputers.co.uk/mcp | Verified | 200 | |
| http (plaintext) | http://changes.bromputers.co.uk/mcp | Inconclusive | 403 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_change ~36
Full stored record for one change id (as returned by the other tools), including the full summary.
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string | yes | – |
No output schema declared.
No examples provided.
list_sources ~26
List the platforms and official sources this feed monitors, with last poll time and item counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
recent_changes ~190
Recent platform changes, newest first. platform: filter by platform (apple, android, google-play, github, vercel, cloudflare, expo, supabase, firebase). tag: filter by heuristic tag (deprecation, breaking, deadline, policy, security, pricing). days: look-back window (max 90). limit: max items (max 50). Summaries are truncated; use get_change for full text. min_importance: "low" (everything), "medium" or "high" to drop routine release noise. Importance is AI-rated or heuristic (see importance_basis). by: "published" (default) or "updated", which also surfaces old posts the vendor edited recently.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | – |
| days | integer | – | – |
| limit | integer | – | – |
| min_importance | string | – | – |
| platform | – | – | – |
| tag | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
search_changes ~41
Case-insensitive text search over change titles and summaries, newest first. limit max 50.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
weekly_digest ~124
Short ranked overview: the most important recent changes grouped by platform. Best first call. platforms: limit to these platforms (apple, android, google-play, github, vercel, cloudflare, expo, supabase, firebase); default all. days: look-back window (max 30). per_platform: items per platform (max 10). Ranking is by importance (AI-rated, heuristic fallback), then recency. Read the source_url before acting on any item.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| per_platform | integer | – | – |
| platforms | – | – | – |
No output schema declared.
No examples provided.
How do I install the Platform Changes MCP server?
Platform Changes is a hosted endpoint at https://changes.bromputers.co.uk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · changes.bromputers.co.uk
claude mcp add --transport http oprych22-platform-changes 'https://changes.bromputers.co.uk/mcp'
What is the Platform Changes MCP server?
Platform Changes is an MCP server listed in the public MCP registry as io.github.Oprych22/platform-changes. Live, sourced changes feed: Apple, Google Play, Android, GitHub, Vercel, Cloudflare, Firebase, more. This page covers its hosted endpoint (https://changes.bromputers.co.uk/mcp).
Is the Platform Changes MCP server safe to use?
Platform Changes scores 57 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Platform Changes MCP server expose?
Platform Changes exposes 5 tools: list_sources, recent_changes, weekly_digest, search_changes, get_change. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.
Does the Platform Changes MCP server require authentication?
No. We connected to Platform Changes without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Platform Changes MCP server still maintained?
Platform Changes is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.