Epinu

What epinu MCP server does

The epinu MCP server exposes Epinu’s agent-facing marketplace through a hosted MCP endpoint. Epinu covers real-world assets and related activity, starting with agro and energy and extending to areas such as mining, equipment, and industrial services. Agents can inspect public marketplace and project information, then prepare proposed changes for human review.

The repository is an integration and reference project rather than the implementation of the Epinu platform. It contains registry metadata, runnable examples, operational checks, and links to the live agent documentation. The hosted endpoint is https://api.epinu.ai/api/agent/mcp.

How it works

Clients communicate with the endpoint over Streamable HTTP using JSON-RPC 2.0. The anonymous access tier supports initialization, tool discovery, and five read tools: getting_started, marketplace_listings_search, projects_search, search, and fetch. These operations query current public data; inventory and results can change over time.

Write operations use a proposal workflow. A tool such as marketplace_listing_create or project_create creates a pending proposal and returns an approval URL instead of changing the database immediately. A person reviews the proposal in the Epinu dashboard and approves or rejects it. Approval is also subject to delegated token scopes, drift checks, and, for sensitive actions, human-side MFA. Pending proposals expire after seven days.

Setup and configuration

The epinu MCP server can be used without an account for its supported public reads. A quickstart shell script and a dependency-free Node example are included in the repository. Node examples require Node 18 or newer.

For a compatible MCP client, configure the endpoint as an HTTP server. Claude Code can add it with:

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

Write proposals require an account owner to create a delegated epagt_ token in Epinu under Settings and Authorize Agent. Send that token as an Authorization: Bearer header on requests to the MCP endpoint. The token is restricted to the scopes selected by the account owner and is valid for this MCP endpoint.

Tools and capabilities

The epinu MCP server supports these documented anonymous read tools:

• getting_started for introductory agent guidance.
• marketplace_listings_search for public marketplace listing searches.
• projects_search for public project searches.
• search and fetch for the server’s public search and retrieval flow.

Authenticated write tools can create proposals for marketplace listings and projects. The available scope and behavior should be checked in Epinu’s current agent documentation at epinu.ai/llms.txt or its MCP manifest, since the platform documentation is maintained separately from this repository.

Limitations and notes

The public repository does not contain the Epinu platform implementation. Public reads are limited to the anonymous tier, while proposal creation needs delegated authorization. Agents do not receive direct database-write access: every write remains pending until a human acts in the Epinu dashboard. This makes the server suitable for assisted marketplace workflows, but not for unattended changes that must execute immediately.

The repository’s examples and documentation are licensed under MIT. Epinu itself is a hosted service, so using the endpoint is separate from licensing the repository contents.