MCP integration

1. Sign in — every checker is free under a weekly limit.
2. Open Your company → Account → Developer access and create a connector URL. Paste it into your agent's MCP connection settings. Clients that support headers can use an account API key instead.
3. List the tools, then try tender_sources to check the connection — it is unmetered. A free tool succeeding does not confirm access to the rate-limited tools.
4. Run the tool you need. If you hit the weekly limit, the reply says when it resets.

A sign-in error means the connection needs your account credentials. A rate-limit error names when it resets. Repeated retries will not resolve either.

Everything lives on https://www.stipple.sh/mcp (Streamable HTTP), listed in the official MCP registry as sh.stipple/openwarrant:

https://www.stipple.sh/mcp-tenders serves the five tender and intelligence tools alone (registry id sh.stipple/stipple-tenders); /mcp-aitext, /mcp-verify and /mcp-plagiarism serve one checker each. Same implementations, same limits; a new install wanting everything uses /mcp.

The bid workspace's own agent talks to a separate gateway, /mcp-bidline, with a key scoped to one bid run: it reads the bid's documents and requirements and records findings. It is not a public install; the workspace connects it for you when you prepare a response.

Customize → Connectors → + → Add custom connector. Name it, paste your connector URL from the account page (Account → MCP → Create connector URL; it looks like https://www.stipple.sh/mcp/c/…) as the remote MCP server URL, leave the OAuth fields empty, and add. The plain https://www.stipple.sh/mcp also connects, for the free tools only. Free accounts get one custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors first. The tools then appear in a conversation's tools menu.

Turn on Developer mode in ChatGPT settings (the menu it sits under has moved between releases — search settings for the phrase; availability can depend on workspace policy). Then create a connector: a name and description, Connection → Public endpoint, and your connector URL from the account page (https://www.stipple.sh/mcp/c/…) — or the plain https://www.stipple.sh/mcp for the free tools only. ChatGPT lists the tools it discovered.

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

To use the metered tools, attach your account's key on the same command: --header "Authorization: Bearer stp_…". The key is on your account page after a sign-in.

Seven tools need no account from any client: find_tenders, buyer_awards, find_signals, tender_sources, check_document, get_warrant and submit_feedback. Anonymous calls to the two intelligence tools get counts, values, dates and buyers; the supplier and incumbent names arrive with a key or a session. The metered tools — detection, references, source overlap, verification, extraction, screening, tender matching, identity and pack checks — need a signed-in account's key (free, no card), sent as an Authorization: Bearer header.

The step-by-step version per client, with what to ask once connected, is in Connect an MCP server to ChatGPT and Claude.

Add to your client's MCP configuration:

{
  "mcpServers": {
    "stipple": { "type": "http", "url": "https://www.stipple.sh/mcp" }
  }
}

For tenders and intelligence alone, https://www.stipple.sh/mcp-tenders; the other scoped servers are listed above. New installs wanting everything should just use /mcp.

The document tools accept a public url — the cheapest call: one short string, no download or encoding — or inline base64 (bytes_b64); the identity and pack checks take a documents list; the text tools take raw text or a url.

# In any connected client, just ask:
"What council road tenders are open in Queensland?"
"Which of these could we bid for? Our site is example.com.au"
"Who holds Transport for NSW's contracts, and what is ending soon?"
"What is planned for ICT in Queensland next quarter?"
"Fact-check this report: https://example.com/report.pdf"
"Is this payslip genuine? <attached file>"

verify_references returns a shareable permalink with every result, so an agent can hand its user a public fact-check record. Each server also publishes MCP prompts (ready-made starters like "Fact-check a report URL") that appear natively in clients that support them.

• Same per-IP rate limits as the REST API (the tools share one quota).
• Outbound URL fetches are SSRF-guarded: public http(s) hosts only, every redirect re-validated, size-capped.
• Transport is stateless Streamable HTTP with JSON responses — no session affinity required.

Agents can also discover the service through agents.md and llms.txt, or call the REST API directly.