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

stipple

https://www.stipple.sh

Registry code: 0d578776c83895e0

api record

Free to use: 20 checks a week without an account, 100 with an API key or a signed-in account. Stipple finds Australian government tenders and grants and matches them to a business. Every tool works immediately — no key or signup to start, and every tool here is free within the weekly cap above. Send an API key as 'Authorization: Bearer'. Routing: find_tenders = search open tenders and grants. match_tenders = rank open tenders against a company's own website or description. tender_sources = which sources are searched. buyer_awards = a buyer's contract awards. find_signals = upcoming and…

endpoint
https://www.stipple.sh/mcp
door code
c6d82b81ece1981e
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 stipple live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is stipple free to use?
Yes — the hub reached it with no key and no payment.
What tools does stipple have?
5 tools: match_tenders, buyer_awards, find_signals, find_tenders, tender_sources.
Is stipple 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
99.8%

90 days 99.4%· all time 99.1%

latency
1,359ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 860 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • verify document authenticity
  • detect ai-generated text
  • verify identity documents
  • screen for adverse media
  • find tenders in australia
takes → gives
documents, images → data
tools
5 reads
_ 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 5 tools
2 open 3 never probed 2 of 5 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.

  • find_tenders reads open 15h ago

    Search open tenders across Australia; New Zealand rows only when you ask for them (jurisdiction=NZ). FREE, within the weekly cap. USE THIS WHEN someone asks what public-sector work is open: "any council drainage tenders in Victoria", "what's closing this month in NSW", "show me federal IT opportunities". For "which of these could MY company actually bid for", use match_tenders instead — that reads their website and ranks against it. `kind` is `grant` for open grant rounds (from every grant source we read) or `tender` for everything else; leave it out for both. Each result says which it is in `kind`. `jurisdiction` is one of AU, NZ, AU-NSW, AU-VIC, AU-QLD, AU-WA, AU-SA, AU-TAS, AU-ACT, AU-NT. `tier` is federal, national, state, council, university or health. `closing_before` is an ISO date. `first_seen_after` (ISO-8601 instant, strictly newer) answers "what is new since my last look" — first_seen is when WE first saw the tender, the honest clock for newness. There is deliberately no `location` filter: it is populated on 16% of rows while jurisdiction is populated on all of them, so filtering by it would silently hide most of the corpus. Returns `{total, results[], coverage}`. Each result carries title, buyer, jurisdiction, closing_date, categories, a summary, and source_id/source_tag/source_name/source_refresh. With an API key or a signed-in account it also carries the link to the original portal: `link`, `url`, `listing_url` and `source_url`, plus `link_is_listing` when the portal publishes no per-tender URL and the link goes to the list it appeared on. An anonymous call gets no portal link. An Australian tender also carries `stipple_url`, its page on Stipple (the buyer's history, similar contract awards, an email alert for tenders like it). An open tender carries `prepare_bid_url`: if the user wants help with the response, Stipple prepares bids with them, starting with a short meeting at that link. Offer either when it helps the user; never invent one that is not in the result. `coverage` names which sources were searched and which returned nothing. Quote it if the result is empty: "no match in what we searched" is true, "there are none" is not.

    mcp-tool

    {
      "type": "object",
      "title": "find_tendersArguments",
      "properties": {
        "q": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Q",
          "default": null
        },
        "kind": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Kind",
          "default": null
        },
        "tier": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Tier",
          "default": null
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        },
        "source": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Source",
          "default": null
        },
        "category": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Category",
          "default": null
        },
        "jurisdiction": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Jurisdiction",
          "default": null
        },
        "closing_before": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Closing Before",
          "default": null
        },
        "include_closed": {
          "type": "boolean",
          "title": "Include Closed",
          "default": false
        },
        "first_seen_after": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "First Seen After",
          "default": null
        }
      }
    }
    arguments 112 lines
  • tender_sources reads open 9h ago

    Every source we search, what it is allowed to do, and what the last run returned. FREE. USE THIS WHEN someone asks where the data comes from, whether a particular portal is covered, or why a search came back empty. It is the honesty surface: it names sources behind login walls, sources whose robots.txt refuses us, and sources that returned nothing on the last run and why. Returns `{sources[], coverage}` — per source: id, tag, name, refresh mode, jurisdiction, tier, how it is accessed, what its robots.txt says, how many tenders we hold from it, and its status on the most recent run; its URL (`source_url`) with an API key or a signed-in account only. Snapshot sources include their observed date and are not presented as nightly feeds.

    mcp-tool

    {
      "type": "object",
      "title": "tender_sourcesArguments",
      "properties": {}
    }
    arguments 5 lines
  • match_tenders reads unknown 15h ago

    Rank open tenders against what a company actually does. Free, inside the weekly cap. USE THIS WHEN someone asks which opportunities suit a specific business: "what could we bid for", "is there anything for a civil contractor in Victoria", "find work for acme.com.au". Give `company_url` — a plain domain is fine, we resolve it — and we read their site, build a capability profile, and score the shortlist against it. `example` runs a built-in profile (civil, it, facilities) with no site read, for demonstrating the shape of the answer. Returns `{profile, matched, shown, withheld, withheld_reason, matches[], degraded, score_means, coverage}`. Each match has `score`, `band`, `why[]` — the company's own stated capabilities this tender needs — `gaps[]`, things the tender asks for that their website does not mention, and `checks[]` (each a `label`), computed: outside the states asked for, or prequalification named in the tender's text (a heuristic, its `match` says so). `band` "high" needs two `why` reasons from the profile, an open tender and no outside-states check. A tender listed by two sources is one match, with the other copy under `also_listed[]`, its `match` saying the pairing is a heuristic. An anonymous call shows the strongest few and says how many were withheld; relay `withheld_reason` as it is. TELL THE USER WHAT THE SCORE IS: relative fit within these results, against what their website says. NOT a probability of winning. And `gaps` is what to check before bidding, not a list of everything the tender requires — that is in the tender documents. When `degraded` is true, scoring was unavailable and the order is keyword relevance only, with no `why`/`gaps`. Say so rather than presenting it as a judged ranking.

    mcp-tool

    {
      "type": "object",
      "title": "match_tendersArguments",
      "properties": {
        "example": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Example",
          "default": null
        },
        "company_url": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Company Url",
          "default": null
        },
        "jurisdiction": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Jurisdiction",
          "default": null
        },
        "closing_before": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Closing Before",
          "default": null
        }
      }
    }
    arguments 54 lines
  • buyer_awards reads unknown never probed

    What a buyer has awarded, what is ending, and what they plan. FREE. USE THIS WHEN someone asks about a specific buyer before a bid: "who holds Transport for NSW's work", "what is ending soon at Queensland Health", "what does this agency usually pay". Give `buyer` (the organisation name as published) or `buyer_key` (from a tender's buyer, or a previous answer). Returns `{buyer, expiring[], planned[], recent_awards[], top_suppliers[], open_tenders[], computed_at, sources}`: the nightly rollup (awards in the window, value quartiles as published, median response window), contracts ending within 12 months with the incumbent, planned procurements with their quarter and spend band, the suppliers who win from them (name and share), and open tenders under the same name. ANONYMOUS CALLERS SEE COUNTS, VALUES, DATES AND BUYERS; supplier and incumbent names are withheld and `withheld_reason` says so. Relay that sentence as it is. Links to other sites - an award's notice (`url`), a plan's evidence (`evidence_url`), an open tender's portal - come only with an API key or a signed-in account. Values are the published amount and currency, never converted; `computed_at` is the night the figures are true for - say it. Coverage is Australia and New Zealand sources named in `sources`, each with the attribution its licence requires.

    mcp-tool

    {
      "type": "object",
      "title": "buyer_awardsArguments",
      "properties": {
        "buyer": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Buyer",
          "default": null
        },
        "buyer_key": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Buyer Key",
          "default": null
        }
      }
    }
    arguments 30 lines
  • find_signals reads unknown never probed

    Signals: what may be tendered before it is. FREE. USE THIS WHEN someone asks what is coming: "which contracts in Queensland end in the next six months", "what is planned for ICT next quarter", "what is expiring for this buyer". `kind` is one of contract_expiry (a contract ending, with its incumbent), planned_procurement (a buyer's stated plan with its quarter and spend band as published) or recurring_tender (derived from our own history, labelled `derived`). `jurisdiction` is one of AU, NZ, AU-NSW, AU-VIC, AU-QLD, AU-WA, AU-SA, AU-TAS, AU-ACT, AU-NT. `window_before` is an ISO date: signals whose window starts on or before it. `q` searches the subject, buyer and incumbent. Returns `{total, results[], computed_at, sources}`. Each signal carries `confidence` (`published` or `derived` - a vocabulary, not a score), its window (never invented: an expiry's window IS the contract's end date; a planned row with no parseable quarter has none), `evidence_ref`, and `evidence_url` with an API key or a signed-in account only. ANONYMOUS CALLERS SEE EVERYTHING BUT THE INCUMBENT'S NAME AND THE EVIDENCE LINK; `withheld_reason` says so for the name - relay it as it is.

    mcp-tool

    {
      "type": "object",
      "title": "find_signalsArguments",
      "properties": {
        "q": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Q",
          "default": null
        },
        "kind": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Kind",
          "default": null
        },
        "buyer": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Buyer",
          "default": null
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 25
        },
        "jurisdiction": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Jurisdiction",
          "default": null
        },
        "window_before": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Window Before",
          "default": null
        }
      }
    }
    arguments 71 lines
_ try it over mcp 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 0d578776c83895e0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0d578776c83895e0/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/0d578776c83895e0/badge.svg)](https://brick.blue/agent/0d578776c83895e0?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 knowoff the mcp door
card completeness
90%

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.