MCP Morning
REMOTE · MCPMORNING.COM
Daily MCP server rankings from public npm, PyPI, and GitHub data.
Available components
Last scanned (14 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 fully verified: no authorisation is required to call this server, and 4 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 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 & 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 566 tokens (~141/item across 4 items; 4 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 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.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 9 Nov 26 62
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 21 Nov 2026 · Probed https://mcpmorning.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpmorning.com | CN=YR2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 4096 | SHA256-RSA | 62a33c8f7806ab259dc15d3f01215ffad2d |
| SANs: mcpmorning.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcpmorning.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| mcpmorning.com. | No DS | 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://mcpmorning.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcpmorning.com/mcp | HTTPS enforced | 302 | https://mcpmorning.com/mcp |
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_server ~100
One MCP server from the current snapshot: stars, weekly downloads, growth, install hints from registry package metadata, and links (GitHub, npm/PyPI, its MCP Morning page). Identify by slug, owner/repo, GitHub URL, or registry name. Install snippets are unverified — we do not run servers.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Slug (e.g. browser-use-browser-use), GitHub URL, or owner/repo. |
No output schema declared.
No examples provided.
latest_edition ~43
Today's MCP Morning newsletter: title, date, up to 5 featured items with links, and the archive URL. Snapshot date included. Editorial, not a test report.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers ~80
Search the MCP Morning snapshot by name, slug, GitHub repo, description or registry name. limit≤25, paginate with offset. Returns snapshot date and mcpmorning.com page URLs. Does not mean MCP Morning ran the server.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | yes | Substring to match. |
No output schema declared.
No examples provided.
top_servers ~286
Ranked MCP servers from the latest MCP Morning snapshot. list=most_used (weekly downloads + GitHub stars/forks), rising (week-over-week download growth; requires 25 stars or 1,000 prior-week downloads), or new (repo created in the last 30 days). Optional language (GitHub primary language) and category (database, browser, files, search, dev, comms, cloud, ai, commerce, marketing, memory, finance). limit≤25, paginate with offset. Returns snapshot date and item page URLs. Popularity only — MCP Morning does not run or test servers.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Job category slug or label: database (Databases & data), browser (Browser & web scraping), files (Files & documents), search (Search & knowledge), dev (Dev tools & GitHub), comms (Messaging & collabo… |
| language | string | – | Filter by GitHub primary language, e.g. TypeScript or Python. |
| limit | integer | – | Page size, max 25. |
| list | string | – | Ranking to return: most_used, rising, or new. |
| offset | integer | – | Number of rows to skip for pagination. |
No output schema declared.
No examples provided.
How do I install the MCP Morning server?
MCP Morning is a hosted endpoint at https://mcpmorning.com/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 · mcpmorning.com
claude mcp add --transport http com-mcpmorning-mcpmorning 'https://mcpmorning.com/mcp'
What is the MCP Morning server?
MCP Morning is listed in the public MCP registry as com.mcpmorning/mcpmorning. Daily MCP server rankings from public npm, PyPI, and GitHub data. This page covers its hosted endpoint (https://mcpmorning.com/mcp).
Is the MCP Morning server safe to use?
MCP Morning scores 68 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 MCP Morning server expose?
MCP Morning exposes 4 tools: top_servers, search_servers, get_server, latest_edition. Their descriptions and schemas cost roughly 509 tokens of context every time the server is loaded.
Does the MCP Morning server require authentication?
No. We connected to MCP Morning without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Morning server still maintained?
MCP Morning is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MCP Morning server?
VerifyMCP ran 12 checks on MCP Morning, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MCP Morning: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.