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.PAGES.DEV · SCANNED SEP 20

Search, preview, and buy 500+ MIT-licensed digital developer products from Datanest Stores.

0 this week 23 Trust /100
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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.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.

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.pages.dev/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.pages.dev

# add to Claude Code
claude mcp add --transport http dev-pages-datanest-stores-store 'https://datanest-stores.pages.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-pages-datanest-stores-store": {
      "url": "https://datanest-stores.pages.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-pages-datanest-stores-store": {
      "type": "http",
      "url": "https://datanest-stores.pages.dev/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.dev-pages-datanest-stores-store]
url = "https://datanest-stores.pages.dev/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-pages-datanest-stores-store": {
      "type": "remote",
      "url": "https://datanest-stores.pages.dev/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-pages-datanest-stores-store --url 'https://datanest-stores.pages.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  dev-pages-datanest-stores-store:
    url: "https://datanest-stores.pages.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-pages-datanest-stores-store": {
      "Transport": "http",
      "Url": "https://datanest-stores.pages.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add dev-pages-datanest-stores-store -t streamable-http -u 'https://datanest-stores.pages.dev/mcp'
// mcp.json
{
  "mcpServers": {
    "dev-pages-datanest-stores-store": {
      "type": "http",
      "url": "https://datanest-stores.pages.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Aug 26 −50
    • Endpoint reachability: reachable → not serving MCP security
    • Stability: 0.70 → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Aug 26 0
    • Tool “search_products” rewrote its description, which is the text the model reads security
  • 2 Aug 26 0
    • Stability: unverified → 0.03 functional
  • 1 Aug 26 0

    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 20 Sept 2026 · Probed https://datanest-stores.pages.dev/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.pages.dev CN=YE2,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 ECDSA 256 ECDSA-SHA384 57bcfa86b7c2b0c82b5b7c8bbd9dc4bc35d
SANs: *.datanest-stores.pages.dev, datanest-stores.pages.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of datanest-stores.pages.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
pages.dev. 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 301

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://datanest-stores.pages.dev/mcp Redirected 301 https://datanest-stores.com/mcp
http (plaintext) http://datanest-stores.pages.dev/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_casestringOptional 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_emailstringOptional prefill for the checkout.
cancel_urlstringOptional; must be on the allowlisted host.
idempotency_keystringOptional idempotency key to avoid duplicate sessions.
product_idstringyesProduct id, SKU, or unambiguous slug.
quantitynumberMust be 1 (digital product).
success_urlstringOptional; 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_tokenstringDownload token (UUID) issued at fulfilment.
emailstringOptional purchaser email, recorded for audit.
session_idstringStripe 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
categorystringFilter by human category name.
domainstringFilter by domain/family id: data, ai, cloud, dev, security, career.
include_unsellablebooleanAlso include unaudited/deprecated products (discoverability only).
max_price_usdnumber
pageinteger
page_sizeinteger
querystringFree-text search over title, description, tags, and store.
tagsarrayRequire ALL of these tags.
verified_onlybooleanOnly return first-party "verified" products.

No output schema declared.

No examples provided.

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, preview, and buy 500+ MIT-licensed digital developer products from Datanest Stores. This page covers its hosted endpoint (https://datanest-stores.pages.dev/mcp).

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

dev.pages.datanest-stores/store 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 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.