mcpbeat Sign in

Stipple — Government Tenders MCP Server

answering

Stipple — Government Tenders is answering right now. Last checked 11 min ago. It exposes 5 tools. Last commit 30 Aug 2026.

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

Uptime history 22 days of history
22 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
1220 ms
Response time
average over 24h
0
Stars
last commit 30 Aug 2026

What changed 10

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 August 2026. No other catalogue keeps this.

15 Sep 2 tools appeared buyer_awards, find_signals
15 Sep 2 tool descriptions were rewritten find_tenders, match_tenders
10 Sep 2 tool descriptions were rewritten find_tenders, match_tenders
2 Sep a tool description was rewritten find_tenders
2 Sep a tool changed the parameters it asks for find_tenders
31 Aug 2 tool descriptions were rewritten find_tenders, tender_sources

Nothing serious here today

Today is the operative word: we check Stipple — Government Tenders every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add stipple-tenders --transport http https://www.stipple.sh/mcp-tenders
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "stipple-tenders": {
      "url": "https://www.stipple.sh/mcp-tenders"
    }
  }
}
~/.codex/config.toml
[mcp_servers.stipple-tenders]
url = "https://www.stipple.sh/mcp-tenders"
.cursor/mcp.json
{
  "mcpServers": {
    "stipple-tenders": {
      "url": "https://www.stipple.sh/mcp-tenders"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "stipple-tenders": {
      "url": "https://www.stipple.sh/mcp-tenders"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

buyer
buyer_awards
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. 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.
match
match_tenders
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 — and `gaps[]`, things the tender asks for that their website does not mention. 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.
signals
find_signals
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`. ANONYMOUS CALLERS SEE EVERYTHING BUT THE INCUMBENT'S NAME; `withheld_reason` says so - relay it as it is.
tender
tender_sources
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, URL, 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. Snapshot sources include their observed date and are not presented as nightly feeds.
tenders
find_tenders
Search open tenders across Australia and New Zealand. 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. `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, a link, and source_id/source_tag/source_name/ source_url/source_refresh — plus `link_is_listing` when the portal publishes no per-tender URL and the link goes to the list it appeared on. `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.

Endpoints

URLTransportStateLatencyChecked
https://www.stipple.sh/mcp-tenders streamable-http answering 1545 ms 11 min ago

Alternatives to Stipple — Government Tenders

same job, measured the same way
Government Tenders
by dataleadspro

Search government tenders and public procurement opportunities with structured results.

1 tools answering
Tender MCP
by ojaskord

Government tender search for AI agents. UK, EU and US procurement opportunities.

111 installs/wk 2 tools answering
IndoTender
by indotender

Indonesian government procurement — LPSE tenders, Inaproc data, and company profiles.

answering
Stayportland
by stayportland

Search Portland rentals, compare homes, save a shortlist, and get a live quote. No payments.

11 tools answering
PNCP
by mcp-dir

Search Brazilian government tenders and public procurement (PNCP): find notices and auctions by keyw

19 tools answering
Vietnam Government Tenders
by indotender

Search Vietnam National E-Procurement System records, packages, participants, and awards.

answering
GovRider
by carlosahumada89

Match tech products and consulting services to live government tenders, grants, and RFPs

42 installs/wk local only
Canonical Company Search
by trycanonical

Verified, long-tail company search: describe what you want, get an LLM-verified company shortlist.

answering

Stipple — Government Tenders — questions

Answers built from our own checks of this server.

What can Stipple — Government Tenders do?
It exposes 5 tools, read directly from the server on our last check. Among them: buyer_awards, find_signals, find_tenders, match_tenders, tender_sources. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Stipple — Government Tenders working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1220 ms. The bar chart above shows every period we have measured.
How do I connect Stipple — Government Tenders?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Stipple — Government Tenders need an API key?
No. Stipple — Government Tenders completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Stipple — Government Tenders?
It answers our handshake in 1220 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Stipple — Government Tenders open source?
Yes — it is published under the MIT licence, written in Dockerfile and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.