Evaluation report
Passingsearch-console-mcp · mcp023a70d· 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/saurabhsharma2u/search-console-mcp @ 023a70d — ★ 177 · TypeScript · MIT · last push 13 days ago
Manifest detected
kind=mcp slug=search-console-mcp · source=package.json
Slug is URL-safe
"search-console-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/search-console-mcp
Version is semver
1.14.0
Documentation
5 passedDescription quality
13 words · 82 chars — OK but more detail helps
README is present and substantial
14,144 chars · 10 sections · 3 code blocks
Tags / topics declared
13 total — mcp, bing-search, bing webmaster, google-search-console, seo, google analytics (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://searchconsolemcp.saurabh.app/
Safety
3 passedDependencies: known vulnerabilities
OSV.dev clean — 0 high/critical across 10 deps
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: search-console-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: 8 tools declared
sites_list, bing_seo_cannibalization, bing_seo_lost_queries, bing_brand_analysis
MCP: server surface
8 tools · 8 resources · 7 prompts
Maintenance
3 passedRecent activity
last push 13 days ago
Tests detected
1 test directory · 48 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.