MCP servers › world.opas › client
MCP server · registry snapshot 2026-11-16 · last tested 2026-11-16
client MCP server
Registry name world.opas/client
Opas World for Clients — the publisher's title
by opas.world · domain (the registry's namespace rule)Website ↗
Find and book guided activities on Opas World, and manage your trips and bookings. — the publisher's description
Summary
world.opas/client is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain opas.world.
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
- required
- Last tested
- 2026-11-16
How a client gets in
OAuth sign-in; a client registration endpoint is published
Read from the server's public metadata on 2026-11-16 (opas.world), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list
Not read: The server required a sign-in before it would list anything, and we never use a credential its operator did not give us. Its operator can test it with their own credential, on their own machine, with our self-test command (/docs/selftest). So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- attempted, see below
- Last tested
- 2026-11-16
- Latest version
- 1.0.1, published 2026-11-15 (registry, as of the 2026-11-16 snapshot)
- First listed version
- 2026-11-15 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-16
- Package and repository
- checked 2026-11-16
- 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
New in the registry: not in the list of 2026-11-15, listed on 2026-11-16 with version 1.0.1 (published 2026-11-15).
Source: the official MCP Registry list on 2026-11-15 and on 2026-11-16.
What it is
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://opas.world/api/integration/{provider}/client/mcpCursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"client": {
"url": "https://opas.world/api/integration/{provider}/client/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"client": {
"type": "http",
"url": "https://opas.world/api/integration/{provider}/client/mcp"
}
}
}Claude Code
claude mcp add --transport http client "https://opas.world/api/integration/{provider}/client/mcp"Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"client": {
"type": "streamableHttp",
"url": "https://opas.world/api/integration/{provider}/client/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"client": {
"httpUrl": "https://opas.world/api/integration/{provider}/client/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.client]
url = "https://opas.world/api/integration/{provider}/client/mcp"Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"client": {
"url": "https://opas.world/api/integration/{provider}/client/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://opas.world/api/integration/{provider}/client/mcp" --transport http- The URL contains parts in { } that the entry marks as variables; replace them with your own values.
- 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-16. 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-16. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-16. Source: read 2026-11-16.
- Cline marketplace. Not in the Cline marketplace on 2026-11-16. Source: read 2026-11-16.
Own host
- security.txt. No security.txt at https://opas.world/.well-known/ (HTTP 200, 2026-11-16). Source: opas.world/.well-known/security.txt · read 2026-11-16.
- A2A agent card. No A2A agent card at https://opas.world/.well-known/ (HTTP 200, 2026-11-16). Source: opas.world/.well-known/agent-card.json · read 2026-11-16.
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 #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 opas.world/api/integration/{provider}/client/mcp | Endpoint answered and asked for sign-in | matches | our test · 2026-11-16 |
| No credential declared as required | Required sign-in | differs | our test · 2026-11-16 |
Choosing
Record checks
Public records · not a safety rating1 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-16. 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 world.opas/client
Answered from the data aboveWho publishes world.opas/client?
The registry ties the namespace world.opas to the domain opas.world; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does world.opas/client need an API key or sign-in?
It required sign-in on 2026-11-16. The registry entry declares no required credential; no declaration is not a guarantee.
Has world.opas/client been security tested?
Partly. 1 of the 18 checks that apply to it was exercised. The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. ProtocolProbe publishes no security verdict for a named server.
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
Needs the operator's credential
The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. No security score is given; a check we did not run is never counted as passed.
Why no live read-only session: The server required a sign-in before it would list anything, and we never use a credential its operator did not give us. Its operator can test it with their own credential, on their own machine, with our self-test command (/docs/selftest). — the server's own choice
- Inventory: not run · needs the operator's credential
- Hidden instructions: not run · needs the operator's credential
- Real execution: not run · needs the operator's credential
- Secret leak: not run · needs the operator's credential
- Internal addresses: not run · needs the operator's credential
- Unconfirmed changes: not run · needs the operator's credential
- Bad input: not run · needs the operator's credential
- Model requests: not run · needs the operator's credential
- Sensitive questions: not run · needs the operator's credential
- Folder boundary: not run · needs the operator's credential
- Log leaks: not run · needs the operator's credential
- Hidden content: not run · needs the operator's credential
- Fake assistant turns: not run · needs the operator's credential
- Token passthrough: not run · needs the operator's credential
- Token audience: not run · needs the operator's credential
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
1 exercised17 not run (reason given)0 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 1 of the 18 checks that apply to it was 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.
- 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 1Inventory
tool-listReads the declared tools, resources and prompts.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 3Real execution
real-executionCalls a tool and checks what really happens.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 7Bad input
error-handlingSends bad input and watches how the server answers.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 8Model requests
samplingChecks whether the server asks the client's model to act for it.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 12Hidden content
audience-hidingChecks resources that hide content from the user.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.Needs a real token issued by the server's own sign-in service, which only its operator can give us.not run · needs the operator's credential - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.Needs a real token issued by the server's own sign-in service, which only its operator can give us.not run · needs the operator's credential - 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
Source: our own test, 2026-11-16, 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 session with the server's remote endpoint
- The server asked for sign-in before listing anything.
- 1,986 msFinished: 1 check 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. “world.opas/client: MCP server record.” Data checked 2026-11-16. https://protocolprobe.com/mcp/servers/world.opas/client
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/world.opas/client)
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