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.

Papyras Product Catalog

REMOTE · PAPYRASAI.COM · 2 COMPONENTS

Search 37,000+ home, garden, outdoor & tool products with live prices and buy links.

+4 this week 65 Trust /100

Last scanned (22 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 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 Security57
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 755 tokens (~151/item across 5 items; 5 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 Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

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 5 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 →

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.

  • 21 Nov 26 +1

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

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

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

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

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

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 59

    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 21 Nov 2026 · Probed https://papyrasai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=papyrasai.com CN=YE1,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 58651625f2fd82c1579eadd04bafc47acde
SANs: papyrasai.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 papyrasai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
papyrasai.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://papyrasai.com/mcp Verified 200
http (plaintext) http://papyrasai.com/mcp HTTPS enforced 301 https://papyrasai.com/mcp
MCP tools · 5 exposed · ~671 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
get_feed_page ~98

Page through the full product catalog sequentially (ordered by when each product was added), rather than searching for anything specific. Useful for bulk export or systematically walking the entire catalog. Defaults to in_stock only; pass availability="all" to include every status. Increase `offset` to get subsequent pages.

NameTypeReqDescription
availability–––
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

get_product ~99

Fetch full detail for a single product by its UUID, including description, material/color/size, full enrichment fields (explanation_long, carousel_label, gift-friendliness, price percentile, rating), current price/availability, and the affiliate purchase URL. Returns full detail regardless of stock status -- this is a direct lookup, not a discovery search.

NameTypeReqDescription
product_idstringyes–

No output schema declared.

No examples provided.

get_products_batch ~107

Fetch multiple products at once by their UUIDs (max 100 per call). Useful when an agent already has a list of candidate product IDs (e.g. from a previous search) and wants full current data for all of them in one call instead of N separate lookups. Returns `results` for found products and `not_found` for any IDs that don't exist in the catalog.

NameTypeReqDescription
product_idsarrayyes–

No output schema declared.

No examples provided.

get_related_products ~79

Fetch products related to a given product (similar, accessory, bundle, or alternative relationships). Currently returns an empty list for all products since relationship data hasn't been generated yet -- calling this will not error, it just won't return anything useful until that pipeline is built.

NameTypeReqDescription
product_idstringyes–

No output schema declared.

No examples provided.

search_products ~288

Search the Papyras product catalog using hybrid structured + semantic search. Pass `query` for free-text/natural-language search -- longer, natural phrases (e.g. "pressure washer for patio") retrieve more accurately than bare single words (e.g. "patio"), since the embedding model has more context to place the query vector precisely. Combine with structured filters (category, brand, price range, intent_tag, use_case_tag, audience_tag) to narrow results further. Defaults to showing only in_stock products. Pass availability="all" to see every status, or a specific value (in_stock | out_of_stock | preorder | discontinued) to filter to just that one. Returns a dict with `results` (list of product summaries including name, price, affiliate_url, tags, and a short explanation of why the product is relevant), plus `count`, `limit`, `offset`, and whether semantic search was actually used.

NameTypeReqDescription
audience_tag–––
availability–––
brand–––
category–––
intent_tag–––
limitinteger––
max_price–––
min_price–––
offsetinteger––
query–––
use_case_tag–––

No output schema declared.

No examples provided.

Install

How do I install the Papyras Product Catalog MCP server?

Papyras Product Catalog is a hosted endpoint at https://papyrasai.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 · papyrasai.com

# add to Claude Code
claude mcp add --transport http papyrasai-cpu-papyras 'https://papyrasai.com/mcp'
Common questions

What is the Papyras Product Catalog MCP server?

Papyras Product Catalog is an MCP server listed in the public MCP registry as io.github.papyrasai-cpu/papyras. Search 37,000+ home, garden, outdoor & tool products with live prices and buy links. This page covers its hosted endpoint (https://papyrasai.com/mcp).

Is the Papyras Product Catalog MCP server safe to use?

Papyras Product Catalog scores 65 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 Papyras Product Catalog MCP server expose?

Papyras Product Catalog exposes 5 tools: search_products, get_product, get_products_batch, get_related_products, get_feed_page. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.

Does the Papyras Product Catalog MCP server require authentication?

No. We connected to Papyras Product Catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Papyras Product Catalog MCP server still maintained?

Papyras Product Catalog 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 Papyras Product Catalog MCP server?

VerifyMCP ran 12 checks on Papyras Product Catalog, 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 Papyras Product Catalog: 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.