Agent Known Issues#

VA-MCP Slow Initialization (Hugging Face Rate Limiting)#

Symptom:

The VA-MCP server initialization is extremely slow, and logs show HTTP 429 errors from Hugging Face.

Cause:

The VA-MCP server downloads a model from Hugging Face. Unauthenticated requests are subject to rate limiting, which causes repeated 429 errors and significantly slows down the initialization process.

Solution:

Provide a Hugging Face access token with READ permissions via the HF_TOKEN environment variable.

  1. Log in to Hugging Face

  2. Go to your profile settings and navigate to Access Tokens

  3. Create a new token with Read permission

  4. Set the environment variable:

export HF_TOKEN=hf_your_token_here

Or add it to your .env file:

HF_TOKEN=hf_your_token_here

Warning

The token must have READ permission only.

Snapshot Timestamp Accuracy (LVS Profile)#

Symptom:

When requesting a snapshot at a specific timestamp (e.g., “take a snapshot at 3 seconds from <sensor_id>”), the actual frame captured may not precisely match the requested timestamp.

Cause:

This is a known limitation in the current frame extraction implementation. The snapshot tool may select a nearby frame rather than the exact frame at the requested timestamp.

Solution:

We expect to fix this in the next release.

Empty Chart for Metrics Queries When No Results#

Symptom:

For natural language metrics/occupancy count queries (e.g., How many people are there in camera 1?), when the count is 0 the chart appears empty, which can be confusing.

Cause:

This is a known limitation in the current chart rendering for metrics queries.

Solution:

This will be resolved in a future release.