Evaluation report
Failing@opentabs-dev/opentabs-plugin-amplitude · mcpc8bff81· 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/opentabs-dev/opentabs @ c8bff81
Manifest detected
kind=mcp slug=opentabs-dev-opentabs-plugin-amplitude · path=plugins/amplitude · source=package.json
Slug is URL-safe
"opentabs-dev-opentabs-plugin-amplitude" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/opentabs-dev-opentabs-plugin-amplitude
Version is semver
0.0.87
Documentation
2 passed2 warningsDescription qualitywarn
Only 5 words · 39 chars — more detail helps discovery
Tell consumers what this artifact does in a full sentence.
README is present and substantialwarn
README present but its contents couldn't be read this scan
Transient fetch issue — re-run the eval to grade the README's substance.
Tags / topics declared
7 total — opentabs-plugin, opentabs, mcp, modelcontextprotocol, chrome-extension, ai-agent (+1)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Safety
3 passedDependencies: known vulnerabilities
OSV.dev clean — 0 high/critical across 1 dep
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
2 passed2 warnings1 failedMCP: launch pathfail
No bin entry and no `scripts.start` in package.json
Add either `"bin": { "your-mcp": "./dist/index.js" }` or `"scripts": { "start": "node ./dist/index.js" }`.
Scan incompletewarn
GitHub returned 502 Detected 28 artifacts before stopping.
Check the portal server logs for the underlying network error.
MCP: @modelcontextprotocol/sdk in dependencieswarn
No @modelcontextprotocol/sdk dependency declared
Run `npm i @modelcontextprotocol/sdk` so consumers can audit your stack.
MCP: ESM package
"type": "module"
MCP: server surface
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.