# Unreasonable Eco (remote · unreasonable.eco) Search Unreasonable people, ventures, funders, programs, and commitments. - Trust score: 39/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-22 ## Components - remote · `unreasonable.eco`: 39/100 (this document), [markdown](https://verifymcp.io/servers/eco-unreasonable-mcp/unreasonable.md), [page](https://verifymcp.io/servers/eco-unreasonable-mcp/unreasonable) ## Channel facts - Endpoint: `https://unreasonable.eco/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.4.3` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-22. - **Endpoint Security**: 97/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. - **Transport & Reachability**: 0/100 - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. - **Schema Quality & AI Usability**: 0/100 - Schema blocked by authentication: the endpoint requires auth we don't have to read it. - **Stability & Change Management**: 0/100 - Stability not yet verified: not enough scan history yet (needs a 30-day window). - **Tool Coverage**: 0/100 - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. - **Capabilities**: 0/100 - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. **Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. ## Install ### How do I install the Unreasonable Eco MCP server? Unreasonable Eco is a hosted endpoint at https://unreasonable.eco/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http eco-unreasonable-mcp 'https://unreasonable.eco/mcp' ``` ### Cursor ```json { "mcpServers": { "eco-unreasonable-mcp": { "url": "https://unreasonable.eco/mcp" } } } ``` ### VS Code ```json { "servers": { "eco-unreasonable-mcp": { "type": "http", "url": "https://unreasonable.eco/mcp" } } } ``` ### Codex ```toml [mcp_servers.eco-unreasonable-mcp] url = "https://unreasonable.eco/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "eco-unreasonable-mcp": { "type": "remote", "url": "https://unreasonable.eco/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add eco-unreasonable-mcp --url 'https://unreasonable.eco/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: eco-unreasonable-mcp: url: "https://unreasonable.eco/mcp" ``` ### Netclaw ```json { "McpServers": { "eco-unreasonable-mcp": { "Transport": "http", "Url": "https://unreasonable.eco/mcp" } } } ``` ### Vellum ```bash assistant mcp add eco-unreasonable-mcp -t streamable-http -u 'https://unreasonable.eco/mcp' ``` ### Other ```json { "mcpServers": { "eco-unreasonable-mcp": { "type": "http", "url": "https://unreasonable.eco/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-22 (score 39) First indexed and scored. ## MCP tools (0) No tool schema has been captured from this endpoint yet. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eco-unreasonable-mcp/unreasonable#diagnostics ## Score history - 2026-08-22: 39 ## Common questions ### What is the Unreasonable Eco MCP server? Unreasonable Eco is an MCP server listed in the public MCP registry as eco.unreasonable/mcp. Search Unreasonable people, ventures, funders, programs, and commitments. This page covers its hosted endpoint (https://unreasonable.eco/mcp). ### Is the Unreasonable Eco MCP server safe to use? Unreasonable Eco scores 39 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### Does the Unreasonable Eco MCP server require authentication? Yes. Unreasonable Eco asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything. ### Is the Unreasonable Eco MCP server still maintained? Unreasonable Eco is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://unreasonable.eco/mcp - Repository: https://github.com/unreasonable/flow - Website: https://urg.ai/+eco-mcp - Changelog RSS feed: https://verifymcp.io/servers/eco-unreasonable-mcp/unreasonable.xml - Changelog JSON feed: https://verifymcp.io/servers/eco-unreasonable-mcp/unreasonable.json - HTML version of this page: https://verifymcp.io/servers/eco-unreasonable-mcp/unreasonable