Evaluation report
Warningsflint-chart-mcp · mcpc8e20b0· 2 months ago
Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.
Structural
5 passedRepository is reachable
https://github.com/microsoft/flint-chart @ c8e20b0 — ★ 1,383 · TypeScript · MIT · last push today
Manifest detected
kind=mcp slug=flint-chart-mcp · path=packages/flint-mcp · source=package.json
Slug is URL-safe
"flint-chart-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/flint-chart-mcp
Version is semver
0.2.0
Documentation
5 passedDescription quality
22 words · 159 chars — "Model Context Protocol server for Flint — compile, validate, and render semantic…"
README is present and substantial
8,437 chars · 9 sections · 5 code blocks
Tags / topics declared
15 total — mcp, model-context-protocol, flint, flint-chart, visualization, charts (+9)
README has usage / example sections
no labeled section but 5 code blocks document usage
Homepage / docs URL declared
https://microsoft.github.io/flint-chart/
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
1 high/critical advisory — [email protected] (HIGH: GHSA-7f2v-3qq3-vvjf)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE file at repo root
LICENSE
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Kind-specific
6 passedMCP: launch path
bin: flint-chart-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.29.0"
MCP: SDK version pinned
pinned at "^1.29.0"
MCP: ESM package
"type": "module"
MCP: 4 tools declared
render_chart, compile_chart, validate_chart, list_chart_types
MCP: server surface
4 tools · 2 resources · 1 prompt
Maintenance
3 passedRecent activity
last push today
Tests detected
3 test directories · 36 test files
CI configuration detected
GitHub Actions (4 workflows)
Behavioral
This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.