Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.pages.datanest-stores/store

REMOTE · DATANEST-STORES.COM

Search and preview Datanest developer products, then prepare buyer-authorized Stripe Checkout.

72 Trust /100

Last scanned (14 hours ago)

Scores higher than 63% of remote servers

Reachable. Last reached 23 Oct 2026.

Category E-commerce

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1117 tokens (~159/item across 7 items; 7 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Changelog

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.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 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.

  • 20 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 19 Oct 26 70

    First indexed and scored.

Diagnostics

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 23 Oct 2026 · Probed https://datanest-stores.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=datanest-stores.com CN=WE1,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 3b3ebe341d2d0f841384a21ad198d0d4
SANs: datanest-stores.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 datanest-stores.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
datanest-stores.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://datanest-stores.com/mcp Verified 200
http (plaintext) http://datanest-stores.com/mcp HTTPS enforced 301 https://datanest-stores.com/mcp
MCP tools · 7 exposed · ~984 tokens

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 →

Tool Tokens
check_order_status ~91

Poll the status of a checkout session created by create_checkout_link. Returns a coarse status (paid | open | expired | unknown) and the recommended next step, with NO buyer PII. When status is "paid", call get_purchase_access with the same session_id to obtain the download link.

NameTypeReqDescription
checkout_session_idstringyesThe Stripe checkout session id (cs_...) returned by create_checkout_link.

No output schema declared.

No examples provided.

compare_products ~89

Compare 2–4 products factually, using only stored metadata (price, license, versions, prerequisites, files, verification status, etc.). Never fabricates differences or suitability claims. Read-only and public.

NameTypeReqDescription
product_idsarrayyes2 to 4 product ids or slugs.
use_casestring–Optional buyer use case (recorded, not used to invent claims).

No output schema declared.

No examples provided.

create_checkout_link ~214

SIDE-EFFECTING: creates a short-lived Stripe Checkout session/link for ONE product (quantity fixed to 1) and returns only the hosted checkout URL, product summary, exact price, and expiry. The price and Stripe price id are resolved server-side from trusted catalogue data — client-supplied price/amount/currency/name/price-id are ignored/rejected. The buyer must explicitly authorize payment in Stripe Checkout; NO card is charged autonomously. Products that are unaudited/deprecated/not agent-sellable are rejected.

NameTypeReqDescription
buyer_emailstring–Optional prefill for the checkout.
cancel_urlstring–Optional; must be on the allowlisted host.
idempotency_keystring–Optional idempotency key to avoid duplicate sessions.
product_idstringyesProduct id, SKU, or unambiguous slug.
quantitynumber–Must be 1 (digital product).
success_urlstring–Optional; must be on the allowlisted host.

No output schema declared.

No examples provided.

get_product_details ~99

Return the full factual detail for one product: exact title, price/currency, short + detailed description, included files, prerequisites, supported technologies/versions, install time, license, latest version, last verified date, verification status, compatibility notes, preview URL, product page URL, and stable product_id/SKU. Read-only and public.

NameTypeReqDescription
product_idstringyesProduct id ("store:slug"), SKU, or unambiguous slug.

No output schema declared.

No examples provided.

get_product_preview ~80

Return SAFE public previews only: documentation excerpts, a file-name tree, screenshot/demo links, and sample snippets intended for public display. Never returns the purchased ZIP, private storage URLs, secrets, whole paid source files, or signed download URLs. Read-only and public.

NameTypeReqDescription
product_idstringyesProduct id, SKU, or unambiguous slug.

No output schema declared.

No examples provided.

get_purchase_access ~139

AUTHENTICATED: for a buyer who already completed a purchase, returns a short-lived (~15 min), single-purpose signed download link for THEIR order only. Ownership is proven by an unguessable credential issued at fulfilment — the Stripe session_id or the download token. Reuses the existing entitlement + signed-link service; each call consumes one of the limited downloads. Cannot list or access other purchasers' orders.

NameTypeReqDescription
download_tokenstring–Download token (UUID) issued at fulfilment.
emailstring–Optional purchaser email, recorded for audit.
session_idstring–Stripe checkout session id (cs_...).

No output schema declared.

No examples provided.

search_products ~272

Search the Datanest catalogue of digital technical products. Accepts natural-language intent queries (e.g. "add authentication to my SaaS", "reduce my AWS bill", "prepare for a system design interview") — stopwords and phrasing are handled, and synonyms are expanded. Returns concise product cards ranked by relevance, with stable canonical URLs. If a query matches little, the result includes suggestions/did_you_mean/available_domains so you can refine. Read-only and public. By default only agent-purchasable products are returned; set include_unsellable=true to also surface unaudited/deprecated items (clearly flagged, not buyable).

NameTypeReqDescription
categorystring–Filter by human category name.
domainstring–Filter by domain/family id: data, ai, cloud, dev, security, career.
include_unsellableboolean–Also include unaudited/deprecated products (discoverability only).
max_price_usdnumber––
pageinteger––
page_sizeinteger––
querystring–Free-text search over title, description, tags, and store.
tagsarray–Require ALL of these tags.
verified_onlyboolean–Only return first-party "verified" products.

No output schema declared.

No examples provided.

Install

How do I install the dev.pages.datanest-stores/store MCP server?

dev.pages.datanest-stores/store is a hosted endpoint at https://datanest-stores.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 · datanest-stores.com

# add to Claude Code
claude mcp add --transport http dev-pages-datanest-stores-store 'https://datanest-stores.com/mcp'
Common questions

What is the dev.pages.datanest-stores/store MCP server?

dev.pages.datanest-stores/store is an MCP server listed in the public MCP registry as dev.pages.datanest-stores/store. Search and preview Datanest developer products, then prepare buyer-authorized Stripe Checkout. This page covers its hosted endpoint (https://datanest-stores.com/mcp).

Is the dev.pages.datanest-stores/store MCP server safe to use?

dev.pages.datanest-stores/store scores 72 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 dev.pages.datanest-stores/store MCP server expose?

dev.pages.datanest-stores/store exposes 7 tools: search_products, get_product_details, compare_products, get_product_preview, create_checkout_link, and 2 more. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.

Does the dev.pages.datanest-stores/store MCP server require authentication?

No. We connected to dev.pages.datanest-stores/store without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dev.pages.datanest-stores/store MCP server still maintained?

dev.pages.datanest-stores/store is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.