digitalassetscan-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_assetA | Submit an asynchronous analysis to the canonical CAI API. Returns the admission document; use get_analysis_job to poll. Unresolved Claims in a successful result are analytical states, not failures. |
| get_analysis_jobA | Retrieve canonical CAI job state and, after success, the unchanged schema 0.6 result. Missing/expired jobs are operational lifecycle conditions, not analytical unresolvedness. |
| list_assetsA | Return the canonical API's neutral 20-asset launch catalog. The catalog is discovery-only, unranked, and does not imply endorsement. |
| get_methodologyA | Return CAI's canonical machine discovery document, including scope, methodology version, endpoint links, and Score/Confidence semantics. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: submitting an analysis, polling for results, listing assets, and retrieving methodology. There is no overlap or ambiguity in what an agent would use each tool for.
All tool names follow a consistent verb_noun snake_case pattern: analyze_asset, get_analysis_job, list_assets, get_methodology. The naming is predictable and easy to navigate.
Four tools is well-scoped for a focused asset-scanning server. Each tool serves a necessary part of the workflow: discover assets, understand methodology, submit analysis, and retrieve results.
The core async analysis lifecycle is covered with submit and poll, and the supporting discovery/methodology tools are present. Minor gaps exist, such as no explicit cancel operation or asset detail retrieval, but the primary workflow is fully usable.