Evaluation report
Warningsfinancial-modeling-prep-mcp-server · mcpcef864e· 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/imbenrabi/Financial-Modeling-Prep-MCP-Server @ cef864e — ★ 137 · TypeScript · Apache-2.0 · last push 6 weeks ago
Manifest detected
kind=mcp slug=financial-modeling-prep-mcp-server · source=package.json
Slug is URL-safe
"financial-modeling-prep-mcp-server" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/financial-modeling-prep-mcp-server
Version is semver
2.6.10
Documentation
5 passedDescription quality
20 words · 139 chars — "Model Context Protocol server for Financial Modeling Prep (FMP) API, exposing 25…"
README is present and substantial
4,445 chars · 10 sections · 3 code blocks
Tags / topics declared
60 total — mcp, ai, assistant, fmp, financial modeling prep, financial data (+54)
README has usage / example sections
found: Quick Start · Installation · Usage
Homepage / docs URL declared
https://github.com/imbenrabi/Financial-Modeling-Prep-MCP-Server
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
13 high/critical advisories — [email protected] (HIGH: GHSA-35jp-ww65-95wh) · [email protected] (HIGH: GHSA-3g43-6gmg-66jw) (+11)
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
5 passedMCP: launch path
bin: fmp-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "^1.27.1"
MCP: SDK version pinned
pinned at "^1.27.1"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 6 weeks ago
Tests detected
45 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.