# Remoto interpreting (ProZ.com) (remote · www.proz.com)

Find interpreters, quote per-minute prices and get start links on Remoto by ProZ.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.proz.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp.md), [page](https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp)

## Channel facts

- Endpoint: `https://www.proz.com/remoto/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.3`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1964 tokens (~115/item across 17 items; 9 tools + 8 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Remoto interpreting (ProZ.com) MCP server?

Remoto interpreting (ProZ.com) is a hosted endpoint at https://www.proz.com/remoto/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-proz-remoto 'https://www.proz.com/remoto/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-proz-remoto": {
      "url": "https://www.proz.com/remoto/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-proz-remoto": {
      "type": "http",
      "url": "https://www.proz.com/remoto/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-proz-remoto]
url = "https://www.proz.com/remoto/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-proz-remoto": {
      "type": "remote",
      "url": "https://www.proz.com/remoto/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-proz-remoto --url 'https://www.proz.com/remoto/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-proz-remoto:
    url: "https://www.proz.com/remoto/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-proz-remoto": {
      "Transport": "http",
      "Url": "https://www.proz.com/remoto/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-proz-remoto -t streamable-http -u 'https://www.proz.com/remoto/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-proz-remoto": {
      "type": "http",
      "url": "https://www.proz.com/remoto/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 72, +1)

- [functional] Server version: 1.1.2 → 1.1.3

### 2026-10-31 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 70)

First indexed and scored.

## MCP tools (9)

### `list_services` (~70 tokens)

List Remoto services

Remoto's interpreting services — on-demand video/audio, Phone Line (dial-in OPI), scheduled calls, sign language, simultaneous interpreting (RSI) for events, business/agency portal, partner API, pro bono — with who each is for, how it works, how it's billed and a link.

Output parameters:

- `services` (array)

### `resolve_language` (~125 tokens)

Resolve a language name

Remoto's language code for a language name, including sign languages. Accepts informal names, aliases, dialects, countries/demonyms and codes ("Farsi", "Tagalog", "Brazilian Portuguese", "Afghan", "ASL", "es") and returns the best matches.

Input parameters:

- `limit` (integer): Most matches to return (default 5).
- `query` (string, required): Language name, alias, dialect, country/demonym or code, e.g. "Farsi", "Tagalog", "Afghan", "ASL", "es".

Output parameters:

- `hint` (string)
- `matches` (array)
- `query` (string)

### `check_language_pair` (~125 tokens)

Check a language pair

Whether Remoto covers a language pair and whether someone can connect now (available_now) or booking ahead is recommended (book_ahead). Never returns interpreter counts. For uncovered pairs it explains the hand-match and English-relay options.

Input parameters:

- `source` (string, required): Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").
- `target` (string, required): Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").

Output parameters:

- `alternatives` (object)
- `availability` (string): available_now = interpreters online now; book_ahead = booking ahead recommended. Never a count.
- `links` (object)
- `message` (string)
- `source` (object)
- `supported` (boolean)
- `target` (object)

### `get_price_quote` (~212 tokens)

Get a price quote

Client price for a language pair: per-minute USD with all platform fees included, billed per second after a one-minute minimum; scheduled calls are a fixed total (minutes × per-minute price). With interpreter_id the result is that interpreter's exact price; without it, the pair's typical price and range.

Input parameters:

- `duration_minutes` (integer): Scheduled: booked length (default 60). On demand: expected length for an estimate (default 10).
- `interpreter_id` (string): Interpreter whose exact price is quoted. When absent, the quote is the pair's typical price and range.
- `mode` (string): on_demand (default) or scheduled.
- `source` (string, required): Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").
- `target` (string, required): Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").

Output parameters:

- `basis` (string)
- `billing` (object)
- `currency` (string)
- `estimate` (object)
- `interpreterId` (string)
- `mode` (string)
- `notes` (array)
- `rangePerMinute` (object)
- `ratePerMinute` (number): Exact client price per minute for the chosen interpreter, all platform fees included.
- `scheduledTotal` (object)
- `source` (object)
- `startLink` (object)
- `target` (object)
- `typicalRatePerMinute` (number)

### `find_interpreters` (~294 tokens)

Find interpreters

Searches Remoto's public interpreter directory by language pair, specialty (medical, legal…), country, mode, online now and HIPAA agreement on file. Returns a short list of public profile fields: name, languages with per-minute price, specialties, rating, online now, profile link. Headlines are interpreter-written text (marked userWritten).

Input parameters:

- `country` (string): ISO 3166 two-letter country where the interpreter is based, e.g. US, MX.
- `hipaa_only` (boolean): Only interpreters with a HIPAA agreement on file.
- `interpreting_mode` (string)
- `limit` (integer): Results per page (default 5, max 10).
- `online_only` (boolean): Only interpreters online right now (for an immediate call).
- `page` (integer)
- `sort` (string)
- `source` (string): Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").
- `specialty` (string): Subject area, e.g. medical, legal, mental health, immigration, education, business.
- `target` (string): Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").
- `verified_only` (boolean): Only interpreters with identity/compliance checks on file.

Output parameters:

- `directoryUrl` (string)
- `hasMore` (boolean)
- `interpreters` (array)
- `page` (number)

### `get_interpreter` (~78 tokens)

Get an interpreter's profile

One interpreter's public profile: languages with per-minute prices, specialties, interpreting modes, rating, online now, experience and profile link. The headline and bio are interpreter-written text (marked userWritten).

Input parameters:

- `interpreter_id` (string, required): Interpreter id: the number in the public profile URL (/profile/<id>), or the profile URL itself.

Output parameters:

- `avatarUrl` (string|null)
- `callTypes` (array)
- `country` (string|null)
- `countryCode` (string|null)
- `experienceYears` (number|null)
- `id` (string)
- `interpretingModes` (array)
- `languagePairs` (array)
- `name` (string)
- `onlineNow` (boolean)
- `proBonoAvailable` (boolean)
- `profileUrl` (string)
- `rating`
- `specialties` (array)
- `userWritten` (object): Text the interpreter wrote for their public profile; not written or checked by Remoto.
- `verification`

### `get_open_slots` (~201 tokens)

Get bookable times

Bookable times for one interpreter, using Remoto's booking calendar rules. Most interpreters take scheduled-call requests instead of fixed slots (bookingRoute = scheduled_request): the person proposes a date, time and length and the interpreter confirms.

Input parameters:

- `from` (string): First day, YYYY-MM-DD (default today).
- `interpreter_id` (string, required): Interpreter id: the number in the public profile URL (/profile/<id>), or the profile URL itself.
- `source` (string): Language pair being booked (prices the slot).
- `target` (string): Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").
- `timezone` (string): IANA timezone for the returned times, e.g. America/New_York (default UTC).
- `to` (string): Last day, YYYY-MM-DD (default from + 13 days, max 31 days).

Output parameters:

- `bookingRoute` (string)
- `bookingUrl` (string)
- `from` (string)
- `interpreterId` (string)
- `message` (string)
- `price`
- `slotDurationMinutes` (number)
- `slots` (array)
- `timezone` (string)
- `to` (string)
- `truncated` (boolean)

### `get_start_link` (~252 tokens)

Get a link to start or book

A link the person opens to start an on-demand call or book a scheduled one, prefilled with the language pair and/or interpreter. Payment is entered on Remoto's page (card, Apple Pay, Google Pay, PayPal; guests need no account). This tool creates nothing and charges nothing.

Input parameters:

- `duration_minutes` (integer): Scheduled only: booked length in minutes.
- `interpreter_id` (string): Interpreter id: the number in the public profile URL (/profile/<id>), or the profile URL itself.
- `mode` (string, required): on_demand = connect now; scheduled = book a time.
- `source` (string): Source language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").
- `starts_at` (string): Scheduled only: the chosen start time (ISO 8601 with offset, e.g. a bookable time's startsAt). With interpreter_id, source and target the link is a price-locked booking link.
- `target` (string): Target language: a name ("Farsi", "Brazilian Portuguese", "ASL") or code ("fas", "spa", "ase").

Output parameters:

- `description` (string)
- `expiresAt` (string)
- `lockedPrice` (object)
- `mode` (string)
- `priceLocked` (boolean)
- `url` (string)

### `search_help` (~80 tokens)

Search Remoto help

Search Remoto's support articles, FAQ and security/privacy/HIPAA facts (BAA on request, encryption, recordings, payments, GDPR). Returns snippets with source links.

Input parameters:

- `limit` (integer)
- `query` (string, required): Question or keywords, e.g. "HIPAA BAA", "how is billing calculated", "phone line PIN".

Output parameters:

- `query` (string)
- `results` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 72
- 2026-11-02: 72
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70

## Common questions

### What is the Remoto interpreting (ProZ.com) MCP server?

Remoto interpreting (ProZ.com) is an MCP server listed in the public MCP registry as com.proz/remoto. Find interpreters, quote per-minute prices and get start links on Remoto by ProZ. This page covers its hosted endpoint (https://www.proz.com/remoto/api/mcp).

### Is the Remoto interpreting (ProZ.com) MCP server safe to use?

Remoto interpreting (ProZ.com) scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Remoto interpreting (ProZ.com) MCP server expose?

Remoto interpreting (ProZ.com) exposes 9 tools: list_services, resolve_language, check_language_pair, get_price_quote, find_interpreters, and 4 more. Their descriptions and schemas cost roughly 1,437 tokens of context every time the server is loaded.

### Does the Remoto interpreting (ProZ.com) MCP server require authentication?

No. We connected to Remoto interpreting (ProZ.com) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Remoto interpreting (ProZ.com) MCP server still maintained?

Remoto interpreting (ProZ.com) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Remoto interpreting (ProZ.com) MCP server?

VerifyMCP ran 14 checks on Remoto interpreting (ProZ.com), covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.proz.com/remoto/api/mcp
- Website: https://www.proz.com/remoto
- Changelog RSS feed: https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-proz-remoto/remoto-api-mcp