Otovo
REMOTE · OTOVO.COM
Check your Otovo solar system and book, move or cancel visits, with your approval.
Available components
Last scanned (19 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (confirm_change). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 17 Nov 26 0
- 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 security
- “find_inspection_times” added an optional parameter “promo_code” cosmetic
- “get_my_otovo” added an optional parameter “promo_code” cosmetic
- 16 Nov 26 +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.
- 13 Nov 26 +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.
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://otovo.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=otovo.com | CN=WE1,O=Google Trust Services,C=US | 6 Nov 2026 | 4 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 87bf34b2c2b00dac0ec14ff894b9732d |
| SANs: otovo.com, *.otovo.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of otovo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| otovo.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://otovo.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://otovo.com/api/v1/mcp | HTTPS enforced | 301 | https://otovo.com/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
confirm_change Confirm a change ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | True: the customer explicitly approved this preview. |
| preview_id | string | yes | The preview_id preview_change returned, unchanged. |
No output schema declared.
No examples provided.
find_inspection_times Find inspection times ~240
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | yes | – |
| contact | object | yes | – |
| 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. |
No output schema declared.
No examples provided.
get_my_otovo My Otovo ~850
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…
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
preview_change Preview a change ~623
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…
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The change's details, exactly as the tool description names them for that change. |
| change | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · otovo.com
claude mcp add --transport http com-otovo-otovo 'https://otovo.com/api/v1/mcp'
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.