Skip to main content
Glama

Stipple — Government Tenders

Server Details

Search AU/NZ government tenders and rank a shortlist against company capabilities.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 41 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Sketchjar/stipple-mcp
GitHub Stars
0
Server Listing
stipple-mcp

TDQS

A4.4/5.0

Scored across 5 tools

Disambiguation4/5

Each tool has a distinct primary intent: buyer-centric rollup (buyer_awards), forward-looking market signals (find_signals), open-tender search (find_tenders), company-specific ranking (match_tenders), and provenance (tender_sources). There is real overlap in output surface — buyer_awards and find_signals both return expiring contracts and planned procurements, and find_tenders and find_signals both surface upcoming/closing work — but the descriptions explicitly signpost when to use which, keeping misselection unlikely.

Naming Consistency4/5

find_signals, find_tenders, match_tenders follow a clean verb_noun pattern and share the tender/signal vocabulary. buyer_awards and tender_sources are noun-phrase forms rather than verb_noun, a minor deviation, but all five are lowercase snake_case and readable as a set.

Tool Count5/5

Five tools is well-scoped for a tender-discovery service: one search, one ranking, one forward-signal feed, one buyer-intel rollup, one transparency surface. Each tool has a clearly earned, non-redundant role and none feels like padding.

Completeness4/5

Core lifecycle is covered — discovering open tenders, anticipating upcoming ones, evaluating buyer history, matching to a company, and verifying coverage. Gaps remain: awards can only be viewed per-buyer (no market-wide award search, e.g. 'who won ICT contracts last year'), and there is no get-tender-by-id detail lookup despite results carrying ids and stipple_url.

Available Tools

5 tools
buyer_awardsContract awards and signals for a buyer
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
buyerNo
buyer_keyNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

find_signalsFind contract expiries and planned procurements
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
qNo
kindNo
buyerNo
limitNo
jurisdictionNo
window_beforeNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

find_tendersSearch AU/NZ tenders
Read-only
Inspect

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
qNo
kindNo
tierNo
limitNo
sourceNo
categoryNo
jurisdictionNo
closing_beforeNo
include_closedNo
first_seen_afterNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

match_tendersMatch tenders to a company
Read-only
Inspect

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.
ParametersJSON Schema
NameRequiredDescriptionDefault
exampleNo
company_urlNo
jurisdictionNo
closing_beforeNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

tender_sourcesList tender data sources
Read-only
Inspect

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.
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedfind_tenders1 field changed
      • addedInput schema / properties / kind
        Added value: +{
        +  "anyOf": [
        +    {
        +      "type": "string"
        +    },
        +    {
        +      "type": "null"
        +    }
        +  ],
        +  "default": null,
        +  "title": "Kind"
        +}
  2. 2 tool updates
    • Addedbuyer_awards
    • Addedfind_signals
  3. 1 tool update
    • Changedfind_tenders1 field changed
      • addedInput schema / properties / first_seen_after
        Added value: +{
        +  "anyOf": [
        +    {
        +      "type": "string"
        +    },
        +    {
        +      "type": "null"
        +    }
        +  ],
        +  "default": null,
        +  "title": "First Seen After"
        +}
  4. 3 tool updates
    • First observedfind_tenders
    • First observedmatch_tenders
    • First observedtender_sources

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to find, score, and monitor government contract opportunities across UK, EU, and US with AI-powered relevance scoring.
    2
    52 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables searching and analyzing government tenders, contract awards, and pre-tender pipelines from 21 official sources, with tools for tender search, award intelligence, and detailed notice retrieval.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.