Epinu

ai.epinuPublished by epinu.aiOfficial publisherv1.0.4Updated Oct 25, 2026

Agent-first marketplace for real-world assets — agro and energy first; humans approve every write.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Epinu is a hosted MCP endpoint for an agent-first marketplace of real-world assets, letting assistants search public projects and listings and read full records

What you can do
Search public Epinu projects and marketplace listings for equipment, services and assets, or run one unified read-only search across both and fetch the full document for a result by its id. Read a static getting-started overview of the platform, its proposal/approval model and agent etiquette. With a delegated token, draft deals as pending proposals that a human must approve before anything is written.
When to use it
Use it when an assistant needs to look up real-world asset projects or marketplace listings (agro, energy, equipment, industrial services) and read their details, or when an account owner wants an agent to prepare listing or project proposals for human review.
Requirements
A remote Streamable HTTP endpoint; no local runtime or package. Read-only search and fetch work anonymously without an account or token. Drafting proposals requires an Epinu account and a delegated epagt_ token sent as an Authorization Bearer header.
Before you install
Writes never execute directly: write tools create pending proposals with an approval_url that a human approves or rejects in the dashboard, and unapproved proposals expire after 7 days. The epagt_ token is scoped and should be kept secret; out-of-scope calls fail, and sensitive actions such as deletes or profile changes need fresh MFA at approval. Proposals record the agent's client id in an audit trail.

Installation

In SourceWeft

  1. Open Epinu in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.epinu%2Fepinu/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Epinu MCP — agent door for a real-world asset marketplace

[MCP endpoint liveness]

Epinu is an agent-first marketplace for real-world assets — agro and energy first, extending to mining, equipment, and industrial services. AI agents are first-class users: they can search, read, and draft deals directly over MCP, and every write goes through a human-approval broker with a full audit trail.

This is the public integration repository for Epinu's hosted MCP endpoint: registry metadata (ai.epinu/epinu in the official MCP Registry), runnable examples, and operational checks. The Epinu platform implementation is maintained separately.

Try it in 60 seconds — no account, no token

bash
bash examples/quickstart.sh

That queries the live public production endpoint anonymously and returns current public project and marketplace results. The sample queries currently surface an ASIC repair center in Odessa, TX and related services; inventory may change. (QA fixtures are excluded from public reads as of 2026-07-15.) The anonymous tier allows initialize, tools/list, and five read tools (getting_started, marketplace_listings_search, projects_search, search, and fetch) against public data — see TOOLS.md for the reference.

Or the same flow in plain Node (zero dependencies, Node ≥ 18):

bash
node examples/walkthrough.mjs

Connect from Claude Code / any MCP client

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

or in .mcp.json:

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

Works immediately in read-only mode. To let your agent draft deals, add "headers": {"Authorization": "Bearer epagt_..."} with a delegated token — see below for how to get one. Details in examples/claude-code.md.

The interesting part: writes never execute

Epinu's write tools (marketplace_listing_create, project_create, …) do not write to the database. They create proposals (status: pending) and return an approval_url. A human reviews the proposal in the Epinu dashboard and approves or rejects it — only approval executes the change.

examples/walkthrough.mjs demonstrates the agent-controlled portion of the flow: search → create a pending proposal → check its status. Human approval happens separately in the Epinu dashboard. examples/walkthrough.md is the recorded, redacted transcript of a real production run — proposal created, reviewed, and rejected by the human, with nothing ever written.

Why is every write human-approved?

  • Agents make mistakes; markets are real. A hallucinated listing, a wrong price, or a duplicate is cheap to reject at proposal time and expensive to unwind after it's live. The broker makes the failure mode "a human clicked reject", not "a bad write hit production".
  • Identity and audit. Every proposal records actor.type=personal_agent and the agent's client id. The human always knows which agent proposed what, and the trail survives.
  • Scoped delegation, not account takeover. An epagt_ token is created by the account owner with explicit scopes (Dashboard → Settings → Authorize Agent). Out-of-scope calls fail with a clean scope error. Sensitive actions (deletes, profile changes) additionally require fresh MFA on the human side at approval time.
  • Drift checks. If the underlying data changed materially between proposal and approval, approval is blocked or requires explicit acknowledgment — an agent can't get a stale change approved.
  • Unapproved proposals expire on their own (7 days).

Production experience: Epinu reports that its first external marketplace participant was onboarded through a delegated AI agent: the agent prepared the catalog proposals, and the account owner reviewed and approved them in the dashboard. A sanitized case study is forthcoming.

Getting a token (for writes)

  1. Create an account at epinu.ai/signup
  2. Dashboard → Settings → Authorize Agent → choose scopes → copy the epagt_ token, or send your agent's human to https://epinu.ai/authorize-agent?name=<AgentName>&scopes=<scopes>
  3. Use it as Authorization: Bearer epagt_... on POST /api/agent/mcp (the token is valid on the MCP endpoint only)

What's in this repo

FileWhat it is
server.jsonThe MCP Registry entry for ai.epinu/epinu
examples/quickstart.shAnonymous tier in 60 seconds (curl)
examples/walkthrough.mjsSearch → create pending proposal → check proposal status (Node, zero deps)
examples/walkthrough.mdRecorded, redacted transcript of a real production run
examples/claude-code.mdConnect from Claude Code / .mcp.json
TOOLS.mdAnonymous-tier tool reference with captured responses
SECURITY.mdHow to report a vulnerability

The canonical, always-current agent documentation lives on the site itself: llms.txt · .well-known/mcp. This repo deliberately links rather than mirrors, so it can't go stale.

License

Examples and docs in this repository: MIT. The Epinu platform itself is a hosted service — epinu.ai.

Source: README.md at commit 1a8ea2b

Tools

5

getting_started

Getting Started

Start here: platform overview, the proposal/approval operating model, auth rules, common flows, and agent etiquette. Static content — requires no scopes.

Takes no parameters.

fetch

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 a token; public data only. Wraps projects_get_deep_dive and marketplace_listing_get. Unknown or malformed ids return a clean not-found.

Parametersidrequired

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts