Nestphones
REMOTE · NESTPHONES.COM
Phone, tablet and smartwatch specs with Algerian prices in DZD, comparisons and articles.
Available components
Last scanned (10 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 813 tokens (~135/item across 6 items; 6 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 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.
- 2 Nov 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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 71
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 5 Nov 2026 · Probed https://nestphones.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nestphones.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 11ab62109404e5260e1a0a1ef8efe5b6 |
| SANs: nestphones.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nestphones.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nestphones.com. | 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://nestphones.com/mcp | Verified | 200 | |
| http (plaintext) | http://nestphones.com/mcp | HTTPS enforced | 301 | https://nestphones.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 →
browse_devices ~272
Browse published devices using the same filters as the site. Price bands are in Algerian dinars (DA); unknown prices remain null. Returns 10 devices per page.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Brand slug from list_brands. |
| category | string | – | Device category. Omit to include all categories. |
| fiveG | boolean | – | Only devices with 5G when true. |
| language | string | – | Language of returned page URLs and blog articles: en (default), fr or ar. |
| nfc | boolean | – | Only devices with NFC when true. |
| page | integer | – | Result page, starting at 1. |
| priceRange | string | – | DA price band: below 30000, 30000–59999, 60000–99999, at least 100000, or at least 200000. |
| q | string | – | Device name or brand, for example Samsung Galaxy S26. |
| ram | string | – | RAM in GB: exact 4, 6 or 8; at least 12 for the 12 option. |
| sort | string | – | Listing order. Defaults to newest. |
| storage | string | – | Storage in GB: exact 64, 128 or 256; at least 512 for the 512 option. |
No output schema declared.
No examples provided.
compare_devices ~85
Return specifications and DA prices for 2–4 distinct device slugs. The website displays two devices at a time; returns a comparison URL for each pair. Does not navigate.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of returned page URLs and blog articles: en (default), fr or ar. |
| slugs | array | yes | Two to four distinct device slugs from search_devices. |
No output schema declared.
No examples provided.
get_device ~84
Get a published device by its exact slug: full specifications, tracked Algerian price in DA (null if unavailable), and canonical URL. Works for phones, tablets and watches.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of returned page URLs and blog articles: en (default), fr or ar. |
| slug | string | yes | Exact device or brand slug returned by a Nestphones tool. |
No output schema declared.
No examples provided.
list_blog_articles ~94
Find Nestphones blog articles in the requested language by title, excerpt or tag. Returns up to 9 summaries and URLs per page; follow a URL to read the full article.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of returned page URLs and blog articles: en (default), fr or ar. |
| page | integer | – | Result page, starting at 1. |
| q | string | – | Optional article topic or tag. |
No output schema declared.
No examples provided.
list_brands ~48
List enabled device brands with exact brand slugs and URLs for filtering and browsing.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of returned page URLs and blog articles: en (default), fr or ar. |
No output schema declared.
No examples provided.
search_devices ~95
Search published Nestphones devices by name or brand. Returns up to 10 matches, prices in Algerian dinars (DA), key specs and device URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language of returned page URLs and blog articles: en (default), fr or ar. |
| page | integer | – | Result page, starting at 1. |
| q | string | yes | Device name or brand, for example Samsung Galaxy S26. |
No output schema declared.
No examples provided.
How do I install the Nestphones MCP server?
Nestphones is a hosted endpoint at https://nestphones.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 · nestphones.com
claude mcp add --transport http com-nestphones-devices 'https://nestphones.com/mcp'
What is the Nestphones MCP server?
Nestphones is an MCP server listed in the public MCP registry as com.nestphones/devices. Phone, tablet and smartwatch specs with Algerian prices in DZD, comparisons and articles. This page covers its hosted endpoint (https://nestphones.com/mcp).
Is the Nestphones MCP server safe to use?
Nestphones scores 73 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 Nestphones MCP server expose?
Nestphones exposes 6 tools: search_devices, browse_devices, get_device, compare_devices, list_brands, list_blog_articles. Their descriptions and schemas cost roughly 678 tokens of context every time the server is loaded.
Does the Nestphones MCP server require authentication?
No. We connected to Nestphones without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nestphones MCP server still maintained?
Nestphones 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.