Connection check
verified live · 26h ago
stipple-tenders
Document forensics: tamper/AI checks, fields, tables, identity, screening, tenders, citations.
Tools
3
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http
Last checked
26h ago
Tools & capabilities
3 toolsRead from the running server on 26h ago.
find_tenders
read-only
qtierlimitsourcecategoryjurisdiction
+3
Search open government tenders across Australia and New Zealand. FREE — no credits. USE THIS WHEN someone asks what public-sector work is open: "any council drainage tende… Search open government tenders across Australia and New Zealand. FREE — no credits. 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, 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.
match_tenders
read-only
examplecompany_urljurisdictionclosing_before
Rank open tenders against what a company actually does. Costs 3 credits. USE THIS WHEN someone asks which opportunities suit a specific business: "what could we bid for",… Rank open tenders against what a company actually does. Costs 3 credits. 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, matches[], degraded, 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. 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.
tender_sources
read-only