mcp server
spektralwerk-docs
Documentation for the Spektralwerk spectrometer SCPI API as a streamable HTTP MCP Server
Description as published by the maintainer. Source
- version 0.1
- slowing
- documentation
- document understanding
slowing — Registry entry last updated 2026-04-27. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
fetch_complete_documentation- Get the complete documentation for the Spektralwerk. Use this only if you can't find the relevant parts through the chapter search, as this fills up a lot of your context.
fetch_complete_error_documentation- Get the complete list of error codes and explanation for the Spektralwerk SCPI API. Warning: This will fill a lot of your available context.
fetch_complete_glossary- Get the complete glossary for terms relevant for understanding Spektralwerk API documentation specifics. Use this only if you can't find a definition through the get_single_glossary_entry search.
get_error_explanation_for_error_code(error_input)- Retrieve the meaning for a single error code given by the Spektralwerk SCPI API. Required: error_input.
get_single_glossary_entry(term_name)- Get the Spektralwerk glossary definition for a given term. Required: term_name.
list_documentation_chapters- Returns a list of available Spektralwrk API documentation headings. Use this to decide wich part of the docs you want to read.
read_documentation_chapter(name)- Read a specific Spektralwerk API documentation chapter by giving its exact name. Required: name.
Last successful function declaration observed on . Source: https://en.silicann.com/spectrometers/spektralwerk-documentation/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://en.silicann.com/spectrometers/spektralwerk-documentation/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-04-27 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-04-27 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 7 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | en.silicann.com | |
| mcp endpoint status | ok | The server listed 7 functions when asked. | as of probe | en.silicann.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json