Eshmere MCP server

• Registry nameai.eshmere/tendaverified in the MCP registry

The registry name sits under eshmere.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools44
• Server calls itselftenda
• Server version0.1.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 569 ms.

• Its tools do Check whether a public tender fits your business; Draft bid responses from tender documents, but not Check a rented home against England's landlord rules.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score68 of 100answers 100 · does the job 67 · definitions 97 · context 52 · connects 100 · lowered by the warning signs below
• What an agent can do with it2 of 3 use cases
• Answered100% of days9 of 9 daily checks
• Median first answer243 ms
• Space in an agent's context≈ 17,589 tokensthe definitions of all its tools (44), which an agent carries on every turn
• Tool definitionsA · 97 of 100
• Typed results38 of 44 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 7 of 44

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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…

• 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…

• 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)…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• list_automations

  Use this when the user asks what Tenda does on its own for their team: the workspace's automations, each with its rules as sentences, whether it's on and what it last did, and the ones Tenda suggests. Needs a Tenda account and workspace…

• get_automation_library

  Use this when the user wants to know which automations Tenda can run for them, before making one with add_automation. Returns each one in Tenda's library, what it does and whether the workspace has it already. Needs a Tenda account and…

• add_automation

  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…

• turn_on_automation

  Use this only after you have read an automation's rules back to the user in plain words and they said yes to turning it on. From then on it runs as the user, outside quiet hours, and acts on the team's pipeline as its rules say…

• turn_off_automation

  Use this when the user wants one of the workspace's automations to stop. It stops running and keeps its rules and history, so it can be turned on again. Needs a Tenda account; owners, admins and bid leads turn them off.

• get_automation_history

  Use this when the user asks what Tenda's automations did lately: the last 10 things they did, newest first, for one automation or all of them. Needs a Tenda account and workspace.

• 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…

• 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…

• 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.

• 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.

• tenda_changes

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

• search_mentions

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

• 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…

• 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…

• 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…

• find_company

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

• finish_setup

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