portfolio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List all projects with optional filters. Returns name, stack, deployment, github, last modified. |
| get_projectB | Get deep info about one project: stack, deps, git, deployment, revenue readiness, LOC. |
| search_projectsA | Search across project names, READMEs, package descriptions, and dependency names. |
| deployment_mapA | Full deployment overview: what's on Vercel, VPS, Netlify, Railway, Docker, or local-only. Grouped by platform. |
| check_healthB | Check if a deployed project is reachable. Pings known URLs for Vercel/Netlify projects. |
| git_overviewA | Scan all projects for git state: uncommitted changes, no remote, stale repos (90+ days without commits). |
| revenue_scanA | Analyze a project's monetization readiness. Checks auth, payments, landing page, deployment, API, README. Returns score 1-10 and suggested path. |
| find_opportunitiesA | Rank ALL projects by revenue potential. Returns top opportunities with scores, what's ready, what's missing, effort estimate, and suggested pricing. |
| suggest_actionsB | For a project, generate concrete monetization steps in priority order. |
| learn_patternsA | Scan ALL projects to learn the developer's patterns: preferred frameworks, common stacks, architecture choices, strengths. Claude uses this to build better. |
| outdated_depsB | Check a project for outdated npm/pip dependencies and security vulnerabilities. |
| stale_projectsB | Find projects with no git commits in 90+ days, sorted by staleness. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Several tools have overlapping boundaries. git_overview and stale_projects both identify projects with no commits in 90+ days, and deployment_map and list_projects both provide project lists with deployment information. This creates real ambiguity for an agent choosing between them.
Most tools follow a clear verb_noun pattern like list_projects, get_project, search_projects, check_health, and find_opportunities. The exceptions are deployment_map and git_overview, which are noun phrases rather than verb-led names, but the naming remains largely predictable and readable.
Twelve tools is within a reasonable range for a portfolio analysis server and each tool serves a distinct functional area overall. The count is slightly higher than necessary due to redundant stale-project logic and the partial overlap between deployment_map and list_projects, but it is not excessive.
The tool surface covers project discovery, deep inspection, deployment status, health checks, git hygiene, dependency vulnerabilities, revenue analysis, and opportunity ranking. Minor gaps exist, such as no bulk dependency scan across all projects and no direct action/deploy tools, but these are workable within the server's apparent analysis-focused purpose.