_ registry / mcp streamable-http · checked 2h ago

Quarterline

https://quarterline.forevenza.com

Registry code: e5c5c87f7c9503ff

api record

At quarterline.forevenza.com an Austin restaurant or multi-location operator lists each location's trap type and size, address or area, current pump-out frequency, last pump-out, current hauler, what they pay per service now (optional) and preferred service windows, sees them on a 12-month board against the City's 90-day ceiling, and sends it as a request. The request gets a reference number; a person reviews it, sources service from liquid waste haulers holding a City of Austin permit, and replies by email with a proposed calendar, how one invoice and per-location manifests would work, and a…

endpoint
https://quarterline.forevenza.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Quarterline live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is Quarterline free to use?
Yes — the hub reached it with no key and no payment.
What tools does Quarterline have?
2 tools: submit_request, describe_business.
Is Quarterline safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
907ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 open 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • describe_business open 2h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • submit_request unknown never probed

    Send a requirement to Quarterline. It is kept with a reference number. 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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "need"
  ],
  "properties": {
    "need": {
      "type": "string",
      "maxLength": 2000
    },
    "action": {
      "enum": [
        "buy",
        "source",
        "quote",
        "verify",
        "lease",
        "license",
        "hire",
        "retrieve",
        "convert",
        "other"
      ],
      "type": "string"
    },
    "budget": {
      "type": "object",
      "required": [
        "amount"
      ],
      "properties": {
        "per": {
          "type": "string"
        },
        "amount": {
          "type": "number"
        },
        "currency": {
          "type": "string"
        }
      }
    },
    "timing": {
      "type": "object",
      "properties": {
        "text": {
          "type": "string"
        },
        "latest": {
          "type": "string"
        },
        "earliest": {
          "type": "string"
        }
      }
    },
    "contact": {
      "type": "object",
      "properties": {
        "name": {
          "type": "string"
        },
        "email": {
          "type": "string"
        },
        "organization": {
          "type": "string"
        }
      }
    },
    "quantity": {
      "type": "object",
      "required": [
        "amount",
        "unit"
      ],
      "properties": {
        "per": {
          "type": "string"
        },
        "unit": {
          "type": "string"
        },
        "amount": {
          "type": "number"
        }
      }
    },
    "geography": {
      "type": "object",
      "properties": {
        "text": {
          "type": "string"
        },
        "country": {
          "type": "string"
        }
      }
    },
    "specifications": {
      "type": "object",
      "propertyNames": {
        "type": "string"
      },
      "additionalProperties": {}
    }
  }
}
    arguments 109 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e5c5c87f7c9503ff.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e5c5c87f7c9503ff/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e5c5c87f7c9503ff/badge.svg)](https://brick.blue/agent/e5c5c87f7c9503ff?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on forevenza.com 7 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.