# VisioForge SDK Assistant (remote · mcp.visioforge.com)

VisioForge .NET SDK assistant: API reference, code examples and deployment guides.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.visioforge.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp.md), [page](https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp)

## Channel facts

- Endpoint: `https://mcp.visioforge.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2068 tokens (~114/item across 18 items; 14 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VisioForge SDK Assistant MCP server?

VisioForge SDK Assistant is a hosted endpoint at https://mcp.visioforge.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-visioforge-sdk-docs 'https://mcp.visioforge.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-visioforge-sdk-docs": {
      "url": "https://mcp.visioforge.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-visioforge-sdk-docs": {
      "type": "http",
      "url": "https://mcp.visioforge.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-visioforge-sdk-docs]
url = "https://mcp.visioforge.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-visioforge-sdk-docs": {
      "type": "remote",
      "url": "https://mcp.visioforge.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-visioforge-sdk-docs --url 'https://mcp.visioforge.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-visioforge-sdk-docs:
    url: "https://mcp.visioforge.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-visioforge-sdk-docs": {
      "Transport": "http",
      "Url": "https://mcp.visioforge.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-visioforge-sdk-docs -t streamable-http -u 'https://mcp.visioforge.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-visioforge-sdk-docs": {
      "type": "http",
      "url": "https://mcp.visioforge.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 77, +8)

- [security improvement] Authorization: unverified → partial
- [functional] Server version: 1.1.0 → 1.2.0

### 2026-11-06 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (14)

### `list_media_blocks` (~133 tokens)

List available VisioForge media blocks, optionally filtered by category. Media blocks are the building blocks of media processing pipelines. Categories include: Sources, Sinks, VideoEncoders, AudioEncoders, VideoDecoders, VideoProcessing, AudioProcessing, AudioRendering, VideoRendering, Demuxers, Parsers, OpenGL, OpenCV, Nvidia, Decklink, AWS, RTSPServer, Bridge, Special, Outputs.

Input parameters:

- `category` (string|null): Optional category to filter by (e.g., 'Sources', 'Sinks', 'VideoEncoders'). Leave empty to list all categories with their blocks.

### `get_nuget_packages_snippet` (~237 tokens)

Get .csproj snippet with required NuGet packages for a specific deployment scenario. Returns XML snippet ready to copy-paste into your project file.

Input parameters:

- `includeOptional` (boolean): Include optional packages? (e.g., OpenCV, AWS, specialized camera support)
- `platform` (string, required): Target platform, required. One of: Windows, Linux, macOS, Android, iOS, macCatalyst.
- `projectType` (string, required): Project type, required. One of: WPF, WinForms, WinUI, Console, MAUI, Avalonia, Uno, Blazor. MAUI, Avalonia and Uno are treated as multi-target, so the native redists are emitted under a target-framew…
- `sdkType` (string, required): SDK type, required. VideoCapture for camera/screen/IP-camera recording, MediaPlayer for playback, VideoEdit for timeline editing — those are the three products. MediaBlocks is the low-level pipeline…

### `get_enum_values` (~118 tokens)

Get all values of a VisioForge SDK enum type with descriptions. Useful for understanding available options for configuration properties (e.g., MediaBlockType, video codecs, audio formats, pixel formats).

Input parameters:

- `enumName` (string, required): Enum name (e.g., 'MediaBlockType', 'MediaBlockPadMediaType', 'MediaBlockPadDirection'). Can be short name or fully qualified.
- `filter` (string|null): Optional text filter to show only matching enum values (e.g., 'H264' to find H264-related values)

### `list_sdk_classes` (~75 tokens)

List core VisioForge SDK classes. These are the main entry-point classes for building media applications: VideoCaptureCoreX (video capture/recording), VideoEditCoreX (video editing), MediaPlayerCoreX (media playback), MediaInfoReaderX (media analysis), SimplePlayerCoreX (simple playback), and more.

### `list_namespaces` (~76 tokens)

Browse VisioForge SDK namespaces hierarchically. Shows child namespaces and classes within a given namespace. Start with 'VisioForge.Core' or leave empty to see top-level namespaces.

Input parameters:

- `parentNamespace` (string|null): Parent namespace to browse (e.g., 'VisioForge.Core.MediaBlocks'). Leave empty for top-level.

### `get_platform_specific_config` (~57 tokens)

Get platform-specific file copying/build configuration code. Returns MSBuild targets or post-build scripts for special deployment requirements.

Input parameters:

- `platform` (string, required): Platform: Windows, macOS, maccatalyst, Android, iOS, Linux

### `search_api` (~145 tokens)

Search across the entire VisioForge SDK API — class names, method names, property names, event names, and their documentation text. Returns ranked results. Use this when you don't know the exact class name, or to find all classes related to a concept (e.g., 'RTSP streaming', 'video overlay', 'audio capture').

Input parameters:

- `maxResults` (integer): Maximum number of results to return (default: 20, max: 50)
- `query` (string, required): Search query — can be a class name, method name, concept, or description (e.g., 'RTSP', 'video resize', 'audio equalizer', 'H264 encoder settings')

### `get_media_block_info` (~97 tokens)

Get detailed information about a specific media block including its properties, methods, events, input/output pads, constructor parameters, and documentation. Use this to understand how to configure and use a specific media block in a pipeline.

Input parameters:

- `blockName` (string, required): Name of the media block (e.g., 'H264EncoderBlock', 'RTSPSourceBlock', 'MP4SinkBlock'). Can be the short name or full qualified name.

### `get_pipeline_template` (~156 tokens)

Get a media block pipeline template for a specific use case. Returns the list of required blocks and how to connect them, along with C# code to build the pipeline.

Input parameters:

- `useCase` (string, required): Use case description. Available templates: 'rtsp-to-mp4' (record network camera to file), 'webcam-preview' (show webcam on screen), 'webcam-to-rtmp' (stream webcam live), 'file-transcode' (convert vi…

### `get_class_info` (~90 tokens)

Get detailed information about any VisioForge SDK class, including its full list of properties, methods, events, constructors, base class, interfaces, and documentation. Works for both core SDK classes and media blocks.

Input parameters:

- `className` (string, required): Class name (e.g., 'VideoCaptureCoreX', 'H264EncoderSettings', 'MP4SinkSettings'). Can be short name or fully qualified.

### `get_method_signature` (~69 tokens)

Get the detailed signature and documentation for a specific method on a class. Useful when you need to understand a method's parameters, return type, and behavior.

Input parameters:

- `className` (string, required): The class name that contains the method
- `methodName` (string, required): The method name to look up

### `list_deployment_guides` (~168 tokens)

List available deployment guides for VisioForge SDK. Filter by platform, project type, SDK type, or scenario. Returns a list of guides with titles, summaries, and tags.

Input parameters:

- `platform` (string|null): Filter by platform (optional). Values: Windows, Linux, macOS, Android, iOS, All
- `projectType` (string|null): Filter by project type (optional). Values: WPF, WinForms, MAUI, Avalonia, Console, Uno, Blazor
- `sdkType` (string|null): Filter by SDK (optional). Values: MediaBlocks, VideoCapture, MediaPlayer, VideoEdit
- `tag` (string|null): Filter by tag (optional). Values: docker, cloud, mobile, desktop, rtsp, streaming

### `get_code_example` (~213 tokens)

Get a code example for a common VisioForge SDK scenario. Returns complete, working C# code snippets that demonstrate how to use the SDK for tasks like video capture, RTSP streaming, media playback, and more.

Input parameters:

- `scenario` (string, required): Scenario name. Available: 'webcam-capture' (capture from webcam to MP4), 'rtsp-playback' (play RTSP stream), 'rtsp-to-mp4' (record RTSP to MP4 file), 'webcam-to-rtmp' (stream webcam to RTMP/YouTube/F…

### `get_deployment_guide` (~66 tokens)

Get the complete deployment guide for a specific scenario. Returns detailed instructions, code snippets, NuGet packages, and platform-specific notes.

Input parameters:

- `guideId` (string, required): Guide ID from list_deployment_guides (e.g., 'windows-desktop', 'maui-mobile')

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp#diagnostics

## Score history

- 2026-11-21: 83
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 81
- 2026-11-17: 81
- 2026-11-16: 80
- 2026-11-15: 80
- 2026-11-14: 80
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 78
- 2026-11-10: 78
- 2026-11-09: 77
- 2026-11-08: 77
- 2026-11-07: 69
- 2026-11-06: 69
- 2026-11-05: 69

## Common questions

### What is the VisioForge SDK Assistant MCP server?

VisioForge SDK Assistant is an MCP server listed in the public MCP registry as com.visioforge/sdk-docs. VisioForge .NET SDK assistant: API reference, code examples and deployment guides. This page covers its hosted endpoint (https://mcp.visioforge.com/mcp).

### Is the VisioForge SDK Assistant MCP server safe to use?

VisioForge SDK Assistant scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the VisioForge SDK Assistant MCP server expose?

VisioForge SDK Assistant exposes 14 tools: list_media_blocks, get_nuget_packages_snippet, get_enum_values, list_sdk_classes, list_namespaces, and 9 more. Their descriptions and schemas cost roughly 1,700 tokens of context every time the server is loaded.

### Does the VisioForge SDK Assistant MCP server require authentication?

No. We connected to VisioForge SDK Assistant without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the VisioForge SDK Assistant MCP server still maintained?

VisioForge SDK Assistant is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the VisioForge SDK Assistant MCP server?

VerifyMCP ran 13 checks on VisioForge SDK Assistant, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.visioforge.com/mcp
- Repository: https://github.com/visioforge/mcp-server
- Website: https://www.visioforge.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-visioforge-sdk-docs/mcp
