RMCP.DEV
← Registry

eCommerce

eno.vn

Manages an e-commerce storefront by retrieving and updating shop profiles and creating, listing, and fetching product listings.

1 endpoint15 known toolsFirst detected September 20, 2026Last detected September 20, 2026

ENDPOINT 1

https://eno.vn/api/mcp

No auth detected

MCP server metadata

Name
eno.vn Partner API
Version
1.0.0
Capabilities
tools
Server instructions

Manage a eno.vn storefront: list/create/update/delete listings, bulk-import, sync a catalogue by your own externalId, read analytics, and manage webhooks. Every action is scoped to the one shop behind the API key.

Known tools 15

get_shop

Get the authenticated shop's storefront profile, trust score, and live listing count.

Inferred read-only
update_shop

Edit the storefront profile.

Potential side effects
list_listings

List the shop's listings (all statuses).

Inferred read-only
get_listing

Get one of the shop's listings by id (any status).

Inferred read-only
create_listing

Create a listing.

Potential side effects
update_listing

Edit one of the shop's listings (sparse).

Potential side effects
set_listing_status

Set a listing's availability: active | sold | hidden.

Inferred read-only
delete_listing

Delete one of the shop's listings.

Potential side effects
bulk_create_listings

Create up to 200 listings in one call.

Potential side effects
sync_catalogue

Upsert the catalogue by your own externalId.

Inferred read-only
analytics_summary

Shop-level totals: views, leads, and listing counts by status.

Inferred read-only
analytics_listings

Per-listing daily views + leads (deltas) over a date range, plus totals.

Inferred read-only
list_webhooks

List the shop's registered webhook endpoints (secrets are never returned) with delivery health.

Inferred read-only
register_webhook

Register an HTTPS endpoint for signed listing events.

Inferred read-only
delete_webhook

Unregister a webhook endpoint by id.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.eno-vn-partner-api]
url = "https://eno.vn/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "eno-vn-partner-api": {
      "type": "http",
      "url": "https://eno.vn/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: eno-vn-partner-api
Remote MCP URL: https://eno.vn/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "eno-vn-partner-api": {
      "url": "https://eno.vn/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "eno-vn-partner-api": {
      "type": "http",
      "url": "https://eno.vn/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "eno-vn-partner-api",
  "transport": "streamable-http",
  "url": "https://eno.vn/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.