Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Epinu

REMOTE · API.EPINU.AI · SCANNED SEP 21

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

Available components

0 this week 85 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 428 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Epinu MCP server?

Epinu is a hosted endpoint at https://api.epinu.ai/api/agent/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.

remote · api.epinu.ai

# add to Claude Code
claude mcp add --transport http ai-epinu-epinu 'https://api.epinu.ai/api/agent/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-epinu-epinu": {
      "url": "https://api.epinu.ai/api/agent/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-epinu-epinu": {
      "type": "http",
      "url": "https://api.epinu.ai/api/agent/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-epinu-epinu]
url = "https://api.epinu.ai/api/agent/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-epinu-epinu": {
      "type": "remote",
      "url": "https://api.epinu.ai/api/agent/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-epinu-epinu --url 'https://api.epinu.ai/api/agent/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-epinu-epinu:
    url: "https://api.epinu.ai/api/agent/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-epinu-epinu": {
      "Transport": "http",
      "Url": "https://api.epinu.ai/api/agent/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-epinu-epinu -t streamable-http -u 'https://api.epinu.ai/api/agent/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-epinu-epinu": {
      "type": "http",
      "url": "https://api.epinu.ai/api/agent/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://api.epinu.ai/api/agent/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=epinu.ai CN=YE2,O=Let's Encrypt,C=US 1 Sept 2026 30 Nov 2026 ECDSA 256 ECDSA-SHA384 6b12648dbf7c6f2ff215fff629b3fbc7b07
SANs: *.epinu.ai, epinu.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.epinu.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
epinu.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="epinu-agent", resource_metadata="https://api.epinu.ai/.well-known/oauth-protected-resource"

Bearer realm="epinu-agent", resource_metadata="https://api.epinu.ai/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;script-src 'self' 'unsafe-inline' https://maps.googleapis.com;img-src 'self' data: https: blob:;connect-src 'self' https://api.openai.com https://api.anthropic.com;font-src 'self' https://fonts.gstatic.com;object-src 'none';media-src 'self';frame-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Protected resource metadata

Document https://api.epinu.ai/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://api.epinu.ai/api/agent/mcp
Authorisation server https://api.epinu.ai

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.epinu.ai/api/agent/mcp Verified 200
http (plaintext) http://api.epinu.ai/api/agent/mcp Inconclusive 405
MCP tools · 5 exposed · ~397 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fetch ~80

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.

NameTypeReqDescription
idstringyes
NameTypeReqDescription
idstringyes
metadataobjectyes
textstringyes
titlestringyes
urlstringyes

No examples provided.

getting_started ~38

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
authobjectyes
common_flowsarrayyes
docsstringyes
etiquettearrayyes
field_limitsstringyes
operating_modelobjectyes
platformstringyes
welcomestring

No examples provided.

marketplace_listings_search ~87

Search the Epinu marketplace for equipment, services, and assets. Returns summaries only; call marketplace_listing_get for detailed packets.

NameTypeReqDescription
availabilityTypestring
categorystring
cursorstring
limitinteger
maxPricenumber
querystring
subcategorystring
NameTypeReqDescription
dropped_invalid_countinteger
next_cursoryes
resultsarrayyes
total_returnedintegeryes

No examples provided.

projects_search ~123

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; another owner's unpublished projects are never returned. Available without a token for public results only.

NameTypeReqDescription
asset_typestring
cursorstring
limitinteger
max_funding_goalnumber
min_roinumber
querystring
statusstring
NameTypeReqDescription
dropped_invalid_countinteger
limitnumberyes
next_cursoryes
projectsarrayyes

No examples provided.

search ~69

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 projects_search and marketplace_listings_search.

NameTypeReqDescription
querystringyes
NameTypeReqDescription
resultsarrayyes

No examples provided.

Common questions

What is the Epinu MCP server?

Epinu is an MCP server listed in the public MCP registry as ai.epinu/epinu. Agent-first marketplace for real-world assets, agro and energy first; humans approve every write. This page covers its hosted endpoint (https://api.epinu.ai/api/agent/mcp).

Is the Epinu MCP server safe to use?

Epinu scores 85 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.

What tools does the Epinu MCP server expose?

Epinu exposes 5 tools: projects_search, getting_started, marketplace_listings_search, search, fetch. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.

Does the Epinu MCP server require authentication?

Yes. Epinu 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 Epinu MCP server still maintained?

Epinu is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.