# Epinu MCP server

Source: https://glimind.com/server/mcp-registry%2Fai.epinu%2Fepinu
Registry id: `mcp-registry/ai.epinu/epinu`
Status: live (checked 2026-10-26T19:39:22.252Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4982
- Outages (90 days): 15

## Install

```json
{
  "mcpServers": {
    "epinu-mcp-server": {
      "type": "http",
      "url": "https://api.epinu.ai/api/agent/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http epinu-mcp-server https://api.epinu.ai/api/agent/mcp
```

## Tools (5)

- `fetch`: Fetch the full document for one search result by its opaque id (project:<uuid> or listing:<uuid>). Returns { id, title, text, url, metadata }. Available without
- `getting_started`: Start here: platform overview, the proposal/approval operating model, auth rules, common flows, and agent etiquette. Static content — requires no scopes.
- `marketplace_listings_search`: Search the Epinu marketplace for equipment, services, and assets. Returns summaries only; call marketplace_listing_get for detailed packets.
- `projects_search`: Search Epinu real-asset projects. Returns bounded summaries only; call projects_get_deep_dive for detailed packets. Results include public projects plus the tok
- `search`: Unified read-only search across public Epinu projects and marketplace listings. Returns { id, title, url } results; call fetch with a returned id for the full d

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.