Evaluation report
Warnings@anyproto/anytype-mcp · mcp627d3db· 3 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/anyproto/anytype-mcp @ 627d3db — ★ 451 · TypeScript · MIT · last push 4 days ago
Manifest detected
kind=mcp slug=anyproto-anytype-mcp · source=package.json
Slug is URL-safe
"anyproto-anytype-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/anyproto-anytype-mcp
Version is semver
1.2.8
Documentation
4 passed1 warningDescription qualitywarn
Only 6 words · 35 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantial
6,335 chars · 5 sections · 11 code blocks
Tags / topics declared
6 total — anytype, api, mcp, server, mcp-server, modelcontextprotocol
README has usage / example sections
found: Quick Start · Example · Installation
Homepage / docs URL declared
https://github.com/anyproto/anytype-mcp#readme
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
1 high/critical advisory — [email protected] (HIGH: GHSA-hmw2-7cc7-3qxx)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE file at repo root
LICENSE.md
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Kind-specific
5 passedMCP: launch path
bin: anytype-mcp
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: server surface
0 tools
Maintenance
3 passedRecent activity
last push 4 days ago
Tests detected
6 test directories · 10 test files
CI configuration detected
GitHub Actions (2 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.