Reecopedia is answering right now. Last checked 8 min ago. It exposes 8 tools.
Regulatory search engine for EU textile sustainability law: ESPR, DPP, CSRD, CBAM, CWA 18291.
Uptime history
91 days of history · worst day 93%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
462 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 46
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 August 2026. No other catalogue keeps this.
25 Sep
2 tool descriptions were rewritten
search, search_eu_textile_regulations
22 Sep
4 tool descriptions were rewritten
document_outline, fetch, search and 1 more
20 Sep
a tool description was rewritten
fetch
17 Sep
7 tool descriptions were rewritten
about_reecopedia, document_outline, fetch and 4 more
17 Sep
6 tools changed the parameters they ask for
document_outline, fetch, find_exact_text and 3 more
17 Sep
a tool changed version
11 Sep
a tool appeared
list_corpus_documents
7 Sep
7 tool descriptions were rewritten10 times that day
about_reecopedia, document_outline, fetch and 4 more
7 Sep
3 tools changed the parameters they ask for
report_answer_issue, search, search_eu_textile_regulations
7 Sep
a tool changed version
and 13 more, back to 22 August 2026
Nothing serious here today
Today is the operative word: we check Reecopedia every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.
run in your terminal
claude mcp add reecopedia --transport http https://ia.reeco.eco/mcpSettings → Connectors → Add custom connector, then paste this address
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
{
"servers": {
"reecopedia": {
"type": "http",
"url": "https://ia.reeco.eco/mcp"
}
}
}Available tools 8
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
no description provided
corpus
list_corpus_documents
List indexed document names matching a substring.
document
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 containers or unverified fragments.
exact
find_exact_text
Locate a literal string in the current corpus, optionally restricted to a document.
fetch
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.
report
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 to correct the corpus and retrieval quality.
THIS TOOL WRITES. Use it only when the user has asked for the problem to
be reported, and send only the original query and the reason the user
gave. Do not call it on your own initiative and do not add anything the
user did not say.
ANNOTATIONS — why each hint is set the way it is, based on this tool's actual
behaviour. readOnlyHint=false: this is the only tool that writes; it appends
one record (the query and the reason, nothing else) to Reecopedia's internal
human curation queue. destructiveHint=false: the write is append-only; it
modifies and deletes nothing that already exists. idempotentHint=false: two
calls can append two records — de-duplication covers only an identical
query+reason pair within the same hour. openWorldHint=false: the record stays
in the internal queue; it is not sent anywhere outside Reecopedia.
search
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.
textile
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 the returned text. Query embeddings use Alibaba; candidate passages are sent to Jina for reranking.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://ia.reeco.eco/mcp | streamable-http | answering | 373 ms | 8 min ago |
Alternatives to Reecopedia
same job, measured the same wayLlmse
by llmse
Public MCP server for the LLM Search Engine
Vexor
by scarletkc
A semantic search engine for files and code.
Thordata SERP MCP Server
by thordata
Thordata SERP search, history, statistics, and engine schemas for MCP clients.
Hashgrid DNA
by hashgrid
A search engine that learns from your grades. Store text, records, images or embeddings.
Searxng MCP
by aicrafted
MCP server for SearXNG aggregator — web search across multiple engines via Model Context Protocol
Market Brew
by marketbrew
Read-only Market Brew search engine modeling and AI visibility data via OAuth.
Visibility Readiness
by vendorlens
Checks if search engines and AI tools can read your site; evidence plus fixes for your builder.
AI Visibility Check
by aivisibilitycheck
Audit how AI assistants and search engines find, understand and recommend a website.
Reecopedia — questions
Answers built from our own checks of this server.
What can Reecopedia do?
It exposes 8 tools, read directly from the server on our last check. Among them: about_reecopedia, document_outline, fetch, find_exact_text, list_corpus_documents, report_answer_issue and 2 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 91 of 91 checks got a reply (100.0%), average response time 462 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 in the form 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 8 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 462 ms on average, which is faster than 26% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.