eVerbary MCP server
Official# eVerbary MCP server
Order certified translations of official documents (birth and marriage certificates, diplomas, transcripts, court records) from Claude, ChatGPT, Cursor or any MCP client. Translations are done by human translators in the US and come with a signed certificate of accuracy accepted by USCIS, courts and universities.
[eVerbary](https://www.everbary.com) works with 1,250+ law firms and translators in the US. This repository holds:
- the connection details for the hosted MCP server, `https://orders.everbary.com/mcp`
- `everbary-mcp`, a small npm package that bridges the hosted server to clients that only speak stdio
- `everbary`, a Python client for the REST API ([`python/`](python/))
- a Postman collection for the REST API ([`postman/`](postman/))
## What the assistant can do
| Tool | What it does |
|---|---|
| `list_languages` | Languages and per-page prices |
| `list_document_types` | Common document types and what each needs |
| `get_quote` | Price and delivery time for this account (team discounts included) |
| `upload_document` | Send a source document (PDF, image, Word) |
| `create_order` | Place the order with the uploaded files |
| `pay_order` | Pay with the account's prepaid balance or saved card, within spending limits |
| `order_status` | Progress, expected delivery and payment state |
| `list_my_orders` | Recent orders |
| `get_payment_link` | A link anyone can use to pay an unpaid order |
Every tool carries MCP annotations (`readOnlyHint` / `destructiveHint`), so clients can ask before anything that places or pays an order. By default an order is capped at $500 and an account at $1,000 a day.
## Connect
### Claude (claude.ai, Desktop)
Settings → Connectors → Add custom connector → URL `https://orders.everbary.com/mcp`. Sign in with your eVerbary account when asked.
### Claude Code
```bash
claude mcp add --transport http everbary https://orders.everbary.com/mcp
```
### ChatGPT
Add `https://orders.everbary.com/mcp` as a custom connector (developer mode) and sign in with your eVerbary account.
### Cursor, VS Code, Windsurf and other stdio clients
```json
{
"mcpServers": {
"everbary": {
"command": "npx",
"args": ["-y", "everbary-mcp"]
}
}
}
```
The first run opens your browser to sign in to eVerbary. To skip the sign-in, put an API key in the environment:
```json
{
"mcpServers": {
"everbary": {
"command": "npx",
"args": ["-y", "everbary-mcp"],
"env": { "EVERBARY_API_KEY": "ev_live_..." }
}
}
}
```
A test key (`ev_test_...`) in `EVERBARY_API_KEY` runs every tool against the sandbox described below: uploads, quotes, orders and payments are pretend, and nothing is charged or sent to a translator.
The bridge is a thin wrapper around [mcp-remote](https://github.com/geelen/mcp-remote): nothing runs locally except the connection.
## REST API
If you are building your own integration (case management software, intake forms, a firm's internal tools), use the REST API directly:
- Reference: https://orders.everbary.com/v1/docs
- Overview and keys: https://www.everbary.com/integrations/api
- Python: `pip install everbary` ([`python/`](python/))
- Postman: import [`postman/everbary.postman_collection.json`](postman/everbary.postman_collection.json) and set `apiKey`
Test keys (`ev_test_...`) work on every REST endpoint and on the MCP server against a sandbox: orders are pretend, nothing is charged or sent to a translator, and each order moves `new` → `in-progress` → `completed` on its own with a sample translation, firing your webhook at every step. Ask support@everbary.com for a test key.
Case management software can also open a hosted checkout with the documents already attached (`POST /v1/checkout/sessions`). Try the demo: https://orders.everbary.com/checkout/demo
## Pricing
From $24.95 per page. Rush options and notarization are extra. Current prices: https://www.everbary.com/pricing
## Links
- MCP setup guide: https://www.everbary.com/integrations/ai-assistants
- Official MCP Registry: `com.everbary.www/orders`
- Security: https://www.everbary.com/security
- Privacy: https://www.everbary.com/privacy
- Support: support@everbary.com
## License
MIT
TDQS
Scored across 9 tools
Each tool targets a distinct step or resource in the translation workflow: reference listing (languages, document types), quoting, uploading, ordering, paying, and status checking. The closest pairs (order_status vs list_my_orders, pay_order vs get_payment_link) are clearly differentiated by their descriptions as single-order detail vs recent list, and account-means payment vs a shareable link.
Most tools follow a consistent verb_noun pattern (list_languages, get_quote, upload_document, create_order, pay_order, get_payment_link, list_my_orders). The exception is order_status, which drops the verb and breaks the pattern, though it remains understandable.
Nine tools is well-scoped for a translation ordering service, covering reference data, the quote/upload/order/pay/status lifecycle, and payment links. No tool feels redundant or out of place.
The core order lifecycle is well covered: reference info, quoting, document upload, order creation, payment (account or link), and status/listing with delivered file links. Possible minor gaps include canceling or modifying an order and retrieving file downloads via a dedicated tool, but agents can work around these.