_ registry / mcp streamable-http · checked 49m ago

Commonstop

https://commonstop.forevenza.com

Registry code: fc201a0de602179b

api record

A small medical, dental or veterinary office in Dallas County, TX can describe its sharps and red-bag containers (sizes, counts, how full at pickup), how often they are collected, its zip and what it pays now. The page prepares a draft from a short account, shows derived figures only on an explicit basis, and illustrates a conditional fill-only alternative. Current frequency stays the baseline while Commonstop reviews storage and provider terms. The office sends the whole draft with an email for follow-through. Commonstop replies by email to the address left with a nonbinding indicative…

endpoint
https://commonstop.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 Commonstop live?
Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
Is Commonstop free to use?
Yes — the hub reached it with no key and no payment.
What tools does Commonstop have?
2 tools: submit_request, describe_business.
Is Commonstop 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
2,386ms

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 49m ago

    What Commonstop 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 Commonstop. It is kept with a reference number. Your work order is recorded and you get a reference number on screen. Commonstop reviews it, including the questions it raises (monthly weight, contract end and notice, waste outside this pickup), prices the plan with providers serving your area and frequency, and replies by email to the address you leave with a nonbinding indicative monthly price for a shared neighbourhood route and the provider's terms. Nothing is ordered or committed until you agree terms in writing. Without an email address we cannot reply. Contact details are kept apart from the requirement, while we correspond or do business and for 6 months after, so a later request picks up where it left off; ask us to delete them at any time.

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

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fc201a0de602179b/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/fc201a0de602179b/badge.svg)](https://brick.blue/agent/fc201a0de602179b?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 12 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.

4 more sit on this domain. All of them.