Sun Ryse MCP plugins

Privacy for Sun Ryse MCP plugins

What these hosted tools receive, process and send to public data sources.

Effective and last updated: 2026-10-29

Services covered

Sun Ryse Software LLC operates the following hosted MCP plugins and their informational pages. These notices cover the nine individual plugins on sunryse-tools.sunrysetech-com.workers.dev and their optional Check My Work collection endpoint.

The separate HaulMath MCP connector has its own privacy notice, terms and support page. It provides a comparison workspace, two calculators and community product and price lookups.

This scope does not include the HaulMath mobile app, other Sun Ryse products, or the AI application in which you use a connector. Their applicable notices and terms are separate.

Inputs and responses

When your AI host invokes a tool, the service receives the structured fields needed for that operation. Depending on the tool, those fields may include public product names, a DOI or notice identifier, document excerpts, dates, quantities, aggregate report values, scope or job IDs, or an authorized practice key and answers. The service returns the result to the requesting host.

These connectors do not require account linking or OAuth credentials and have no integration for retrieving private files, receipts or your full chat history. Your host determines which fields it sends. Supply public or nonsensitive information that you are authorized to use; omit passwords, payment information, personal records and confidential documents.

Temporary processing and storage

The deployed tool code processes inputs and results in memory for the request. It does not save tool inputs, results, user profiles, inventories, study progress or chat sessions to a service database. It does not set user cookies or create MCP sessions. Application request logs and traces are disabled in the current Worker configurations; tool inputs and outputs are not written to application logs.

Calculations and comparisons use the supplied inputs. Your AI host controls any retention of draft inputs and results in the interactive view.

For abuse prevention, short-lived Cloudflare rate-limit counters use the connecting IP address and service identifier to limit request bursts. These counters do not contain tool inputs or results and are not used for advertising or user analytics.

Requests pass through Cloudflare hosting and network systems. Those systems may process technical request information to deliver or protect the service under their own policies. Your AI host, public data providers, and any website you follow from a result have their own handling and retention practices. The temporary-processing description above does not promise that those independent systems retain nothing.

Anonymous usage counts and your control

To measure which tools run and whether they finish, we store daily aggregate counters in Cloudflare D1. For each UTC day and combination of plugin, tool, outcome, HTTP status, broad activity and client categories, and declared workspace/example flags, we store totals for tool-call attempts, handler starts and completions, and elapsed duration. We do not store individual tool-call records, exact event timestamps or event IDs. These daily aggregates remain until we clear them. Connection setup, tool discovery, resource reads and guide-page views do not contribute to these counts. Opening the workspace is counted separately from running a task.

These aggregates contain no tool inputs or results, document text, search terms, request IDs, raw user-agent strings, IP addresses, account identifiers or cookies. They do not provide a person or unique-user count. Client labels distinguish declared probes and tests; a Codex or browser label is not proof of a human user. We use aggregate counts to understand tool usefulness and reliability, not for advertising profiles or cross-site tracking.

In the workspace, uncheck “Include anonymous usage counts” before running a task to exclude future tasks in that open view. For a custom MCP client, send DNT: 1, Sec-GPC: 1, or X-Sunryse-Telemetry: off, or set params._meta["sunryse/telemetry"] to false on a tool call. These choices do not reduce tool functionality. A host may not forward your browser's privacy preference; the workspace control applies directly to its calls. We do not maintain an identifiable request history to retrieve or delete.

Public-source requests

PluginWhat leaves the tool serviceDestination
Product Recall CheckerProduct-name search terms or a selected recall ID. Model, brand and lot inputs stay inside the tool; only returned structured model values support exact comparisons, while unsupported brand and lot checks remain unresolved.CPSC's public API at saferproducts.gov
Citation CheckerA public bibliography search phrase or selected DOI. Claimed titles in an audit are compared inside the tool.api.crossref.org
Public Comment DeadlinesTopic or docket search terms, publication filters and selected document IDs. A selected notice may trigger a bounded related-docket search.federalregister.gov

Document Change Checker, Scope Change Checker, Report Numbers Checker, Renewal Deadline Planner, Study Plan Builder and Job Status Checker do not make external data lookups. Calendar-text exports also use caller-supplied inputs. None of these MCP services sends tool inputs to a separate model API.

Pages, contact and your choices

These plugin pages contain no analytics script, sign-in form or upload form. Following a link to the company contact page or another website takes you to that site's policies. Support correspondence that you choose to send is separate from a tool request and is handled through the company contact channels.

You can stop sending requests or remove a connector in your AI host. To manage chat history or host-retained data, use that host's controls. We do not maintain identifiable request histories or stored tool-input/result content. For questions about this notice or information sent to Sun Ryse support, use Sun Ryse product support; do not include sensitive inputs in an initial message.

Changes

This notice describes the services as of the date above. If their processing changes, this page will be updated. A future account, storage or payment feature would require an appropriate update; this notice does not claim those features exist today.