← Registry

General Tools

reeco.eco

A tool to help prepare for upcoming environmental regulations.

1 endpoint7 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://ia.reeco.eco/mcp

No auth detected

MCP server metadata

Name
Reecopedia — EU Textile Regulations Search
Version
1.4.0
Capabilities
experimentalloggingprompts.listChangedresources.listChangedtools.listChangedextensions.io.modelcontextprotocol/ui
Server instructions

LANGUAGE CONTRACT — READ BEFORE CALLING. Corpus is English. Call the search tools ONLY with an English query in the legal register of the act (the wording of the Official Journal), not a tourist translation. Keep act identifiers and rewrite article/annex numbers into English ('Article 9', 'Annex I'; 第9条 / Artikel 9 / articolo 9 -> 'Article 9'). After you receive passages, answer the user in the user's language; quote the law in English with (file, page, article). If the user spoke another language, YOU translate before the call. Do not send non-English text in `query`. This is a contract, not a preference: measured 2026-08-27 on the live index, one question in three renderings — the Italian original returned only the CWA guidance (0.20); the literal English 'must a marketplace show the product passport before purchase, where is it written?' returned NOTHING AT ALL; the legal-register English 'make the digital product passport accessible to customers before they are bound by a contract of sale' returned the ESPR itself first (0.94, p.21, Article 9(2)(e)). Regulatory search engine for EU textile sustainability law: ESPR (Ecodesign for Sustainable Products Regulation 2024/1781), Digital Product Passport, CSRD, CBAM, EU ETS, CWA 18291 (CIRPASS-2), JRC preparatory studies. Use search_eu_textile_regulations for any question about these topics; ALWAYS cite the returned sources (file, page) in your answer, and answer ONLY from the returned passages — if they don't contain the answer, say so. The `search` and `fetch` tools expose the same corpus in the deep-research format (search results by id, fetch full document page by id). To explore a document's structure before fetching pages use `document_outline`; to locate an exact string (article numbers, regulation ids, precise wording) use `find_exact_text`. Some results are national-transposition REGISTER cards (source file 'CELEX_..._NIM.txt'): these are bibliographic pointers to a national law, not its text. The date they carry is a register/notification date, NOT the entry into force or date of application — those live in the national act. If a `notice` field is present in the tool result, follow it: state that the national text is not indexed for that measure and cite the official source rather than inferring an operative date. If the user says an answer built from these results was wrong or misleading, call `report_answer_issue` with the original query and a short reason: the report enters Reecopedia's human curation queue (no personal data is stored).

Known tools 7

search_eu_textile_regulations

LANGUAGE CONTRACT — READ BEFORE CALLING.

Inferred read-only
about_reecopedia

What Reecopedia is, who runs it, and its privacy policy.

Inferred read-only
report_answer_issue

Report that an answer built from Reecopedia search results was wrong, misleading or incomplete.

Inferred read-only
search

LANGUAGE CONTRACT — READ BEFORE CALLING.

Inferred read-only
fetch

Fetch the full text of a regulatory document page returned by `search`.

Inferred read-only
document_outline

Return the heading tree (table of sections) of an indexed document, so you can explore its structure before fetching pages.

Inferred read-only
find_exact_text

Find literal occurrences of an exact string in the corpus — article numbers, regulation ids, precise wording (e.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.reecopedia-eu-textile-regulations-search]
url = "https://ia.reeco.eco/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "reecopedia-eu-textile-regulations-search": {
      "type": "http",
      "url": "https://ia.reeco.eco/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: reecopedia-eu-textile-regulations-search
Remote MCP URL: https://ia.reeco.eco/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "reecopedia-eu-textile-regulations-search": {
      "url": "https://ia.reeco.eco/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "reecopedia-eu-textile-regulations-search": {
      "type": "http",
      "url": "https://ia.reeco.eco/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "reecopedia-eu-textile-regulations-search",
  "transport": "streamable-http",
  "url": "https://ia.reeco.eco/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for reeco.eco was fetched 2026-08-03T21:48:40.597Z and is being refreshed.

Trust status Trusted

reeco.eco is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.