Winquill MCP Server

by eshmere Your server? Claim it

not responding

Winquill is listed as active in the registry but did not answer our last check. It exposes 39 tools.

Public tenders and contract awards in the UK, US, Canada and EU, and help preparing bids.

Uptime history 32 days of history · worst day 0%

32 days agonow

0.0%

Uptime 24h

0 of 92 checks

Tools

read from the server

120 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 7

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

25 Oct 3 tools appeared automations, remove_from_pipeline, share_tender

25 Oct 3 tools changed the parameters they ask for assess_tender_fit, get_tender_details, save_company_profile

25 Oct a tool description was rewritten move_in_pipeline

Winquill does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tenda --transport http https://mcp.tenda.eshmere.ai/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.tenda.eshmere.ai/mcp

~/.codex/config.toml

[mcp_servers.tenda]
url = "https://mcp.tenda.eshmere.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tenda": {
      "url": "https://mcp.tenda.eshmere.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "tenda": {
      "type": "http",
      "url": "https://mcp.tenda.eshmere.ai/mcp"
    }
  }
}

Available tools 39

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

tenda

get_tenda_settings

Use this when the user asks which Tenda workspace ChatGPT uses, or which countries' tenders it shows: returns Tenda's settings in ChatGPT, the workspace (for someone in more than one) and the workspace's countries. Needs a Tenda account. Do not use for the company profile (use save_company_profile).

set_up_tenda

Use this when the user wants to set Tenda up for their company, or has just added Tenda and has no workspace yet: shows a short form in the chat for the company, where it works and the work it does, then how many open tenders fit it now. Needs a Tenda account. Do not use to change one fact the user names, such as a certification (use save_company_profile).

tenda_changes

Says when the team's work in a workspace last changed, for Tenda's app to keep its page up to date.

update_tenda_settings

Use this when the user wants ChatGPT to use another of their Tenda workspaces, or to show tenders from another country or stop: set "workspace" to the workspace's name, or a country's key from get_tenda_settings (such as "us") to true or false. The workspace's home country stays on. Owners and admins change countries. Needs a Tenda account.

bid

check_bid_readiness

Use this when the user wants to know what they're missing before bidding, for one tender or in general: registrations, certifications, insurance, policies and each country's own documents, such as Cyber Essentials in the UK, SAM.gov registration in the US or the DUME in France. A general check follows the user's home country. Returns what is held, missing or expiring. It gives readiness guidance, not legal advice. Not for Companies House look-ups or tax questions. Example: {"tender_reference":"003344-2026","documents_held":["cyber_essentials","iso_9001"]}

get_bid_draft

Use this when the user asks how a bid Tenda is drafting is going, or wants to read it: its progress in steps and answers written, each question with its word count and Tenda's mark out of 5, what's left for the team to confirm, and the check of the whole bid. Give question to read that answer in full. Once it's ready, it gives a Word file link that works for an hour, and a link to the draft in Tenda. Needs a Tenda account. Example: {"tender_reference":"012345-2026"}

update_bid_sprint

Use this when the user says a step of a bid their team is running is done, or not done after all: decode the pack, assign questions, draft answers, review and score, final checks or submit. Ticks it off with who did it and when, and says what is next and when it is due. Ticking submit moves the tender to Submitted. Needs a Tenda account and a bid sprint, which starts with a call to bid (record_bid_call). Do not use to write or check answers (use draft_bid_response or review_bid_draft).

tender

add_tender_documents

Use this when the user shares text from a tender's documents, or wants Tenda to read the files the buyer published with the notice (read_published, signed in). Returns a checklist of everything the bid must include, each with its file, page and the buyer's own words, and the requirements the notice leaves out, such as turnover, insurance and certifications. When the workspace can use Tenda's AI, it also returns the questions the buyer scores and how they're marked. Not for documents unrelated to a tender. Example: {"tender_reference":"012345-2026","read_published":true}

get_tender_details

Use this when the user asks about one tender, framework or standing offer, by notice ID, buyer reference or from earlier results: the deadline, the portal to submit through, lots, value, conditions, award criteria and what the buyer wants, in plain English. It also reads the competition: who holds the work now, what the buyer paid before, how many bids it drew, and whether the tender is worth chasing. Not for finding tenders (use search_tenders). Example: {"tender_reference":"012345-2026"}

get_tender_updates

Use this when the user asks what's new from their Tenda watches: new matching tenders, pipeline notices, deadline changes, clarifications, cancellations and awards. Without since, it gives the updates not shown before and marks them seen. Agents that check on a schedule pass since, the nextSince from the answer before: it reads what was recorded after it, oldest first, and marks nothing. watch_id keeps to one watch. Needs a Tenda account. Not for searching (use search_tenders). Example: {"since":"eyJzZXEiOjQyfQ"}

open

open_bid_panel

Opens the team's live bids beside a chat: each bid's steps and questions, what scores, and a way to work on one in the chat.

open_tenda

Opens Tenda's own app from ChatGPT's sidebar: Today, the team's board, Find and each tender, with the bid call. The app moves between its pages itself.

pipeline

add_to_pipeline

Use this when the user wants to save a tender to their team's Tenda pipeline to consider bidding, e.g. "add this to our pipeline" or "let's track the Falkirk cleaning framework". Adds it in Watching, ready for the bid or no-bid call, and says which e-tendering portal the tender is run on. Until the team has said whether it has an account on that portal, the answer asks; pass the question on, and record the reply with record_portal_account. Needs a Tenda account and workspace. Do not use for alerts about new tenders (use watch_tenders) or to record a decision to bid (use record_bid_call).

get_pipeline_status

Use this when the user asks how their team's bids are going, for a status report, or what is due: how many tenders are in each stage of their Tenda pipeline, which bids are running with their next step and due date, which tenders still need the bid or no-bid call, and which bids are waiting on a result. Needs a Tenda account and workspace. Do not use to find new tenders (use search_tenders) or for alerts from saved watches (use get_tender_updates).

record

record_bid_call

Use this when the user's team has decided whether to bid: records the bid or no-bid call, the team's answers to Tenda's five questions and the reason. A bid moves the tender to Bidding and plans a six-step sprint back from the deadline; a tender not in the pipeline is added first. Confirm the decision with the user before calling. Needs a Tenda account and a role that makes bid calls. Not for judging fit before the call (use assess_tender_fit). Example: {"tender_reference":"012345-2026","decision":"bid","answers":{"fit":"yes"}}

record_portal_account

Use this when the user says whether their company has an account on the e-tendering portal a tender is run on, where suppliers get the tender pack and bid, often after Tenda asked as a tender joined the pipeline: "yes, we have an EU-Supply account" or "no, we're not on Atamis yet". Notes it for the whole team, so Tenda stops asking about that portal. Give the tender's reference, or the portal's name or the key Tenda gave (portal.key). Needs a Tenda account and workspace. Do not use to sign in to a portal: Tenda never handles portal passwords.

assess

assess_tender_fit

Use this when the user asks whether their business should bid for a public contract, or which open tenders suit them best. Compares the tender's conditions of participation (turnover, insurance levels, experience and certifications), location and lot sizes with the company's profile, and returns a fit score with reasons, likely disqualifiers and gaps. Omit tender_reference to rank the open tenders that suit the company. It does not predict or guarantee an award. Do not use for general business strategy or for private-sector sales leads.

assign

assign_task

Use this when the user gives work on a team bid to someone, or takes it on: "give the Bristol bid call to Sam". The work is the bid call while a tender waits in Watching or Qualifying, or a sprint step, the next one unless named. Says who has it and whether they heard in Slack. When the person's role can't do it, the answer says who can: ask the user before choosing one. Needs a Tenda account and workspace. Not for ticking off a step (use update_bid_sprint) or the call itself (use record_bid_call). Example: {"tender_reference":"012345-2026","person":"Sam","task":"review"}

automations

automations

Use this when the user wants Tenda to do something on its own, again and again: add strong fits to the pipeline, remind people of sprint steps, check a bid before it closes, say what a buyer changed, or send a morning shortlist or a report. Before turn_on, read the rules back to the user in plain words and ask them to confirm. Automations never submit a bid, write to a buyer, decline a tender, email anyone outside the team or change who is in the workspace. Needs a Tenda account. Example: {"action":"add","template":"morning_shortlist"}

choose

choose_alerts

Use this when the user wants to change which Slack and Teams channels get Tenda's alerts, or asks where they go: "stop the morning summary in Slack". Change only what the user asked for; with neither send nor stop it changes nothing and says where alerts go now. Owners and admins can change alerts. Needs a Tenda account and workspace. Not for connecting a channel (Tenda dashboard, Settings, Connections) or for email alerts (use watch_tenders). Example: {"app":"slack","stop":["morning_summary"]}

company

find_company

Finds a UK company on Companies House by name, for Tenda's setup.

continue

continue_bid_draft

Use this to carry on a bid draft Tenda started with start_bid_draft: give it the buyer's questions it asked for, the team's answers to the questions Tenda asked, or the go-ahead to draft now with what it has (Tenda marks the gaps [TO CONFIRM]). Drafting starts once Tenda's questions are answered, or when draft_now is true. Pass each answer with the question's number or words. Needs a Tenda account. Do not use for a new bid (use start_bid_draft).

contract

search_contract_awards

Use this to find who won public contracts in the UK, Canada, the United States, Germany, France and the rest of the EU, what a buyer paid last time, and which contracts end soon and may be re-tendered. Searches the user's own countries unless they name one. Answers give the total, pass nextCursor back as cursor for more, and summarise says who won most across every match. Not for tenders open now (use search_tenders) or a public body's total spending. Example: {"buyer":"Leeds City Council","query":"cleaning","summarise":"supplier"}

coverage

get_coverage

Use this to know where Tenda looks: the countries and sources it reads, how many open, upcoming and awarded notices each holds, and when each was last read. Use it before telling the user a tender isn't published anywhere Tenda reads, or to say how fresh results are. Not for searching (use search_tenders). Example: {"country":"Canada"}

draft

draft_bid_response

Use this when the user wants help writing part of a response to a public tender: a quality question answer, social value response, method statement, case study, company overview, cover letter or clarification question. Returns a drafting brief built from the tender's award criteria, word limits and the user's facts, so the draft answers what evaluators will score. Write the draft from the brief. Do not use for job applications, grant applications or private-sector sales proposals.

finish

finish_setup

Saves what Tenda's setup was told, making the workspace for someone without one, and finds the open tenders that fit.

from

remove_from_pipeline

Use this when the user wants a tender taken off their team's Tenda pipeline, for good or until a change brings it back: "remove it until it gets a value". It deletes the tender's bid call, sprint and the files the team added; for one in Bidding, Submitted, Won or Lost the answer asks first, so confirm with the user and call again with confirmed. Needs a Tenda account and workspace. Not for moving a tender to another stage (use move_in_pipeline) or a no-bid call (use record_bid_call). Example: {"tender_reference":"012345-2026","return_when":"value"}

mentions

search_mentions

Finds the team's tenders and people by name, for @ mentions in ChatGPT.

move

move_in_pipeline

Use this when the user wants to change where a tender stands in their team's Tenda pipeline: to Qualifying while they look into it, back to Watching, to Submitted, or to Won or Lost when the buyer announces the result. Moving to Bidding or No bid takes the bid or no-bid call (use record_bid_call). Needs a Tenda account and workspace. Do not use to take a tender off the pipeline (use remove_from_pipeline).

review

review_bid_draft

Use this when the user has a draft answer for a public tender and wants it checked before submission, the way an evaluator would: word limit, every part of the question answered, specific evidence, firm commitments, no unfinished placeholders or empty superlatives, and what the section type needs (mobilisation, KPIs, measurable social value). Returns checks plus the tender's scoring criteria and a 0 to 5 rubric to score it against. Do not use to write a new answer (use draft_bid_response).

rewrite

rewrite_bid_answer

Use this when the user wants Tenda to rewrite one answer in a bid it drafted, e.g. "make Q3 shorter" or "use the Glasgow contract as the example in 2.1". Tenda rewrites it in the background, marks it again and says when it's done. A bid's first ten rewrites are included; after that each uses a little of the workspace's allowance. Needs a Tenda account. Do not use before the draft is ready.

save

save_company_profile

Use this when the user wants Tenda to remember their business for searches, fit and readiness checks and drafting. Fill in only company facts the user has told you, leaving out anything unsure and any personal details, and show the user what you'll save so they can confirm or correct it first. Saves to their team's workspace and fills in more from Companies House (SAM.gov for a US company) and contracts the company has won. Needs a Tenda account. Not for personal profiles or CVs. Example: {"summary":"Office and school cleaning in Greater Manchester","company_number":"08123456"}

share_tender

Use this when the user wants to share a tender or send someone its link. Returns a link anyone can open without signing in: it shows what the public notice says, and chat apps preview it with the tender's name, value and closing date. Give the link as it is. Nothing about the user or their workspace is in the link or on the page.

start

start_bid_draft

Use this when the user wants Tenda to write a whole bid for their team: it asks a few questions, drafts every answer from the company's evidence, then marks and revises them. Relay Tenda's questions as they are. A whole bid uses one of the month's full bids, so first call it without confirmed, tell the user how many are left and offer to write it here with draft_bid_response, which uses none; call again with confirmed only if they choose Tenda. notify says where to hear when it's ready. Needs a Tenda account and workspace. Example: {"tender_reference":"012345-2026"}

stop

stop_watch

Use this when the user wants to stop one of their Tenda watches, by the watchId that watch_tenders or list_watches gave. It finds nothing new after that; what it already found still shows in get_tender_updates. Needs a Tenda account. Example: {"watch_id":"wch_abc123"}

tenders

search_tenders

Use this to find public sector contracts to bid for in the UK, Canada, the United States, Germany, France and the rest of the EU: open tenders, frameworks and upcoming notices from any public buyer. Searches the user's own countries unless they name one; get_coverage lists every source and when it was last read. Answers give the total; pass nextCursor back as cursor for more. Not for past winners (use search_contract_awards) or jobs. Example: {"query":"school cleaning","region":"North West","closing_within_days":30}

watch

watch_tenders

Use this when the user wants alerts for new tenders or upcoming notices that match a search, or for changes to one tender they follow (clarifications, new deadlines, the award). Saves a watch and gives its watchId: matches show in get_tender_updates and, with notify, in the workspace's Slack or Teams channels that get changes. Needs a Tenda account. Not for seeing the user's watches (use list_watches) or stopping one (use stop_watch). Example: {"query":"office cleaning","include_upcoming":true}

watches

list_watches

Use this when the user asks which Tenda watches they have, or to find the one to stop: each watch with its ID, what it watches for, its countries and whether it posts to Slack or Teams. Needs a Tenda account. Do not use for what the watches found (use get_tender_updates). Example: {}

winning

add_winning_bid

Use this when the user shares a bid their company won, for Tenda to learn from, e.g. after Tenda offers to learn from winning bids. Tenda keeps it in the workspace's Library and learns what worked in it (structure, tone, the evidence it uses) for the bids it drafts. Pass the bid's text as the user shared it, not a link. Needs a Tenda account and workspace. Do not use for the buyer's questions for a new bid (use start_bid_draft or continue_bid_draft).

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.tenda.eshmere.ai/mcp	streamable-http	answering	120 ms	0 min ago

Alternatives to Winquill

same job, measured the same way

TenderSignal

by co-tendersignal

UK and Ireland public sector tenders, contract awards, buyers and expected re-tenders.

answering

UK Data: UK public tenders

by co-reliness

UK public sector tenders and contract awards from Find a Tender: values, buyers, winners, deadlines

1 tools answering

Open Contracting

by pipeworx-io

Open Contracting MCP — international public procurement: government tenders and contract awards…

346 installs/wk 48 tools answering

MCP Public Award Monitor

by mambabuilt

Find the companies that won US or UK public contracts, grants or SBIR awards in a window.

272 installs/wk local only

Arquestra Consulting Market Radar

by arquestra

Public consulting tenders and awards in Europe: who wins, open calls, firms and buyers

6 tools answering

Public Tenders (EU TED)

by kiskecske24

Search open EU public tenders and contract awards on TED by keyword, CPV, country and deadline.

answering

EU Tender Award Winners (TED)

by pcp183

See who wins EU public contracts (TED award notices). $0.03/call via x402.

1 tools answering

Polish Public Tenders

by contentwriterco

Polish public procurement for AI agents: BZP and TED tenders, awards, buyers and contractors.

9 tools answering

Winquill — questions

Answers built from our own checks of this server.

What can Winquill do?

It exposes 39 tools, read directly from the server on our last check. Among them: add_tender_documents, add_to_pipeline, add_winning_bid, assess_tender_fit, assign_task, automations and 33 more. 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 →

What is Winquill mostly used for?

Its tools cluster around tenda, tender and bid. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Winquill working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 120 ms. The bar chart above shows every period we have measured.

The registry lists Winquill as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Winquill?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Winquill need an API key?

No. Winquill completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 39 of them are readable on this page. This is what we observed, not what the docs claim.