Home / MCP registry index / ai.eshmere/tenda
Tenda
ai.eshmere/tenda in the official MCP registry.
Endpoint https://mcp.tenda.eshmere.ai/mcp.
The registry describes it as: Public tenders and contract awards in the UK, US, Canada and EU, and help preparing bids.
We read its 36 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_tenders get_tender_details search_contract_awards assess_tender_fit check_bid_readiness draft_bid_response review_bid_draft watch_tenders list_watches stop_watch get_tender_updates add_tender_documents save_company_profile get_pipeline_status add_to_pipeline record_portal_account record_bid_call update_bid_sprint assign_task move_in_pipeline choose_alerts start_bid_draft continue_bid_draft get_bid_draft rewrite_bid_answer add_winning_bid get_coverage open_tenda open_bid_panel tenda_changes search_mentions get_tenda_settings update_tenda_settings set_up_tenda find_company finish_setup
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-eshmere-tenda)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.