Aseptway: Houston pharmacy cleanroom and hood certification coordination

com.forevenza.servicesPublished by services.forevenza.comv1.0.0Updated Nov 7, 2026

Houston pharmacy cleanroom and hood certification coordination

The publisher's own server: hood. — .hood name service

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Coordinates Houston pharmacy cleanroom and hood certification requests: submit a scope, track status, inspect offers, accept or decline, and release payment…

What you can do
  • Learn what the service does and which request fields it expects
  • Submit a certification requirement and receive a reference number
  • Resume a request with receipt credentials and read linked offers
  • Inspect an offer's exact terms, terms hash, order state and payment links
  • Accept or decline an offer, and confirm a payment release where the order allows it
When to use it
Use it when a pharmacy or cleanroom site needs certification scope, provider pricing and visit options gathered and progressed, and you want the assistant to file the request and follow the resulting offers rather than exchange emails by hand.
Requirements
A remote streamable HTTP endpoint; no package, environment variable or header is declared. You supply site notes or inventory, room classifications, PECs, sampling exclusions and visit or report targets, plus an email address for replies. Receipt and offer link credentials are needed to resume a request or inspect an offer.
Before you install
Submitting a request sends your site details to a third-party coordinator, and replies come by email. A request is not a booking or a certification result. Accepting an offer places an order on the buyer's behalf and requires the exact terms hash and explicit acceptance; release_payment records approval but does not pay the processor. Keep receipt and offer credentials private.

Installation

In SourceWeft

  1. Open Aseptway: Houston pharmacy cleanroom and hood certification coordination in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.forevenza.services%2Faseptway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "aseptway-houston-pharmacy-cleanroom-and": {
      "type": "http",
      "url": "https://aseptway.forevenza.com/mcp"
    }
  }
}

Tools

7

describe_business

About Aseptway

What Aseptway does, what happens to a request, and the request fields.

Takes no parameters.

submit_request

Send a requirement

Send a requirement to Aseptway. It is kept with a reference number. Your request is recorded with a reference number. Aseptway reviews your proposed scope, resolves consequential questions and seeks provider pricing and visit options. We reply by email when you leave an address. Nothing is ordered or committed until you agree terms; a request does not reserve a visit. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.

Parametersneedrequiredactionbudgettimingcontactquantitygeographycontinuationspecificationsrequested_fields

request_status

request status

Resume a requirement using the receipt credentials. Read the recorded requirement and any linked offers. Contact details are kept apart.

Parametersidrequiredtokenrequired

inspect_offer

inspect offer

Read the exact authorized terms, terms hash, order state and processor payment links. Use the offer link credentials, or credentials of the request explicitly linked to this offer.

Parametersidrequiredtokenrequired

accept_offer

accept offer

Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state.

Parametersidrequirednamerequiredtokenrequiredacceptrequiredorganizationterms_sha256requiredpurchase_order

decline_offer

decline offer

Decline an issued offer on its inspected terms.

Parametersidrequiredtokenrequiredreasonterms_sha256required

release_payment

release payment

Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.

Parametersidrequirednametokenrequiredconfirmrequiredpaymentrequiredterms_sha256required

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Hood integrations