Skip to content
Epinu Agro Network logo

Epinu Agro Network MCP server

Which MCP servers are Epinu Agro Network's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-23

← Back to Epinu Agro Network

Whose server it is
  • Registry nameai.epinu/epinuverified in the MCP registry

The registry name sits under epinu.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-23
  • Stateanswerschecked 2026-10-23
  • Tools5
  • Server calls itselfepinu-agent-api
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-23 the server answered initialize and tools/list without a sign-in. First answer in 424 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 4 of 5 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-23
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer316 ms
  • Space in an agent's context≈ 674 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsC · 70 of 100
  • Typed results5 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 5
  • Not saying whether it only reads or can destroy: 5 of 5

What an agent can do with it

  • not sure · find fincas and cattle partnerships on an interactive map
  • cannot · offer cattle and farm produce on a marketplace
  • not sure · review AI-prepared partnership proposals before final approval

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-23
  • 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 token owner's own archived, draft, or unpublished projects for duplicate checks…

  • 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.

  • 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 document. Available without a token; public data only. Additive alias over…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.epinu.ai/api/agent/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.