Skip to content

Stipple — Government Tenders MCP server

sh.stipple/stipple-tendersstipple.shstreamable-httpv0.1.1Scanned

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

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Stipple — Government Tenders MCP server can do

The Stipple — Government Tenders MCP server is published by stipple.sh, a domain the MCP Registry verified. It has 5 tools. It can create or change data (3 tools: match_tenders, tender_sources and buyer_awards), but cannot delete data. 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • buyer_awardsWhat a buyer has awarded, what is ending, and what they plan.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • match_tendersRank open tenders against what a company actually does.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • tender_sourcesEvery source we search, what it is allowed to do, and what the last run returned.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
Only reads 2Show 2 read-only tools
  • find_signalsSignals: what may be tendered before it is.No findings

    Why it is in this group

    • The name "find_signals" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • find_tendersSearch open tenders across Australia; New Zealand rows only when you ask for them (jurisdiction=NZ).1 finding

    Why it is in this group

    • The name "find_tenders" says "find": a word for reading.

    Findings

    • Info

      The description is 2,190 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...esult is empty: "no match in what we searched" is true, "there are none" is not."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.stipple.sh/mcp-tenders: tools/list returned 5 tools to an anonymous client, including match_tenders (write), tender_sources (write), buyer_awards (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,190 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...esult is empty: "no match in what we searched" is true, "there are none" is not."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http stipple-tenders https://www.stipple.sh/mcp-tenders
claude mcp add --transport http stipple-tenders https://www.stipple.sh/mcp-tenders

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__stipple-tenders__find_tenders",
      "mcp__stipple-tenders__find_signals"
    ],
    "ask": [
      "mcp__stipple-tenders__match_tenders",
      "mcp__stipple-tenders__tender_sources",
      "mcp__stipple-tenders__buyer_awards"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stipple-tenders. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/sh.stipple/stipple-tenders/verify?hash=6f25576ae03069c6f453f9820b0236934238b1bb5af92a64f669d28ddc94ac25" | jq -e '.changed == false'

Pinned hash 6f25576ae030, from Nov 21, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/sh.stipple/stipple-tenders/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for sh.stipple/stipple-tenders
[![Anlyon Radar](https://radar.anlyon.com/badge/sh.stipple/stipple-tenders.svg)](https://radar.anlyon.com/servers/sh.stipple/stipple-tenders)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

Stipple — Government Tenders MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Stipple — Government Tenders MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Stipple — Government Tenders MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Stipple — Government Tenders MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Stipple — Government Tenders MCP server have?

5 tools: 3 write, 2 read. match_tenders, tender_sources, buyer_awards, find_tenders and find_signals.

Does the Stipple — Government Tenders MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Stipple — Government Tenders MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Stipple — Government Tenders MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.