# Otovo (remote · otovo.com)

Check your Otovo solar system and book, move or cancel visits, with your approval.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `otovo.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-otovo-otovo/api-v1-mcp.md), [page](https://verifymcp.io/servers/com-otovo-otovo/api-v1-mcp)

## Channel facts

- Endpoint: `https://otovo.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (confirm_change).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2172 tokens (~543/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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).
  - 92% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Otovo MCP server?

Otovo is a hosted endpoint at https://otovo.com/api/v1/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-otovo-otovo 'https://otovo.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-otovo-otovo": {
      "url": "https://otovo.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-otovo-otovo": {
      "type": "http",
      "url": "https://otovo.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-otovo-otovo]
url = "https://otovo.com/api/v1/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-otovo-otovo --url 'https://otovo.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-otovo-otovo:
    url: "https://otovo.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-otovo-otovo": {
      "Transport": "http",
      "Url": "https://otovo.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-otovo-otovo -t streamable-http -u 'https://otovo.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-otovo-otovo": {
      "type": "http",
      "url": "https://otovo.com/api/v1/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-20 (score 65, +1)

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

### 2026-11-18 (score 64, +1)

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

### 2026-11-17 (score 63, 0)

- [security] Tool “get_my_otovo” rewrote its description, which is the text the model reads
- [security] Tool “preview_change” rewrote its description, which is the text the model reads
- [cosmetic] “find_inspection_times” added an optional parameter “promo_code”
- [cosmetic] “get_my_otovo” added an optional parameter “promo_code”

### 2026-11-16 (score 63, +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-13 (score 62, +1)

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

### 2026-11-12 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 61)

First indexed and scored.

## MCP tools (4)

### `get_my_otovo` (~850 tokens)

My Otovo

Reads what a customer can see in their Otovo portal, one view at a time. Changes nothing. With a scheduling code and no account, three views: booking_status (the address, services offered, the visit already scheduled and whether it can be moved or cancelled, open access questions, the support line), booking_options (code and service_type, optional week_start, location_id and promo_code: bookable times for a new visit, best first, with the price and what the promo code does) and reschedule_options (code, optional week_start: times the scheduled visit can move to). With a connected account, site_id selects one of the customer's sites when they have several: sites, profile, home, summary; monitoring (production now, equipment status, alerts and when each reading was taken; a missing or stale reading is not zero production), monitoring_page, monitoring_history (node_id, query range day|week|month|year and date), monitoring_devices (node_id), monitoring_device (node_id, device_id), monitoring_energy_rate; connect_system (the monitoring providers Otovo connects, the fields each connection needs and the portal's setup steps; id = one provider); energy, energy_usage (query start_date, end_date, granularity), energy_bills, energy_plans; service (visits, work orders, bookable services), appointment (id), appointment_tracking (id: where the crew is on the day), scheduling (what can be booked or moved, open access questions), booking_options (service_type, optional week_start and promo_code) and reschedule_options (optional week_start); work_order (id), repair (id), site_report (id; photos stay in the portal); quotes, quote (id); billing, billing_records (query limit, cursor), billing_record (id; the invoice PDF is a portal link), payment_methods, subscription, subscription_plans, subscription_terms (query tier, billing_interval); documents (pending, signed, project and historical); leases, lease (id); hour_bank; notification_settings. Reading booking times for a connected cus…

Input parameters:

- `code` (string): Without an account: the customer's scheduling code, the last part of the otovo.com/book/... link they were sent. It cannot be looked up from other details.
- `device_id` (string): A device from view monitoring_devices (monitoring_device).
- `id` (string): The record a single-record view is about: an appointment, work order, site report, quote, billing record (its quote id), lease (project id), or a provider key for connect_system.
- `location_id` (string): booking_options: which property, when the booking covers more than one.
- `node_id` (string): A monitoring node from view monitoring (monitoring_history, monitoring_devices, monitoring_device).
- `promo_code` (string): booking_options: a promo code the customer gave. The answer's charge is the price with it and promo says whether it applied, their Otovo Care discount is larger, or why it was refused.
- `query` (object): Extra filters the view takes, as named in the description: for example {"range":"month","date":"2026-10-01"} for monitoring_history, {"limit":20} for billing_records, {"tier":"care"} for subscription…
- `service_type` (string): booking_options: the kind of new visit. booking_status or view scheduling lists what is actually offered.
- `site_id` (string): Connected customers: one of their own sites, a site_id from view sites. Needed when they have more than one.
- `view` (string, required): What to read. See the tool description for what each view holds and which parameters it takes.
- `week_start` (string): booking_options, reschedule_options: earliest date to search from, YYYY-MM-DD. Step it forward a week at a time to look further out.

### `find_inspection_times` (~240 tokens)

Find inspection times

Finds real inspection or panel-cleaning appointment times at a street address, for a person with no Otovo account or scheduling link. The times come from the dispatch planner, so a crew can reach the address in each one. Creates the person's customer record (name, contact details, address) so the planner can route to it; books nothing. Each returned slot is a selected_slot value for a request_inspection change. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.

Input parameters:

- `address` (object, required)
- `contact` (object, required)
- `notes` (string): Anything the crew should know before arriving.
- `preferred_week_start` (string): Earliest date to search from, YYYY-MM-DD. Omit for the soonest available.
- `promo_code` (string): A promo code the customer gave. The answer's charge is the price with it and promo says whether it applied or why it was refused; pass it again in request_inspection.
- `service_type` (string): Which visit to plan. Defaults to inspection.

### `preview_change` (~623 tokens)

Preview a change

Prepares one change and returns a plain summary of exactly what it would do, with a preview_id. Changes nothing: the change happens only when that preview_id is confirmed. Without an account: book_appointment (code; body service_type, selected_slot exactly as booking_options returned it, location_id, property_details {someone_home_during_service, ok_to_proceed_without_customer, pets_on_property, gated_community, gate_code, dog_access_considerations, access_instructions}, expected_total_cents, promo_code), reschedule_appointment (code; body selected_slot from reschedule_options), cancel_appointment (code; body reason), request_quote (body contact {first_name, last_name, email, phone, sms_consent: true when the customer agreed to texts, consent_label}, address {line1, line2, city, state, zip, country}, service_title in the customer's words, panel_count, notes, source) and request_inspection (body: the contact and address the times were found for, service_type, selected_slot, promo_code, notes). A connected customer passes site_id instead of code for the three appointment changes, and also has: save_access_details (body property_details), reject_quote (id; body reason, lost_reason), connect_system (provider; body fields: the fields the connect_system view lists for that provider), disconnect_system (provider), set_energy_rate (body currency, importRatePerKwh, exportRatePerKwh as decimal strings), change_subscription_tier (body targetTier, billingInterval), cancel_subscription (body cancelAtPeriodEnd), resume_subscription, withdraw_document (id), update_notification_settings (body: the settings to change, as notification_settings names them), request_lease_offer (id; body language), accept_lease_offer (id; body quote_id). payment_method, payment, sign_document, lease_bank_account and subscribe are not carried out by this connector: previewing one returns the portal link where the customer does it themselves. Serves every Otovo region: without a connected account the sc…

Input parameters:

- `body` (object): The change's details, exactly as the tool description names them for that change.
- `change` (string, required): The one change to preview. See the tool description for what each takes in body.
- `code` (string): Without an account: the customer's scheduling code, the last part of the otovo.com/book/... link they were sent. It cannot be looked up from other details.
- `id` (string): The record the change is about: a quote (reject_quote), document envelope (withdraw_document) or lease project (request_lease_offer, accept_lease_offer).
- `provider` (string): connect_system, disconnect_system: the provider key from get_my_otovo view connect_system.
- `site_id` (string): Connected customers: one of their own sites, a site_id from view sites. Needed when they have more than one.

### `confirm_change` (~143 tokens)

Confirm a change

Carries out exactly the change one preview described, using its preview_id, with confirmed=true meaning the customer approved that preview. Each preview_id stands for one change. An appointment receipt with status reconciliation_required means the outcome is not yet known. A change can update the customer's visit, calendar, account, subscription or monitoring and sends them the notices the portal would. Serves every Otovo region: without a connected account the scheduling code, preview or address selects the region; a connected customer is served where their account lives.

Input parameters:

- `confirmed` (boolean, required): True: the customer explicitly approved this preview.
- `preview_id` (string, required): The preview_id preview_change returned, unchanged.

## Diagnostics

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

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 62
- 2026-11-12: 61
- 2026-11-11: 61

## Common questions

### What is the Otovo MCP server?

Otovo is an MCP server listed in the public MCP registry as com.otovo/otovo. Check your Otovo solar system and book, move or cancel visits, with your approval. This page covers its hosted endpoint (https://otovo.com/api/v1/mcp).

### Is the Otovo MCP server safe to use?

Otovo scores 65 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 Otovo MCP server expose?

Otovo exposes 4 tools: get_my_otovo, find_inspection_times, preview_change, confirm_change. Their descriptions and schemas cost roughly 1,856 tokens of context every time the server is loaded.

### Does the Otovo MCP server require authentication?

No. We connected to Otovo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Otovo MCP server still maintained?

Otovo is still listed as active in the MCP registry. We last reached this channel on 21 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 Otovo MCP server?

VerifyMCP ran 13 checks on Otovo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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://otovo.com/api/v1/mcp
- Repository: https://github.com/otovo/otovo-mcp
- Website: https://otovo.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-otovo-otovo/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-otovo-otovo/api-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-otovo-otovo/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-otovo-otovo/api-v1-mcp
