TAM MCP Server logo

TAM MCP Server

Unclaimed

by gvaibhav

A comprehensive Model Context Protocol (MCP) server for market sizing analysis, TAM/SAM calculations, and industry research. Built with TypeScript, Express.js, and following the MCP specification.

Install

$docker run -p 3000:3000 --env-file .env tam-mcp-server

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
ai-toolsbusiness-intelligencemarket-analysismcp-servermodel-context-protocoltypescript

More in AI & ML

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

30 of 30 tools

Documented tools (30)

From project documentation. A server handshake does not verify each tool’s description or behavior.

asset_management_research

Institutional asset management research

best_practices_guide

Best practices for market analysis

company_financials_retriever

Enhanced company financial data retrieval

competitive_intelligence

Competitive landscape analysis

corporate_strategy_entry

Fortune 500 market entry strategy analysis

crisis_management_analysis

Emergency market analysis for crisis response

data_validation

Cross-source data quality validation

esg_sustainability_analysis

ESG and sustainability market analysis

generic_data_query

Direct data source service access

industry_analysis

Enhanced multi-source industry analysis

industry_data

Detailed industry intelligence with trends and key players

industry_search

Basic industry data search from sources

international_expansion

Global market entry strategy analysis

investment_screening

Investment opportunity screening

market_comparison

Multi-market comparative analysis

market_forecasting

Time series forecasting with scenarios

market_opportunities

Market gap identification

market_opportunity_scan

Rapid market opportunity identification

market_segments

Hierarchical market segmentation

market_size

Advanced market size estimation with confidence scoring

market_size_calculator

Market size estimation and calculations

private_equity_research

Investment committee packages for PE deals

regulatory_impact_assessment

Regulatory change impact analysis

sam_calculator

Serviceable Addressable Market analysis

startup_funding_pitch

Series A-C funding presentations with TAM/SAM analysis

tam_analysis

Advanced Total Addressable Market calculations

tam_calculator

Basic Total Addressable Market calculations

technology_disruption_analysis

Technology disruption impact assessment

tool_guidance

Interactive guide to TAM MCP Server tools

venture_capital_thesis

VC investment thesis development

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about TAM MCP Server

How do I connect TAM MCP Server to Claude?
The listing records `docker run -p 3000:3000 --env-file .env tam-mcp-server` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop as compatible clients.
Is TAM MCP Server free?
The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can TAM MCP Server do?
TAM MCP Server documents 30 tools to the agent, including asset_management_research, best_practices_guide, company_financials_retriever. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.