Skip to content

Otovo MCP server

com.otovo/otovootovo.comstreamable-httpv1.0.0Scanned

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

4 tools: 1 can delete or cancel things and 3 change things.

Tools: 1 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Otovo MCP server can do

The Otovo MCP server is published by otovo.com, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: confirm_change) and create or change data (3 tools: get_my_otovo, find_inspection_times and preview_change). None of its tools only reads.

1 tool brings in text other people can write (confirm_change); 1 tool can send data out of your system (find_inspection_times).

The fixed checks matched 5 findings (long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 11, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • confirm_changeCarries out exactly the change one preview described, using its preview_id, with confirmed=true meaning the customer approved that preview.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Confirm a change
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Changes things 3Claude Code: ask
  • find_inspection_timesFinds real inspection or panel-cleaning appointment times at a street address, for a person with no Otovo account or scheduling link.Can send data out1 finding

    Why it is in this group

    • The name "find_inspection_times" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • outboundThe input takes a destination (input.contact.phone): what the tool writes goes there.

    Findings

    • Warn

      The server marks "find_inspection_times" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "find_inspection_times" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find inspection times
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • get_my_otovoReads what a customer can see in their Otovo portal, one view at a time.2 findings

    Why it is in this group

    • The name "get_my_otovo" says "get": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,173 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ess selects the region; a connected customer is served where their account lives."

      What this check looks for
    • Warn

      The server marks "get_my_otovo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_my_otovo" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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 and location_id: bookable times for a new visit, best first) 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 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 customer can create their own Otovo scheduler link; nothing is sent to them. 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.

    Annotations the server declares

    • title: My Otovo
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_changePrepares one change and returns a plain summary of exactly what it would do, with a preview_id.2 findings

    Why it is in this group

    • The name "preview_change" says "preview": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,086 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ess selects the region; a connected customer is served where their account lives."

      What this check looks for
    • Warn

      The server marks "preview_change" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "preview_change" says "preview": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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), 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, 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 scheduling code, preview or address selects the region; a connected customer is served where their account lives.

    Annotations the server declares

    • title: Preview a change
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:21 UTC, unchanged since Nov 12, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
4
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://otovo.com/.well-known/oauth-protected-resource/api/v1/mcp
Authorization servers
https://otovo.com/oauth/customer
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://otovo.com/api/v1/mcp: tools/list returned 4 tools to an anonymous client, including confirm_change (destructive), get_my_otovo (write), find_inspection_times (write), preview_change (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

3 warn2 info
  • The server marks "get_my_otovo" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_my_otovo" says "get": a word for reading.

    What this check looks for
  • The server marks "find_inspection_times" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "find_inspection_times" says "find": a word for reading.

    What this check looks for
  • The server marks "preview_change" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "preview_change" says "preview": a word for reading.

    What this check looks for
  • The description is 2,173 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ess selects the region; a connected customer is served where their account lives."

    What this check looks for
  • The description is 2,086 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ess selects the region; a connected customer is served where their account lives."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http otovo https://otovo.com/api/v1/mcp
claude mcp add --transport http otovo https://otovo.com/api/v1/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__otovo__get_my_otovo",
      "mcp__otovo__find_inspection_times",
      "mcp__otovo__preview_change"
    ],
    "deny": [
      "mcp__otovo__confirm_change"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as otovo. Review it before you use it.

Capability tags behind 2 rules
  • mcp__otovo__find_inspection_times outbound
  • mcp__otovo__confirm_change untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.otovo/otovo/verify?hash=1378ceccf8c2469d3c13abd56c8baa24929d268a36833a01d45813ad86147db9" | jq -e '.changed == false'

Pinned hash 1378ceccf8c2, from Nov 11, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.otovo/otovo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.otovo/otovo
[![Anlyon Radar](https://radar.anlyon.com/badge/com.otovo/otovo.svg)](https://radar.anlyon.com/servers/com.otovo/otovo)

Source: MCP Registry · repository. Synced Nov 11, 2026, 22:17 UTC.

Otovo MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Otovo MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Otovo MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: confirm_change.

Can the Otovo MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Otovo MCP server have?

4 tools: 1 destructive, 3 write. confirm_change, get_my_otovo, find_inspection_times and preview_change.

Does the Otovo MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Otovo MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): find_inspection_times.

Has the Otovo MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.