mcpdirectory.dev
9,129 servers · updated 23 Sept

College Roi MCP server

community Active last commit 2 mo
{
  "mcpServers": {
    "college-roi": {
      "command": "npx",
      "args": [
        "-y",
        "college-roi-mcp@latest",
        "college-roi-mcp"
      ]
    }
  }
}
file .mcp.json (in your project root)install npx -y college-roi-mcpversion 1.0.1

What it does

This server provides access to U.S. college return-on-investment data, including 30-year net present value for 500 colleges and lifetime ROI for 19 major categories and 115 CIP subfields. It is for developers, advisors, and analysts who need to query college affordability and career outcomes data without authentication.

  • Compare lifetime ROI across different majors to help students evaluate career paths.
  • Find the best-value colleges in a specific state or region based on resident tuition costs.
  • Analyze the financial penalty of attending college out-of-state versus in-state over a 30-year period.

Tools this server exposes

ToolDoes
list_majorsReturns compact ROI rows for major categories and subfields, including median and mean lifetime ROI, percentage that never break even, and break-even age.
get_majorRetrieves the full record for a single major, including ROI distribution percentiles, completion-adjusted ROI, dropout ROI, and AI-exposure detail.
search_collegesSearches the 500 colleges by name, state, or control type, returning resident and non-resident 30-year NPV, cost of attendance, and median earnings.
get_collegeReturns the full record for a single college, including IPEDS unitid and FREOPP coverage.
best_value_collegesLists each state's best-value four-year colleges at resident pricing, or returns a nationwide top-pick summary.
out_of_state_penaltyRanks public four-year colleges by the reduction in 30-year NPV for non-residents compared to residents.
get_api_infoReturns metadata for the underlying API, including endpoints, license, dataset DOI, and attribution information.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.