# DOTmed MCP Server: Medical Equipment Tools (`subrosa/dotmed-mcp-server`) Actor

MCP server giving AI agents live tools for DOTmed.com medical equipment data: search listings and auctions, look up a specific item, and compare current prices by category and manufacturer. Built for Claude, ChatGPT, Cursor, and other MCP clients.

- **URL**: https://apify.com/subrosa/dotmed-mcp-server.md
- **Developed by:** [Sub Rosa](https://apify.com/subrosa) (community)
- **Categories:** E-commerce, AI
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $30.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## DOTmed MCP Server

An MCP (Model Context Protocol) tool server that gives Claude, ChatGPT,
Cursor, and any other MCP-compatible AI assistant live access to
DOTmed.com's medical equipment marketplace — search, listing lookup, and
price comparison — as callable tools instead of a dataset. Built on the
same extraction logic as the `dotmed-equipment` Actor, exposed as
always-ready tools via Apify Actor Standby rather than a run-once crawl.

### Who uses this and for what

**A procurement analyst working in Claude or ChatGPT** who wants to ask
"what's a fair asking price for a used Siemens CT scanner right now"
without leaving the chat — the assistant calls `compare_prices` and
answers with the actual current range, not a training-data guess.

**An agentic workflow inside Cursor or a custom agent** that needs to
check equipment availability or price a component as one step in a
larger task (a purchasing bot, a refurbishment-margin calculator) —
`search_equipment` and `get_listing` give it structured tool calls
instead of a scraping step it would have to build itself.

**A biomedical engineer's AI assistant** sourcing a specific replacement
part — asks for a manufacturer-filtered search and gets back real
listings with condition, price, and seller, in one tool call.

### Tools

#### `search_equipment`

Search a category, optionally filtered by manufacturer. Returns up to
`maxResults` (1–10, default 5) items with full detail.

```json
{ "category": "dental", "manufacturer": "Planmeca", "maxResults": 5 }
```

#### `get_listing`

Full detail for one known DOTmed listing or auction URL (as returned by
`search_equipment`).

```json
{ "url": "https://www.dotmed.com/auction/dental-x-ray/planmeca/proone/282916" }
```

#### `compare_prices`

Samples a category (optionally filtered by manufacturer) and returns
min/max/average asking price for fixed listings and the current-bid
range for auctions — a quick market check before buying or selling.

```json
{ "category": "cardiology", "sampleSize": 10 }
```

Real output from a live call (2026-09-26):

```json
{
  "category": "cardiology",
  "manufacturer": null,
  "sampledItems": 5,
  "fixedListings": null,
  "auctions": { "count": 5, "minUsd": 50, "maxUsd": 11000, "avgUsd": 2270 }
}
```

Category slugs match `dotmed-equipment`'s: `imaging`, `cardiology`,
`dental`, `surgical`, `laboratory`, `endoscopy`, `respiratory`,
`neonatal`, `homecare-rehab`, `veterinary`, `ophthalmology` — all
verified live 2026-09-26.

### Connecting an MCP client

This Actor runs in Standby mode — always ready, no run to start. Point
your MCP client at its container URL with your Apify API token as a
bearer token:

```json
{
  "mcpServers": {
    "dotmed": {
      "url": "https://<your-run>.apify.actor/mcp",
      "headers": { "Authorization": "Bearer <YOUR_APIFY_API_TOKEN>" }
    }
  }
}
```

### Pricing

Pay-per-event. Two events:

- **Actor start** — $0.01, charged once when a Standby instance starts
  (not per tool call — Standby instances serve many calls once running).
- **Tool call** — $0.03, charged once per completed call to any of the
  three tools.

### Limits and honesty

- Every tool call makes one or more live requests to DOTmed.com under
  the house's declared identity — there is no caching between calls
  beyond what DOTmed itself serves fresh. A `search_equipment` or
  `compare_prices` call with `maxResults`/`sampleSize` near 10 makes up
  to 11 requests (1 category page + up to 10 detail pages) and can take
  several seconds.
- Same data limits as `dotmed-equipment`: `specifications`,
  `sellerLocation`, `sellerType`, `auctionEndsAt`, and `listedAt` are
  always null (see that Actor's README for why). Query-string
  pagination is never used (robots.txt disallows it) — a search only
  ever samples the first ~15 items DOTmed's own category page embeds.
- `get_listing` only fetches `dotmed.com/listing/` or `/auction/` URLs —
  it refuses anything else, so a client cannot use this tool as a
  general-purpose fetcher.
- No personal data. Same Rule 5 handling as `dotmed-equipment`: business
  names only, contact-prose patterns filtered from descriptions.

### Legal

Same basis as `dotmed-equipment`: this server fetches only logged-out
public pages that DOTmed's robots.txt permits, under the declared
identity `SubRosaBot/1.0`, at a polite rate. See that Actor's README for
the full Legal section — it applies identically here since both Actors
crawl the same source the same way.

### Changelog

See `CHANGELOG.md`.

### Support

Open an issue on this Actor's Issues tab. The house replies within one
day.

# Changelog

This Actor's version history is a separate document: https://apify.com/subrosa/dotmed-mcp-server/changelog.md

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("subrosa/dotmed-mcp-server").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("subrosa/dotmed-mcp-server").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call subrosa/dotmed-mcp-server --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,subrosa/dotmed-mcp-server"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/htXtEcMdDWaexQS0B/builds/5ciyXvzLn34Zi47V7/openapi.json