Skip to content

MCP servers › vn.eno › partner-api

MCP server · registry snapshot 2026-11-15 · last tested 2026-11-15

partner-api MCP server

Registry name vn.eno/partner-api

eno.vn Partner API — the publisher's title

by eno.vn · domain (the registry's namespace rule)Website ↗

Manage one storefront: listings, bulk catalogue sync, analytics and webhooks. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-11-15version 1.0.2streamable HTTP15 tools

Summary

vn.eno/partner-api is a remote MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the domain eno.vn. On 2026-11-15 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
15
Last tested
2026-11-15

Tool list size

8,018 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (15 tools). Counted with Anthropic's token counter on 2026-11-15, from the tool list we read on 2026-11-15. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-15 (eno.vn), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.2).

Add to your client

Observed fact

This server accepted a session without any credential and lists 8 tools whose name or declaration suggests they change data (update_shop, create_listing, update_listing, set_listing_status, delete_listing and 3 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-15.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-15
Mode
read-only (no tool calls)
Latest version
1.0.2, published 2026-11-14 (registry, as of the 2026-11-15 snapshot)
First listed version
2026-11-11 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-11 to 2026-11-14; 3 in the 90 days before the 2026-11-15 snapshot.
Most recent 3 versions
  • 1.0.2 · 2026-11-14
  • 1.0.1 · 2026-11-13
  • 1.0.0 · 2026-11-11
(versions still listed in the registry only)
Registry data
snapshot 2026-11-15
Package and repository
checked 2026-11-15
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.0.1 (published 2026-11-13) → 1.0.2 (published 2026-11-14), between the registry lists of 2026-11-14 and 2026-11-15.

No release note: the registry entry links no GitHub repository.

Source: the official MCP Registry list on 2026-11-14 and on 2026-11-15; release notes from the GitHub Releases API, checked 2026-11-15.

What it is

What does this server offer?

Observed inventory
15tools
0resources
0prompts

None of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.

  • “Read the storefront this connection acts for.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • update_shop

    “Change this shop's profile: the name, bio, location and logo buyers see on its page, and the contact phone eno shares with a buyer inside its chat.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    5 inputs
    • namestring“The shop's public name, shown on its page and beside its listings.”
    • biostring“About the shop, shown on its page.”
    • locationstring“Where the shop is, shown on its page.”
    • avatarUrlstring“The shop's logo: an image URL already on eno's storage, such as one from a listing's images.”
    • phonestring“The shop's contact phone number, a Vietnamese mobile; eno shares it with a buyer only inside its chat, never on the public page.”
  • list_listingson 10 other servers

    “List this shop's own listings, newest first, in every status unless you ask for one: active (on sale), sold or hidden.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • limitinteger“How many listings to return in this call.”
    • cursorstring“Where to continue: the `next_cursor` of the previous page; leave it out for the first page”
    • statusstring“Show only listings in one state, e.g.”
  • “Read one of this shop's listings by id, in any status.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“The listing to read, by the id list_listings or create_listing gave”
  • create_listingon 27 other servers

    “Post one new listing for this shop when the seller asks to sell, rent out or advertise something, or to post a job.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    12 inputs, 2 required
    • categorySlugstringrequired“The category to file the listing under, by its slug, e.g.”
    • titlestringrequired“The headline buyers see in search and on the listing page: name the item and what sets it apart.”
    • pricenumber“The asking price in VND.”
    • descriptionstring“The text shown on the listing page; contact details (phone, e-mail, links) are not allowed in it”
    • districtstring“Where the item is: the district or area as free text, e.g.”
    • conditionstring“The item's condition in words, e.g.”
    • imagesarray“Photos as public image URLs, in display order; eno copies each one to its own storage.”
    • negotiableboolean“Whether buyers may send offers below the price (yes unless you say no); services and jobs never take offers”
    • listingTypestring“What the listing offers: "sell" or "rent" where the category allows it ("job" or "wanted" in jobs); otherwise the category's usual one is used”
    • brandstring“The brand, matched to eno's brand list even with typos; only used in categories that have brands”
    • modelstring“The model within that brand; kept only when the brand was recognised”
    • salaryMinteger“A job's monthly salary in millions of VND (category "jobs"); leave it out when the pay is agreed with the candidate”
  • update_listingon 24 other servers

    “Change one of this shop's listings when the seller asks for a new price, better text, another district or new photos.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    8 inputs, 1 required
    • idstringrequired“The listing to change, by the id list_listings or create_listing gave”
    • titlestring“The new headline; phone numbers are not allowed in it.”
    • descriptionstring“The new text for the listing page; contact details are not allowed in it.”
    • pricenumber“The new asking price in VND (for a job: its monthly salary in VND).”
    • districtstring“Where the item is, as a district or area.”
    • conditionstring“The item's condition in words.”
    • imagesarray“The complete new set of photos as public image URLs, in display order; it replaces the current photos.”
    • salaryMinteger or null“A job's monthly salary in millions of VND; it wins over `price`.”
  • set_listing_statuson 3 other servers

    “Put one of this shop's listings on sale (active), mark it sold, or hide it from the site without deleting it.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 2 required
    • idstringrequired“The listing to change: the `id` that list_listings, get_listing or create_listing gave”
    • statusstringrequired“The state to move the listing to: sold once the item has gone to a buyer, hidden to take it off the site for now (for example while it is out of stock), active…”
  • delete_listingon 6 other servers

    “Permanently delete one of this shop's listings; it cannot be undone (use set_listing_status hidden to take it down instead).”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    1 input, 1 required
    • idstringrequired“The listing to delete for good: the `id` that list_listings or get_listing gave.”
  • bulk_create_listingson 1 other server

    “Post many new listings in one call, one row each (category, title, price in VND, optional text and photos as public image URLs), e.g.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • listingsarrayrequired“The new listings, one row each; every row succeeds or fails on its own”
  • sync_catalogue

    “Make this shop's listings match your own catalogue, matched by your externalId: a new externalId creates a listing, a known one updates it in place, and a row's status can mark it sold or hidden.”

    Publisher declares: read-only no · destructive yes · idempotent no · open-world yes

    2 inputs, 1 required
    • modestring“How to treat your listings missing from this payload: partial leaves them as they are, for sending only the rows that changed; full hides each active one whose…”
    • listingsarrayrequired“Your catalogue rows, each matched to its listing by externalId.”
  • analytics_summary

    “Read this shop's totals in one call.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • analytics_listings

    “Read views and leads (times a buyer opened contact) per listing per day over a date range, the last 30 days unless you choose one, with each listing's all-time totals.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • fromstring“The first day of the period to report, a UTC date written YYYY-MM-DD; left out, the 30 days before `to`.”
    • tostring“The last day of the period to report, a UTC date written YYYY-MM-DD; left out, today”
    • limitinteger“How many listings to return in this call.”
    • cursorstring“Where to continue: the `next_cursor` of the previous page; leave it out for the first page”
Show 3 more tools
  • list_webhookson 73 other servers

    “List the webhook endpoints registered for this shop.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • register_webhookon 15 other servers

    “Register an HTTPS endpoint of yours that eno will POST signed events to when this shop's listings are created, updated, change status or are deleted.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • urlstringrequired“Your public HTTPS address that will receive the events”
    • eventsarray“The changes to be told about, e.g.”
  • delete_webhookon 56 other servers

    “Remove one of this shop's webhook endpoints, e.g.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • idstringrequired“The webhook to remove, by the id list_webhooks or register_webhook gave”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-15.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 42
Tools with a description
100% of 15
Typical description length
493 characters

The tool set

Counted from the listing

Tools
15
Size of the list
about 12,827 tokens for an agent to load (characters ÷ 4)
Naming
15 of 15 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-15 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://eno.vn/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "partner-api": {
      "url": "https://eno.vn/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "partner-api": {
      "type": "http",
      "url": "https://eno.vn/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"partner-api","type":"http","url":"https://eno.vn/api/mcp"}'
Claude Code
claude mcp add --transport http partner-api https://eno.vn/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "partner-api": {
      "type": "streamableHttp",
      "url": "https://eno.vn/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "partner-api": {
      "httpUrl": "https://eno.vn/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.partner-api]
url = "https://eno.vn/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "partner-api": {
      "url": "https://eno.vn/api/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://eno.vn/api/mcp --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-15. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-15. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-15. Source: read 2026-11-15.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-15. Source: read 2026-11-15.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint eno.vn/api/mcpSession openedmatchesour test · 2026-11-15
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-15

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-15. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about vn.eno/partner-api

Answered from the data above

Who publishes vn.eno/partner-api?

The registry ties the namespace vn.eno to the domain eno.vn; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does vn.eno/partner-api need an API key or sign-in?

It opened a session without any credential on 2026-11-15. The registry entry declares no required credential; no declaration is not a guarantee.

Has vn.eno/partner-api been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-15
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-15, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 604 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 15 tools, 0 resources, 0 prompts.
  4. 2,482 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-15; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-15
MCP capability
tools
our test · 2026-11-15
Transport
streamable HTTP
registry · 2026-11-15
Required credentials
none declared
registry · 2026-11-15 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-15
Lifecycle status
registry · 2026-11-15
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-15

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “vn.eno/partner-api: MCP server record.” Data checked 2026-11-15. https://protocolprobe.com/mcp/servers/vn.eno/partner-api

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/vn.eno/partner-api)](https://protocolprobe.com/mcp/servers/vn.eno/partner-api)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology