Reeco® MCP server

• Registry nameeco.reeco/reecopediaverified in the MCP registry

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

• Stateanswerschecked 2026-10-20
• Tools8
• Server calls itselfReecopedia — EU Textile Regulations Search
• Server version2.0.0
• Protocol version2025-06-18

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

• Its tools do none of the product's use cases we checked: check textile certification claims against primary certification databases; issue per-garment digital product passports with signed records; compute durability and repairability indices from lab test reports.
• Checked on 2 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: 2 so far
• What an agent can do with it0 of 3 use cases
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer1023 ms
• Space in an agent's context≈ 1,038 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsB · 85 of 100
• Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once

• No description an agent can choose by: 1 of 8
• Parameters without a description: in 6 of 8

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 (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). 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_eu_textile_regulations

  Search regulatory evidence in English legal register. Cite original document and unit; verify each claim. Optional scope narrows corpus partitions. No model assesses the answer in this MCP tool; the client must verify each claim against…

• search

  Return cited corpus results by id; use fetch for full source text. The client verifies the evidence. Query embeddings use Alibaba; candidate passages go to Jina for reranking.

• fetch

  Fetch original text by an opaque id from search or document_outline. Pass ids unchanged. Navigation containers have citable=false and child ids, not source evidence. Historical page identifiers return migration guidance.

• document_outline

  Return a compact navigation-v1 tree of indexed source text. Source metadata is shared in documents; depth/path encode hierarchy. Pass opaque ids unchanged to fetch. Warnings expose uncertain structure; citable=false marks navigation…

• find_exact_text

  Locate a literal string in the current corpus, optionally restricted to a document.

• list_corpus_documents

  List indexed document names matching a substring.

• about_reecopedia

  No description given.

• report_answer_issue

  File a report that an answer built from Reecopedia search results was wrong, misleading or incomplete. The report (the query and the reason, nothing else — no personal data) enters Reecopedia's human curation queue and is reviewed weekly…