Archived listing / no verified MCP endpoint/Other

Uviqora listing

No MCP endpoint is published. This listing is retained for reference.

Uviqora was a free public pilot, starting in Zurich, for booking people to run short on-site tasks such as pickups, location checks, and condition recording, with no payments through the platform. On 2026-11-16 the docs site said Uviqora was temporarily closed and the MCP endpoint returned HTTP 503. The previous claim that every binding step was enforced server-side has no reachable provider statement, so it is withdrawn and the listing is archived.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

No one right now: the service is temporarily closed.

  • Check whether the provider reopens.
  • Treat the confirmation-enforcement claim as unverified.
  • Do not attempt a connection from this listing.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.