For metering teams running VIVAVIS IDSpecto on their own instance
Pexon builds a VIVAVIS IDSpecto API connector so Claude, ChatGPT or Copilot can read meter readings and load profiles from the customer's own IDSpecto system. VIVAVIS describes an ADMIN WebService API and publishes no endpoint list. No IDSpecto MCP server was found on 26 October 2026.
Why IDSpecto is hard for agents
01 · Family
The flyer dated 8 October 2020 names DAYOS, collector, GWA, IDEX, enVIEW, scadalink and CLS Operator. The pages read on 26 October 2026 add ADMIN and MDUS. The connector is scoped to the modules that are installed.
02 · Docs
ADMIN is described as ranging from CSV to a WebService API for billing, workforce and EDM. DAYOS is described with an integrator interface. Neither page publishes a base path or a resource list. Every backend below is confirmed against your release.
03 · Identity
No sign-in method is published. The 2020 flyer says tenants sit in separate parts of one system. A shared account would answer for that account's tenant. The submetering deployment of DAYOS is described as SaaS in a German computer centre. The connector runs where it can already reach the instance.
04 · Writes
MDUS names connect and disconnect. CLS-Operator names control-box schedules and switching, including IEC 60870-5-104. DAYOS names a SmartGrid.Connector for the same class of control. Those operations stay off the manifest. Device keys, which DAYOS says it stores, are not a tool.
Checked 26 October 2026
| What we found | |
|---|---|
| Interfaces | IDSpecto.ADMIN WebService API (WebService, CSV, docs not published) · IDSpecto.DAYOS integrator interface (not named, docs not published) · IDSpecto.MDUS (SAP AMI, docs not published) · IDSpecto.CLS-Operator WebService (WebService, IEC 60870-5-104, IEC 61850, docs not published) |
| Authentication | No sign-in method for the WebService API or the integrator interface was on the pages read on 26 October 2026. A flyer dated 8 October 2020 describes separate tenants in one system. The connector uses the asking person's login on that tenant. |
| Vendor MCP server | No vendor server. No IDSpecto MCP server is named on the VIVAVIS pages read on 26 October 2026, and a search that day did not return one from VIVAVIS. |
| Vendor AI assistant | None found. |
| Other connectors | None found. |
VIVAVIS AG (DE). Public utilities and energy companies. A VIVAVIS flyer dated 8 October 2020 says about 300 customers in Germany use IDSpecto. The DAYOS page read on 26 October 2026 says the platform supports municipal utilities and the processing of several million metering points. The 2020 count was not repeated on those pages.
What we build
Built on what VIVAVIS AG documents: meter readings, load profiles, registers, device data, metering points. Backends named below are documented resources; "confirmed in blueprint" means the vendor documentation sits behind a login and the resource is checked against your release first.
# vivavis-idspecto-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
list_metering_points: # -> metering points this login may see
backend: confirmed in blueprint
mode: read
get_meter_readings: # metering point, period -> meter readings
backend: confirmed in blueprint
mode: read
get_load_profile: # metering point, period -> load profile
backend: confirmed in blueprint
mode: read
get_register: # metering point, register -> register value
backend: confirmed in blueprint
mode: read
get_device: # device -> device data this login may see
backend: confirmed in blueprint
mode: read
audit: every call logged with user, tool, arguments and the IDSpecto responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
One interface per row
01
WebService, CSV. Documentation is not published. VIVAVIS says ADMIN interfaces to billing, workforce and EDM range from a CSV file to a WebService API, and that the system has more than 300 meter drivers; no operation list was public on 26 October 2026
02
not named. Documentation is not published. DAYOS is described with automatable interfaces and a use-case-based integrator interface; the submetering page calls them open data interfaces and says that DAYOS deployment can run as SaaS in a German computer centre
03
SAP AMI. Documentation is not published. the DAYOS page says MDUS carries SAP AMI master-data synchronisation and meter readings, and also connect and disconnect, which stay off the manifest
04
WebService, IEC 60870-5-104, IEC 61850. Documentation is not published. VIVAVIS describes WebService interfaces and IEC 60870-5-104 for control-box processes and a measured-value transfer; switching and schedule import stay off the manifest
IDSpecto holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
When this is the wrong page
If the record is a BelVis portfolio or a Schleupen.CS bill, use that connector. IDSpecto holds meter readings and load profiles on the customer's own VIVAVIS instance. A VIVAVIS MCP server for IDSpecto was not found on 26 October 2026; if one appears, this page is the restriction and identity work, not a second writer.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your IDSpecto owners and checks every backend against your release and licence. Week two tests whether a person's own IDSpecto permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named IDSpecto administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Not one that was named on the IDSpecto pages read on 26 October 2026. A search that day for a VIVAVIS or IDSpecto MCP server did not return one from VIVAVIS.
Meter readings, load profiles, registers and device data for the metering points that login may see, on the customer's own IDSpecto instance. VIVAVIS describes a WebService API on IDSpecto.ADMIN and an integrator interface on DAYOS, and does not publish the paths, so each backend is confirmed in the blueprint. Connect, disconnect and switching stay off the tool list.
The call uses that person's login. A VIVAVIS flyer dated 8 October 2020 describes separate tenants in one system. No sign-in method was published on the pages read on 26 October 2026. A shared IDSpecto account would answer for that account's tenant, which is why the connector does not use one.
The two-week Readiness Blueprint is fixed at €4,900: the tool list, which IDSpecto modules are installed, identity tested end to end, and a costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Thirty minutes with the engineer who would build the connector, with your IDSpecto administrator in the room if you like.