mcpbeat

Reecopedia MCP Server

eco.reeco/reecopedia
answering

Reecopedia is answering right now. Last checked 1 min ago. It exposes 7 tools.

Regulatory search engine for EU textile sustainability law: ESPR, DPP, CSRD, CBAM, CWA 18291.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
7
Tools
read from the server
358 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add reecopedia --transport http https://ia.reeco.eco/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "reecopedia": {
      "url": "https://ia.reeco.eco/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.reecopedia]
url = "https://ia.reeco.eco/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "reecopedia": {
      "url": "https://ia.reeco.eco/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "reecopedia": {
      "url": "https://ia.reeco.eco/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

about
about_reecopedia
What Reecopedia is, who runs it, and its privacy policy.
document
document_outline
Return the heading tree (table of sections) of an indexed document, so you can explore its structure before fetching pages. Each entry has the heading text, its full path, depth and first page: pass the page to `fetch` as "<document>#p<page>" to read it.
exact
find_exact_text
Find literal occurrences of an exact string in the corpus — article numbers, regulation ids, precise wording (e.g. "Article 8(3)", "2024/1781"). Complements semantic `search`: use this when you need the exact string, not the concept. Returns one match per (file, page) with an occurrence count and a text snippet; read the full page with `fetch`. Scans the literal chunk text of both indexes the semantic search serves (the two chunkings differ, so some passages exist in only one); the synthetic contextual enrichment is NOT scanned — it is not document text.
fetch
fetch
Fetch the full text of a regulatory document page returned by `search`.
report
report_answer_issue
Report that an answer built from Reecopedia search results was wrong, misleading or incomplete. The report (query + reason, nothing else — no personal data) enters Reecopedia's human curation queue and is reviewed weekly to correct the corpus and retrieval quality. Call this when the user flags an answer as wrong, or when you notice the retrieved passages contradict the answer you gave.
search
search
Search EU textile sustainability regulations (ESPR, DPP, CSRD, CBAM, EU ETS, CWA 18291, JRC studies). Deep-research interface: returns a list of matching regulatory passages as {results: [{id, title, text, url}]}. Pass a result `id` to the `fetch` tool to get the full document page.
textile
search_eu_textile_regulations
Search the Reecopedia corpus of EU textile sustainability regulations. Returns the most relevant regulatory passages with citations (source file, page, section). Answer the user's question ONLY from these passages and cite them. Corpus: ESPR 2024/1781, Digital Product Passport, CSRD, CBAM, EU ETS, CWA 18291, JRC BREF and textile preparatory studies, EP studies.

Endpoints

URLTransportStateLatencyChecked
https://ia.reeco.eco/mcp streamable-http answering 387 ms 1 min ago

Reecopedia — questions

Answers built from our own checks of this server.

What can Reecopedia do?
It exposes 7 tools, read directly from the server on our last check. Among them: about_reecopedia, document_outline, fetch, find_exact_text, report_answer_issue, search and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Reecopedia working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 358 ms. The bar chart above shows every period we have measured.
How do I connect Reecopedia?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Reecopedia need an API key?
No. Reecopedia completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Reecopedia?
It answers our handshake in 358 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.