_ registry / mcp streamable-http · checked 3h ago

otovo

https://otovo.com

Registry code: 1060e3d559acc5b4

api record

Otovo's tools for its solar and home energy customers: get_my_otovo reads, preview_change prepares one change and says exactly what it will do, confirm_change carries it out after the customer approves, and find_inspection_times shows a new customer real inspection times. Three ways in. A customer with an Otovo scheduling link has a code (the last part of otovo.com/book/...): ask for it, read view booking_status first, then booking_options, and preview_change book_appointment. A customer with no link either wants pricing (preview_change request_quote) or an inspection now…

endpoint
https://otovo.com/api/v1/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is otovo live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is otovo free to use?
Yes — the hub reached it with no key and no payment.
What tools does otovo have?
4 tools: find_inspection_times, confirm_change, get_my_otovo, preview_change.
Is otovo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
557ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_inspection_times unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "contact",
    "address"
  ],
  "properties": {
    "notes": {
      "type": "string",
      "description": "Anything the crew should know before arriving."
    },
    "address": {
      "type": "object",
      "required": [
        "line1",
        "city",
        "state",
        "zip"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "description": "Postal code."
        },
        "city": {
          "type": "string",
          "description": "City."
        },
        "line1": {
          "type": "string",
          "description": "Street address."
        },
        "line2": {
          "type": "string",
          "description": "Apartment, unit or suite."
        },
        "state": {
          "type": "string",
          "description": "State or province."
        },
        "country": {
          "type": "string",
          "description": "ISO country code. Defaults to US."
        }
      },
      "additionalProperties": false
    },
    "contact": {
      "type": "object",
      "required": [
        "first_name",
        "last_name",
        "email",
        "phone"
      ],
      "properties": {
        "email": {
          "type": "string",
          "description": "Email address."
        },
        "phone": {
          "type": "string",
          "description": "Phone number."
        },
        "last_name": {
          "type": "string",
          "description": "Customer's last name."
        },
        "first_name": {
          "type": "string",
          "description": "Customer's first name."
        }
      },
      "additionalProperties": false
    },
    "service_type": {
      "enum": [
        "inspection",
        "panel_cleaning",
        "inspection_panel_cleaning"
      ],
      "type": "string",
      "description": "Which visit to plan. Defaults to inspection."
    },
    "preferred_week_start": {
      "type": "string",
      "description": "Earliest date to search from, YYYY-MM-DD. Omit for the soonest available."
    }
  },
  "additionalProperties": false
}
    arguments 91 lines
  • confirm_change unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "preview_id",
    "confirmed"
  ],
  "properties": {
    "confirmed": {
      "type": "boolean",
      "const": true,
      "description": "True: the customer explicitly approved this preview."
    },
    "preview_id": {
      "type": "string",
      "description": "The preview_id preview_change returned, unchanged."
    }
  },
  "additionalProperties": false
}
    arguments 19 lines
  • get_my_otovo unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "view"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "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."
    },
    "code": {
      "type": "string",
      "description": "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."
    },
    "view": {
      "enum": [
        "sites",
        "profile",
        "home",
        "summary",
        "monitoring",
        "monitoring_page",
        "monitoring_history",
        "monitoring_devices",
        "monitoring_device",
        "monitoring_energy_rate",
        "connect_system",
        "energy",
        "energy_usage",
        "energy_bills",
        "energy_plans",
        "service",
        "appointment",
        "appointment_tracking",
        "scheduling",
        "booking_status",
        "booking_options",
        "reschedule_options",
        "work_order",
        "repair",
        "site_report",
        "quotes",
        "quote",
        "billing",
        "billing_records",
        "billing_record",
        "payment_methods",
        "subscription",
        "subscription_plans",
        "subscription_terms",
        "documents",
        "leases",
        "lease",
        "hour_bank",
        "notification_settings"
      ],
      "type": "string",
      "description": "What to read. See the tool description for what each view holds and which parameters it takes."
    },
    "query": {
      "type": "object",
      "description": "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_terms."
    },
    "node_id": {
      "type": "string",
      "description": "A monitoring node from view monitoring (monitoring_history, monitoring_devices, monitoring_device)."
    },
    "site_id": {
      "type": "string",
      "description": "Connected customers: one of their own sites, a site_id from view sites. Needed when they have more than one."
    },
    "device_id": {
      "type": "string",
      "description": "A device from view monitoring_devices (monitoring_device)."
    },
    "week_start": {
      "type": "string",
      "description": "booking_options, reschedule_options: earliest date to search from, YYYY-MM-DD. Step it forward a week at a time to look further out."
    },
    "location_id": {
      "type": "string",
      "description": "booking_options: which property, when the booking covers more than one."
    },
    "service_type": {
      "enum": [
        "panel_cleaning",
        "inspection",
        "inspection_panel_cleaning",
        "generator",
        "project_consultation"
      ],
      "type": "string",
      "description": "booking_options: the kind of new visit. booking_status or view scheduling lists what is actually offered."
    }
  },
  "additionalProperties": false
}
    arguments 97 lines
  • preview_change unknown 3h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "change"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The record the change is about: a quote (reject_quote), document envelope (withdraw_document) or lease project (request_lease_offer, accept_lease_offer)."
    },
    "body": {
      "type": "object",
      "description": "The change's details, exactly as the tool description names them for that change."
    },
    "code": {
      "type": "string",
      "description": "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."
    },
    "change": {
      "enum": [
        "book_appointment",
        "reschedule_appointment",
        "cancel_appointment",
        "request_quote",
        "request_inspection",
        "save_access_details",
        "reject_quote",
        "connect_system",
        "disconnect_system",
        "set_energy_rate",
        "change_subscription_tier",
        "cancel_subscription",
        "resume_subscription",
        "withdraw_document",
        "update_notification_settings",
        "request_lease_offer",
        "accept_lease_offer",
        "payment_method",
        "payment",
        "sign_document",
        "lease_bank_account",
        "subscribe"
      ],
      "type": "string",
      "description": "The one change to preview. See the tool description for what each takes in body."
    },
    "site_id": {
      "type": "string",
      "description": "Connected customers: one of their own sites, a site_id from view sites. Needed when they have more than one."
    },
    "provider": {
      "type": "string",
      "description": "connect_system, disconnect_system: the provider key from get_my_otovo view connect_system."
    }
  },
  "additionalProperties": false
}
    arguments 57 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1060e3d559acc5b4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1060e3d559acc5b4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1060e3d559acc5b4/badge.svg)](https://brick.blue/agent/1060e3d559acc5b4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.