# io.github.amakkar-leap/convergent-provider-directory (remote · convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io)

Search a healthcare provider directory and get full provider details by id.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io`: 79/100 (this document), [markdown](https://verifymcp.io/servers/amakkar-leap-convergent-provider-directory/convergent-mcp-dummy.md), [page](https://verifymcp.io/servers/amakkar-leap-convergent-provider-directory/convergent-mcp-dummy)

## Channel facts

- Endpoint: `https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 273 tokens (~136/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the io.github.amakkar-leap/convergent-provider-directory MCP server?

io.github.amakkar-leap/convergent-provider-directory is a hosted endpoint at https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http amakkar-leap-convergent-provider-directory 'https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "amakkar-leap-convergent-provider-directory": {
      "url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "amakkar-leap-convergent-provider-directory": {
      "type": "http",
      "url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.amakkar-leap-convergent-provider-directory]
url = "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "amakkar-leap-convergent-provider-directory": {
      "type": "remote",
      "url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add amakkar-leap-convergent-provider-directory --url 'https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  amakkar-leap-convergent-provider-directory:
    url: "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "amakkar-leap-convergent-provider-directory": {
      "Transport": "http",
      "Url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add amakkar-leap-convergent-provider-directory -t streamable-http -u 'https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "amakkar-leap-convergent-provider-directory": {
      "type": "http",
      "url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `get_provider_details` (~54 tokens)

Get Provider Details

Get the full detail record for one provider by 'id'. Use the 'id' value returned by search_provider.

Input parameters:

- `id` (string, required): The provider id returned by search_provider (e.g. 'prov-001').

### `search_provider` (~125 tokens)

Search Providers

Search the provider directory by name, specialty, and/or city. Returns a list of matching providers, each with an 'id' that can be passed to get_provider_details for the full record.

Input parameters:

- `acceptingNewPatients` (boolean): If set, only return providers with this intake status.
- `city` (string): City to match (e.g. 'Durham').
- `name` (string): Full or partial provider name to match (e.g. 'Jessica').
- `specialty` (string): Specialty to match (e.g. 'Pediatrics', 'Cardiology').

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/amakkar-leap-convergent-provider-directory/convergent-mcp-dummy#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 78
- 2026-09-22: 78
- 2026-09-21: 78
- 2026-09-20: 77
- 2026-09-19: 77
- 2026-09-18: 76
- 2026-09-17: 76
- 2026-09-16: 75
- 2026-09-15: 75
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 73
- 2026-09-11: 73
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 71
- 2026-09-06: 71
- 2026-09-05: 70
- 2026-09-04: 70

## Common questions

### What is the io.github.amakkar-leap/convergent-provider-directory MCP server?

io.github.amakkar-leap/convergent-provider-directory is an MCP server listed in the public MCP registry as io.github.amakkar-leap/convergent-provider-directory. Search a healthcare provider directory and get full provider details by id. This page covers its hosted endpoint (https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp).

### Is the io.github.amakkar-leap/convergent-provider-directory MCP server safe to use?

io.github.amakkar-leap/convergent-provider-directory scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.amakkar-leap/convergent-provider-directory MCP server expose?

io.github.amakkar-leap/convergent-provider-directory exposes 2 tools: get_provider_details, search_provider. Their descriptions and schemas cost roughly 179 tokens of context every time the server is loaded.

### Does the io.github.amakkar-leap/convergent-provider-directory MCP server require authentication?

No. We connected to io.github.amakkar-leap/convergent-provider-directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.amakkar-leap/convergent-provider-directory MCP server still maintained?

io.github.amakkar-leap/convergent-provider-directory is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp
- Website: https://www.leaporbit.com/
- Changelog RSS feed: https://verifymcp.io/servers/amakkar-leap-convergent-provider-directory/convergent-mcp-dummy.xml
- Changelog JSON feed: https://verifymcp.io/servers/amakkar-leap-convergent-provider-directory/convergent-mcp-dummy.json
- HTML version of this page: https://verifymcp.io/servers/amakkar-leap-convergent-provider-directory/convergent-mcp-dummy