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.

Quarterline: Grease trap pumping for Austin restaurant groups, on one 90-day calendar

REMOTE · QUARTERLINE.FOREVENZA.COM

Requests for grease trap pumping across Austin restaurant locations on one calendar and invoice

+4 this week 68 Trust /100

Last scanned (13 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Workflow Automation

Recent critical change

Authorization (7 Nov 2026). See the changelog before you install this server.

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 Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3014 tokens (~167/item across 18 items; 18 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 19 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 (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1
    • Tool “describe_business” rewrote its description, which is the text the model reads security
  • 12 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.

  • 10 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “request_status” rewrote its description, which is the text the model reads security
    • Schema quality: 2366 → 2977 ▼ functional
    • New tool “edit_requirement” functional
    • New tool “get_requirement” functional
    • New tool “interpret_requirement” functional
    • New tool “send_requirement” functional
  • 9 Nov 26 +5
    • HTTPS: unverified → pass ▲ security
    • Tool “describe_business” rewrote its description, which is the text the model reads security
    • Tool “inspect_offer” rewrote its description, which is the text the model reads security
    • Tool “submit_request” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 16% → 62% ▲ functional
    • Schema quality: fair → good functional
    • New tool “answer_remedy” functional
    • New tool “counter_offer” functional
    • New tool “inspect_delivery” functional
    • New tool “report_vendor_status” functional
    • New tool “retrieve_deliverable” functional
    • New tool “state_purchasing_requirements” functional
    • New tool “submit_purchase_order” functional
    • “accept_offer” reworded the description of “id” cosmetic
    • “decline_offer” reworded the description of “id” cosmetic
    • “inspect_offer” reworded the description of “id” cosmetic
    • “release_payment” reworded the description of “id” cosmetic
    • “request_status” reworded the description of “id” cosmetic
    • “submit_request” reworded the description of “continuation” cosmetic
    • “submit_request” reworded the description of “need” cosmetic
    • “submit_request” reworded the description of “specifications” cosmetic
    • Tool “accept_offer” changed its title: accept offer → Accept an offer and place the order cosmetic
    • Tool “decline_offer” changed its title: decline offer → Decline an offer cosmetic
    • Tool “inspect_offer” changed its title: inspect offer → Inspect an offer's terms and thread cosmetic
    • Tool “release_payment” changed its title: release payment → Release a payment condition cosmetic
    • Tool “request_status” changed its title: request status → Check a request and its offers cosmetic
    • Tool “submit_request” changed its title: Send a requirement → Send Quarterline a requirement cosmetic
  • 8 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.

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://quarterline.forevenza.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=forevenza.com CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 c9598b64692343a9136c264deb429c68
SANs: forevenza.com, *.forevenza.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of quarterline.forevenza.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
forevenza.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
Header Value
content-security-policy default-src 'self'; script-src 'self' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self'; media-src 'self' blob:; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin
permissions-policy payment=(), camera=(), microphone=(), usb=(), serial=(), hid=(), bluetooth=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://quarterline.forevenza.com/mcp Verified 200
http (plaintext) http://quarterline.forevenza.com/mcp HTTPS enforced 301 https://quarterline.forevenza.com/mcp
MCP tools · 18 exposed · ~2,841 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
accept_offer ~123

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.

NameTypeReqDescription
acceptbooleanyes–
idstringyesThe request or offer id from your receipt or customer link
namestringyes–
organizationstring––
purchase_orderstring––
terms_sha256stringyes–
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

answer_remedy ~175

Accept 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.

NameTypeReqDescription
answerstringyes–
idstringyesThe request or offer id from your receipt or customer link
namestringyesName of the person making this for the buyer
notestring––
remedy_idstringyes–
terms_sha256stringyesExact terms_sha256 from inspect_offer; the act is refused if the terms have changed since
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

counter_offer ~242

Propose 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
namestringyesName of the person making this for the buyer
organizationstring–The buyer's organization
proposalobjectyesAt least one of quantities, counterparties, deliver_by, total_minor, payment or note
terms_sha256stringyesExact terms_sha256 from inspect_offer; the act is refused if the terms have changed since
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

decline_offer ~73

Decline an issued offer on its inspected terms.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
reasonstring––
terms_sha256stringyes–
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

describe_business ~122

What Quarterline does (Grease trap pumping for Austin restaurant groups, on one 90-day calendar: Put every grease trap your Austin group runs on one board against the City's 90-day ceiling, and request one calendar for all locations, one invoice and the manifests filed per location.), 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

edit_requirement ~133

Set 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.

NameTypeReqDescription
base_revisioninteger––
idstringyesThe requirement id from an earlier answer
op_idstring––
opsarrayyes–
tokenstringyesIts private token (also the receipt token of the request it is sent as); keep it private

No output schema declared.

No examples provided.

get_requirement ~87

A Quarterline 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.

NameTypeReqDescription
idstringyesThe requirement id from an earlier answer
tokenstringyesIts private token (also the receipt token of the request it is sent as); keep it private

No output schema declared.

No examples provided.

inspect_delivery ~208

Record 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
linesarrayyes–
namestringyesName of the person making this for the buyer
notestring––
portionstring–The portion inspected, as thread.fulfilment.portions names it
terms_sha256stringyesExact terms_sha256 from inspect_offer; the act is refused if the terms have changed since
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

inspect_offer ~134

Read 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

interpret_requirement ~180

Give Quarterline 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.

NameTypeReqDescription
requirementobject–The requirement to continue
timezonestring–The buyer's IANA time zone, for reading dates
turn_idstring–Your id for this message: a retry with the same id is applied once
utterancestringyesThe buyer's words, as written

No output schema declared.

No examples provided.

release_payment ~104

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

NameTypeReqDescription
confirmbooleanyes–
idstringyesThe request or offer id from your receipt or customer link
namestring––
paymentstringyes–
terms_sha256stringyes–
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

report_vendor_status ~198

Report 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.

NameTypeReqDescription
buyer_vendor_idstring––
documents_requestedarray––
idstringyesThe request or offer id from your receipt or customer link
namestringyesName of the person making this for the buyer
organizationstringyesThe buyer's organization
referencestringyesThe buyer's approval or case reference
statusstringyes–
terms_sha256stringyesExact terms_sha256 from inspect_offer; the act is refused if the terms have changed since
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

request_status ~103

Resume 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

retrieve_deliverable ~104

Retrieve 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

send_requirement ~165

Send the requirement to Quarterline 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.

NameTypeReqDescription
actionstring–What the buyer wants done (default quote): to buy, lease, verify...
contactobject––
idstringyesThe requirement id from an earlier answer
op_idstring––
revisionintegeryes–
tokenstringyesIts private token (also the receipt token of the request it is sent as); keep it private

No output schema declared.

No examples provided.

state_purchasing_requirements ~196

Tell 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
namestringyesName of the person making this for the buyer
organizationstringyesThe buyer's organization, whose purchasing this is
requirementsobjectyes–
terms_sha256stringyesExact terms_sha256 from inspect_offer; the act is refused if the terms have changed since
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

submit_purchase_order ~187

Send 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.

NameTypeReqDescription
idstringyesThe request or offer id from your receipt or customer link
namestringyesName of the person making this for the buyer
organizationstring–The buyer's organization
poobjectyes–
terms_sha256stringyesExact terms_sha256 from inspect_offer; the act is refused if the terms have changed since
tokenstringyesPrivate token from your receipt or customer link; keep it for later visits

No output schema declared.

No examples provided.

submit_request ~307

Send Quarterline a requirement (Grease trap pumping for Austin restaurant groups, on one 90-day calendar). Your board is recorded as a request and given a reference number, shown on screen when you send it. A person reviews the locations, trap sizes, frequencies, last pump-outs, current haulers and service windows you gave, and sources service from liquid waste haulers holding a City of Austin permit. The reply comes by email to the address you leave, with a proposed calendar for all your locations, how one invoice and per-location manifests would work, and a firm price for you to accept or decline. Nothing is scheduled, ordered or committed until you agree terms. Contact details are deleted after 180 days. 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.

NameTypeReqDescription
actionstring––
budgetobject––
contactobject––
continuationobject–The receipt id and token of an earlier request, to add to it instead of opening a new one
geographyobject––
needstringyesThe requirement in the buyer's own words
quantityobject––
requested_fieldsarray––
specificationsobject–Fields from the request_schema describe_business returns
timingobject––

No output schema declared.

No examples provided.

Install

How do I install the Quarterline: Grease trap pumping for Austin restaurant… MCP server?

Quarterline: Grease trap pumping for Austin restaurant… is a hosted endpoint at https://quarterline.forevenza.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 · quarterline.forevenza.com

# add to Claude Code
claude mcp add --transport http com-forevenza-services-quarterline 'https://quarterline.forevenza.com/mcp'
Common questions

What is the Quarterline: Grease trap pumping for Austin restaurant… MCP server?

Quarterline: Grease trap pumping for Austin restaurant… is an MCP server listed in the public MCP registry as com.forevenza.services/quarterline. Requests for grease trap pumping across Austin restaurant locations on one calendar and invoice. This page covers its hosted endpoint (https://quarterline.forevenza.com/mcp).

Is the Quarterline: Grease trap pumping for Austin restaurant… MCP server safe to use?

Quarterline: Grease trap pumping for Austin restaurant… scores 68 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 Quarterline: Grease trap pumping for Austin restaurant… MCP server expose?

Quarterline: Grease trap pumping for Austin restaurant… exposes 18 tools: describe_business, submit_request, interpret_requirement, get_requirement, edit_requirement, and 13 more. Their descriptions and schemas cost roughly 2,841 tokens of context every time the server is loaded.

Does the Quarterline: Grease trap pumping for Austin restaurant… MCP server require authentication?

No. We connected to Quarterline: Grease trap pumping for Austin restaurant… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Quarterline: Grease trap pumping for Austin restaurant… MCP server still maintained?

Quarterline: Grease trap pumping for Austin restaurant… 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 Quarterline: Grease trap pumping for Austin restaurant… MCP server?

VerifyMCP ran 13 checks on Quarterline: Grease trap pumping for Austin restaurant…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.