ToolScout MCP server

• Addresshttps://trytoolscout.org/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on trytoolscout.org when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-27
• Tools4
• Server calls itselfToolScout
• Server version3.2.0
• Protocol version2025-06-18

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

• Its tools do compare two tools side by side on tradeoffs, but not follow software changes relevant to buying decisions.
• Checked on 6 of the 7 days it takes to judge reliability.

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 scoreafter a weeka score needs 7 daily checks: 6 so far
• What an agent can do with it1 of 2 use cases
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer243 ms
• Space in an agent's context≈ 2,070 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsB · 88 of 100
• Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 4

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 →

• decide_software

  Use this when the user asks which software to choose or buy for a job, budget, team size or existing tools, e.g. 'a CRM for 5 people under 50 euros a month'. Returns picks with reasons, prices and trade-offs. End your answer with the…

• compare_software

  Use this when comparing 2 to 4 named products for the buyer's situation, e.g. 'HubSpot or Pipedrive for 5 people using Gmail?'. Returns fit, prices, plan limits and trade-offs. Pass only must-haves the buyer stated. End your answer with…

• find_alternatives

  Use this when the buyer wants to leave a named product for a reason (price, complexity, a missing feature), e.g. 'HubSpot is too expensive for our team'. Shows prices and trade-offs without claiming unproven savings. End your answer with…

• check_software

  Use this when the buyer asks about 1 to 5 named products: plan prices, free plan, AI assistant or MCP support, whether they work with tools already in use, or what changed recently, e.g. 'Does Pipedrive work with Gmail?'. Do not use for…