Skip to main content

Commonstop: Shared-route sharps and red-bag pickup for Dallas County offices

com.forevenza.services/commonstopVersion 1.0.1

Sharps and red-bag pickup proposals for Dallas County offices, with named-office records

Status

Responds1132 msAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.
Last checked
Nov 14, 2026, 13:57 UTC
Latency
1132 ms
Remotes responding
1 of 1
Sign-in
No sign-in
Hosting
Hosted outside the EU (detected)
Registry data as of
Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP
https://commonstop.forevenza.com/mcpResponds1132 ms
No sign-in

Claude Code

claude mcp add --transport http commonstop https://commonstop.forevenza.com/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: commonstop
Remote MCP server URL: https://commonstop.forevenza.com/mcp

Cursor

{
  "mcpServers": {
    "commonstop": {
      "url": "https://commonstop.forevenza.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"commonstop","type":"http","url":"https://commonstop.forevenza.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

18 tools

Tools of Commonstop: Shared-route sharps and red-bag pickup for Dallas County offices
Read-only
Idempotent
Open world
accept_offerPlace 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.NoNoYesNo
answer_remedyAccept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, which applies it and shows the result there. Accepting a credit or refund here moves no money; the business records it when its payment processor does.NoNoYesNo
counter_offerPropose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery date, a total price for the whole, a payment plan, or a note. It is a proposal, not a change: the terms stand and can still be accepted as they are. The business answers it in inspect_offer thread.counteroffers, with a revised offer to inspect and accept, or a reason. A later proposal replaces an earlier one still awaiting an answer. Nothing here orders or pays.NoNoYesNo
decline_offerDecline an issued offer on its inspected terms.YesNoYesNo
describe_businessWhat Commonstop does (Shared-route sharps and red-bag pickup for Dallas County offices: Describe your office's waste collection. Commonstop prepares the requirement, seeks route pricing and brings back a nonbinding monthly-price proposal and provider terms by email.), what happens to a request, what you receive, its price basis (a verified price, an estimate, a method or a scoped quotation; never an offer), when a reply is due, who the buyer contracts with and who invoices, its scope, and the request fields with examples.NoYesYesNo
edit_requirementSet fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.NoNoYesNo
get_requirementA Commonstop requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.NoYesYesNo
inspect_deliveryRecord the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally for one portion of the order. Whether it was accepted is computed: only when nothing is rejected. Recorded for the business, which answers a rejection in inspect_offer thread.fulfilment, with a proposed remedy. Nothing here pays or refunds.NoNoYesNo
inspect_offerRead the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status and purchase order matches it holds (thread.purchasing), and the portions, shortfall and remedies of delivery (thread.fulfilment). Use the offer link credentials, or credentials of the request explicitly linked to this offer.NoYesYesNo
interpret_requirementGive Commonstop the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written. Pass the requirement (id, token) from the first answer to continue it. Nothing is sent or ordered: send_requirement sends it when the buyer says so. When you already have the fields in structured form, use submit_request instead.NoNoNoNo
release_paymentConfirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.NoNoYesNo
report_vendor_statusReport the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requested. Recorded as the buyer's own statement; the business answers it in inspect_offer thread.purchasing.NoNoYesNo
request_statusResume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by sending a continuation. Contact details are kept apart.NoYesYesNo
retrieve_deliverableRetrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before payment is confirmed it says it is not yet available. Use the offer link or linked request credentials.NoYesYesNo
send_requirementSend the requirement to Commonstop once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later send of a changed requirement records a revision of the same request. Name the revision the buyer saw. This orders nothing: an offer comes later and is accepted separately on its exact terms.NoNoYesNo
state_purchasing_requirementsTell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, the seller's vendor id with the buyer, where orders and invoices go, and the payment terms. Recorded as the buyer's statement; the business answers it in inspect_offer thread.purchasing. Nothing here orders or pays.NoNoYesNo
submit_purchase_orderSend the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the accepted terms; differences are recorded and shown in inspect_offer thread.purchasing as exceptions, never silently accepted. A changed purchase order is the same number with a higher revision. This does not accept the offer and pays nothing.NoNoYesNo
submit_requestSend Commonstop a requirement (Shared-route sharps and red-bag pickup for Dallas County offices). Your request is recorded and you receive a reference number. Commonstop reviews the prepared requirement and open questions, confirms scope and coverage, seeks provider pricing and terms, and replies by email to the address you leave with a nonbinding monthly-price proposal. Records and manifests in your office's name are a condition of the provider proposal. Nothing is ordered or committed until you agree terms in writing. 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. It is answered with a receipt: keep its id and token to read its status (request_status), to add details later (continuation) and to act on an offer made in reply. A requirement is not an order and costs nothing.NoNoNoNo

Details

Registry status
Active
Published
Nov 6, 2026
Updated
Nov 6, 2026
Repository
Not given
Categories (suggested)
Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR
Not declared

Are you the operator? Claim this listing