Morning brief
REMOTE · IAAPP-A912A14E.ALPIC.LIVE
Chatgpt app for Morning brief
Available components
Last scanned (5 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 14 Oct 26 −61
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Oct 26 0
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
- 12 Oct 26 0
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
- 10 Oct 26 0
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
- 9 Oct 26 0
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
- 5 Oct 26 0
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
- 4 Oct 26 0
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
- 3 Oct 26 84
- Resource “get-morning-brief” now points somewhere else: ui://widgets/apps-sdk/get-morning-brief.html → ui://widgets/ext-apps/get-morning-brief.html security
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 5 Nov 2026 · Probed https://iaapp-a912a14e.alpic.live
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.alpic.live | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 23 Sept 2026 | 8 Apr 2027 | RSA 2048 | SHA256-RSA | 41ca0c3068063f7c713f936a81919aa |
| SANs: *.alpic.live | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| 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 iaapp-a912a14e.alpic.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| live. | present | 4724, 36322 | 8, 8 | Verified |
| alpic.live. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://iaapp-a912a14e.alpic.live | HTTP error | 404 | |
| sse | https://iaapp-a912a14e.alpic.live | HTTP error | 404 | |
| http (plaintext) | http://iaapp-a912a14e.alpic.live | HTTPS enforced | 301 | https://iaapp-a912a14e.alpic.live/ |
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-morning-brief ~94
Generate a prioritized morning briefing from a unified array of async messages (email, Slack, Linear). Returns urgent items, hot deals, and today's commitments.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Reference date in ISO format. Defaults to today. |
| locale | string | – | Primary locale for pattern matching. Defaults to 'fr'. |
| messages | array | yes | Unified messages from any source (email, Slack, Linear, etc.) |
No output schema declared.
No examples provided.
How do I install the Morning brief MCP server?
Morning brief is a hosted endpoint at https://iaapp-a912a14e.alpic.live/, 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 · iaapp-a912a14e.alpic.live
claude mcp add --transport http live-alpic-iaapp-a912a14e-iaapp 'https://iaapp-a912a14e.alpic.live/'
What is the Morning brief MCP server?
Morning brief is an MCP server listed in the public MCP registry as live.alpic.iaapp-a912a14e/IAApp. Chatgpt app for Morning brief. This page covers its hosted endpoint (https://iaapp-a912a14e.alpic.live).
Is the Morning brief MCP server safe to use?
Morning brief scores 23 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 Morning brief MCP server expose?
Morning brief exposes 1 tool: get-morning-brief. Their descriptions and schemas cost roughly 94 tokens of context every time the server is loaded.
Does the Morning brief MCP server require authentication?
Its publisher declares no required credentials for Morning brief. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Morning brief MCP server still maintained?
Morning brief is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.