io.github.amakkar-leap/convergent-provider-directory
REMOTE · CONVERGENT-MCP-DUMMY.LIVELYCOAST-4BE0CD2B.EASTUS2.AZURECONTAINERAPPS.IO · SCANNED SEP 24
Search a healthcare provider directory and get full provider details by id.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 273 tokens (~136/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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.
remote · convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io
claude mcp add --transport http amakkar-leap-convergent-provider-directory 'https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp'
{
"mcpServers": {
"amakkar-leap-convergent-provider-directory": {
"url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
}
}
} {
"servers": {
"amakkar-leap-convergent-provider-directory": {
"type": "http",
"url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
}
}
} [mcp_servers.amakkar-leap-convergent-provider-directory] url = "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
{
"$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 mcp add amakkar-leap-convergent-provider-directory --url 'https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp' --transport streamable-http
mcp_servers:
amakkar-leap-convergent-provider-directory:
url: "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp" {
"McpServers": {
"amakkar-leap-convergent-provider-directory": {
"Transport": "http",
"Url": "https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp"
}
}
} assistant mcp add amakkar-leap-convergent-provider-directory -t streamable-http -u 'https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=livelycoast-4be0cd2b.eastus2.azurecontainerapps.io,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US | 3 Sept 2026 | 12 Dec 2026 | RSA 2048 | SHA384-RSA | 4900d5dbec623562b316fcd43e000000d5dbec |
| SANs: *.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io, *.scm.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io, *.internal.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io, *.ext.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io, livelycoast-4be0cd2b.eastus2.azurecontainerapps.io | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000f33206537ee42ae4f00000000000f |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| azurecontainerapps.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp | Verified | 200 | |
| http (plaintext) | http://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp | HTTPS enforced | 301 | https://convergent-mcp-dummy.livelycoast-4be0cd2b.eastus2.azurecontainerapps.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_provider_details Get Provider Details ~54
Get the full detail record for one provider by 'id'. Use the 'id' value returned by search_provider.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The provider id returned by search_provider (e.g. 'prov-001'). |
No output schema declared.
No examples provided.
search_provider Search Providers ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'). |
No output schema declared.
No examples provided.
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.