MCP servers › com.simvito › esim
MCP server · registry snapshot 2026-11-08 · last checked 2026-11-15
esim MCP server
Registry name com.simvito/esim
Simvito eSIM — the publisher's title
by simvito.com · domain (the registry's namespace rule)repository owner on GitHub: SimvitoTeam (organization)Source ↗npm ↗Website ↗
Compare travel eSIM plans and each local network (4G/5G), check phone support, get payment links. — the publisher's description
Summary
com.simvito/esim is a remote and local MCP server listed in the official MCP registry at version 1.3.4, under the namespace of the domain simvito.com. Its linked repository is github.com/SimvitoTeam/simvito-mcp; GitHub reports its owner as SimvitoTeam, an organization. On 2026-11-08 ProtocolProbe connected to it in read-only mode and read its inventory: 10 tools, 2 resources and 4 prompts.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #9,572 of 20,610 packages by monthly downloads, tied with 8 others
- Not ranked by stars: 1 star (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 10
- Last tested
- 2026-11-08
Tool list size
6,594 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (10 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-08. 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-08 (mcp.simvito.com), 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.3.4).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-08
- Mode
- read-only (no tool calls)
- Latest version
- 1.3.4, published 2026-11-08 (registry, as of the 2026-11-08 snapshot)
- First listed version
- 2026-11-08 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 4 versions listed, all on 2026-11-08; 4 in the 90 days before the 2026-11-08 snapshot.(versions still listed in the registry only)
Most recent 4 versions
1.3.4· 2026-11-081.3.3· 2026-11-081.3.2· 2026-11-081.3.1· 2026-11-08
- Registry data
- snapshot 2026-11-08
- 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; 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
New in the registry: not in the list of 2026-11-07, listed on 2026-11-08 with version 1.3.4 (published 2026-11-08).
Source: the official MCP Registry list on 2026-11-07 and on 2026-11-08.
What it is
What does this server offer?
Observed inventoryNone of its 10 tools are described as changing anything. For 10 the reading was uncertain, so no mark is shown.
- find_destinationon 3 other servers
“Find where a trip goes: a country, a region such as 'Europe' or 'Asia', or a multi-country plan, by name in any language, ISO code or misspelling (many cities and islands such as 'Tokyo' or 'Bali' wo…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
querystringrequired“Country, territory or region name, e.g.”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- search_planson 26 other servers
“Find travel eSIM data plans for one destination and trip length, e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 2 required
destinationstringrequired“Destination slug from find_destination (e.g.”daysintegerrequired“Trip length in days”data_gbnumber“Total data needed for the whole trip in GB; omit if unsure”plan_typestring“total = one data allowance for the trip; daily = allowance renews each day; unlimited.”currencystring“The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, A…”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- compare_networks
“Compare the local mobile networks for a destination side by side, for questions like 'which network is best in Thailand' or 'which eSIM has 5G in Tokyo': each operator the plans use, its best generat…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
destinationstringrequired“Destination slug from find_destination (e.g.”countrystring“Only for multi-country destinations: one covered country (name or ISO code)”currencystring“The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, A…”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- plan_tripon 29 other servers
“For a trip through several countries (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
stopsarrayrequireddata_gb_per_daynumber“Expected data use per day in GB; defaults to 1”currencystring“The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, A…”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- check_deviceon 6 other servers
“Check whether a phone supports eSIM, e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
modelstringrequired“Phone model, e.g.”purchase_regionstring“ISO code of the country/region where the phone was bought, e.g.”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- get_buy_linkon 7 other servers
“Get the simvito.com checkout link for a plan from search_plans or plan_trip, with the price in the user's currency (total for the quantity) and the payment methods for that currency.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
destinationstring“Destination slug from find_destination (e.g.”plan_idstringrequired“plan_id returned by search_plans or plan_trip”trip_daysinteger“Trip length in days, if known”quantityinteger“Number of eSIMs (one per traveller).”currencystring“The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, A…”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- list_my_esims
“List the eSIMs in the user's connected Simvito account: destination, plan, status, whether installed, data left and expiry, with a link to manage each one (install, add data) on simvito.com.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- get_checkout_optionson 1 other server
“Languages, currencies and payment methods at simvito.com checkout.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
countrystring“Buyer's country or region (ISO 3166-1 alpha-2, e.g.”currencystring“The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, A…”languagestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
- start_checkouton 48 other servers
“When the user decides to buy and their Simvito account is connected: places the order on their account and returns two payment links to give them exactly as returned, a secure payment page for cards,…”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
9 inputs
destinationstring“The destination search_plans returned with the plan(s); can also be given on each item.”itemsarray“The plans to buy, each with its quantity.”plan_idstring“Shorthand for a single plan: plan_id returned by search_plans or plan_trip (instead of items)”quantityinteger“With plan_id: number of eSIMs (one per traveller).”expected_unit_amountnumber“With plan_id, only after price_changed: the new unit price the user accepted.”currencystring“The user's currency (ISO 4217) for prices: USD, EUR, GBP, HKD, CNY, SGD, JPY, AUD, NZD, CAD, BRL, IDR, MYR, PHP, THB, KRW, PLN, CHF, SEK, TWD, VND, TRY, SAR, A…”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”devicestring“Where the user will open the payment link, if you know: 'phone' or 'computer'”confirmationsarray“Codes from a previous confirmation_required result that the user explicitly agreed to after seeing each text.”
- get_order_statuson 89 other servers
“After the user pays through start_checkout's links (e.g.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
checkout_idstringrequired“checkout_id returned by start_checkout”localestring“Language of the conversation, as a simvito.com language code ('en', 'ja', 'zh-CN', 'es'…); names and links follow it.”
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-08.
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
- 98% of 40
- Tools with a description
- 100% of 10
- Typical description length
- 317 characters
The tool set
Counted from the listing
- Tools
- 10
- Size of the list
- about 10,145 tokens for an agent to load (characters ÷ 4)
- Naming
- 10 of 10 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 10 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 npm package simvito-mcp
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"esim": {
"command": "npx",
"args": [
"-y",
"simvito-mcp@1.3.3"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"esim": {
"command": "npx",
"args": [
"-y",
"simvito-mcp@1.3.3"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"esim": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"simvito-mcp@1.3.3"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"esim","type":"stdio","command":"npx","args":["-y","simvito-mcp@1.3.3"]}'Claude Code
claude mcp add --transport stdio esim -- npx -y simvito-mcp@1.3.3
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"esim": {
"command": "npx",
"args": [
"-y",
"simvito-mcp@1.3.3"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"esim": {
"command": "npx",
"args": [
"-y",
"simvito-mcp@1.3.3"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.esim] command = "npx" args = ["-y", "simvito-mcp@1.3.3"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"esim": {
"command": "npx",
"args": [
"-y",
"simvito-mcp@1.3.3"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y simvito-mcp@1.3.3
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-08 (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://mcp.simvito.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"esim": {
"url": "https://mcp.simvito.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"esim": {
"type": "http",
"url": "https://mcp.simvito.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"esim","type":"http","url":"https://mcp.simvito.com/mcp"}'Claude Code
claude mcp add --transport http esim https://mcp.simvito.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"esim": {
"type": "streamableHttp",
"url": "https://mcp.simvito.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"esim": {
"httpUrl": "https://mcp.simvito.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.esim] url = "https://mcp.simvito.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"esim": {
"url": "https://mcp.simvito.com/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://mcp.simvito.com/mcp --transport http
- 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.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 1.3.3
- Latest stable
- 1.3.3
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-15. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-08 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-x+kyGG9PG7guHhKn/…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-11-15.
Usage
- Downloads
- 429 in the last month
Source: api.npmjs.org · 2026-11-15.
Does the registry listing match what we found?
Feature #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.simvito.com/mcp | Session opened | matches | our test · 2026-11-08 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-08 |
| Version 1.3.3 on npm | Exists and can be installed | matches | npm · 2026-11-15 |
| Repository github.com/SimvitoTeam/simvito-mcp | Opens publicly | matches | api.github.com · 2026-11-15 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- com.simvito
- GitHub owner
- an organization (SimvitoTeam)
- Build record
- signed
- Repository
- github.com/SimvitoTeam/simvito-mcp
- Stars
- 1
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-15; security policy read from GitHub · 2026-11-08.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- #9,572 of 20,610 packages by monthly downloads, tied with 8 others
- Not ranked by stars: 1 star (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-15 (security policy 2026-11-08). 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 com.simvito/esim
Answered from the data aboveWho publishes com.simvito/esim?
The registry ties the namespace com.simvito to the domain simvito.com; only its owner can publish under it. Its linked repository is github.com/SimvitoTeam/simvito-mcp; GitHub reports its owner as SimvitoTeam, an organization. These are facts from the registry and GitHub, not a rating.
Is com.simvito/esim safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does com.simvito/esim need an API key or sign-in?
It opened a session without any credential on 2026-11-08. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.simvito/esim been security tested?
Partly. 5 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its 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). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Does com.simvito/esim publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 1.3.3, the latest stable release on npm.
Where is the source code of com.simvito/esim?
In github.com/SimvitoTeam/simvito-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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
Not probed (no operator permission)
We connected and read what the server declares, but did not call its 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). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
5 exercised11 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 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.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls 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-leakPlants 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
ssrfChecks 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-confirmationChecks 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-handlingSends 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
samplingChecks 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-dataChecks 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-boundaryChecks 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-channelChecks 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 - 16Sign-in redirect
open-redirectChecks 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-deputyChecks 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
- 14Token passthrough
token-passthroughChecks 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-validationChecks 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-08, 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.
- 0 msStarted a read-only session with the server's remote endpoint
- 866 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 10 tools, 2 resources, 4 prompts.
- 2,558 msFinished: 5 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.
“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. “com.simvito/esim: MCP server record.” Data checked 2026-11-15. https://protocolprobe.com/mcp/servers/com.simvito/esim
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
[](https://protocolprobe.com/mcp/servers/com.simvito/esim)
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