NPI Registry
Look up and search US provider records from the CMS NPPES NPI Registry.

618 MCP servers with 12,363+ tools, ready to connect to Claude, ChatGPT, Cursor and Agentman agents over the Model Context Protocol.
35 of 618 connectors in HealthcareShow all
Look up and search US provider records from the CMS NPPES NPI Registry.
Query TCGA histopathology slides — cell-type quantification, tumour-microenvironment features, cohort survival.
Query Yale's harmonized US public-health surveillance data — flu, COVID, RSV, measles, overdose, chronic disease…
Search 41 million biomedical citations and retrieve PMC full text.
Search over 8 million peer-reviewed Wiley journal articles with DOI-linked citations.
Search papers, patents, trials, grants and FDA records, with Smart Citations showing if later work supported or…
Look up, validate and expand SNOMED CT clinical concepts from your AI agent.
Query your own Strava training history from an AI agent.
Search Synapse research datasets and read entity metadata, annotations and provenance.
Generate synthetic human gene expression data from a plain-language experiment description and run differential…
Query US negotiated healthcare rates — hospital, lab, drug, device — plus a payer/provider graph.
Product names and logos belong to their owners. Each connector is built by its own developer, and Agentman is not affiliated with them. The ones Agentman builds and runs are marked “Built and run by Agentman”.
A server that exposes a tool’s capabilities over the Model Context Protocol, so an AI agent can call them directly. It is the standard way to let an assistant act in a system rather than just describe it.
Each server page carries its connection URL, which works in any MCP-compatible client. In Agentman Studio connecting is one click and there is no config file to edit.
Most are not. Each is built by its own developer, and each page names them and links to their documentation. The few Agentman builds and runs are marked “Built and run by Agentman”. Every page lists what the server exposes and cites the sources its factual claims come from.
Each page lists the tools the server exposes. Where we could read the server directly, every tool carries the safety label its vendor gave it: read-only, acts, or destructive. Each page also has a Limits section; read both before connecting anything to a production system.
Connect any of these once and your agents call their tools on their own: on a schedule, in a workflow, with nobody at the keyboard.