Home / MCP registry index / com.smartpress/mcp

Smartpress

com.smartpress/mcp in the official MCP registry. Endpoint https://mcp.smartpress.com/mcp.

The registry describes it as: Configure, price, proof and add custom print products to a Smartpress cart. US printing, no login.

We read its 21 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_product_config find_products get_product_templates create_config_session update_config_session get_session_latest create_file_session link_file_session clone_file_session list_session_files get_file_upload_url add_to_cart analyze_file get_file_analysis get_file_session_analysis recommend_products get_file_session_proofs create_proof create_file_check set_proof_approval send_feedback

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-smartpress-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-smartpress-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.