← Registry

Analytics

chartely.com

Analyzes medical records to extract structured events and build detailed, page-cited chronology summaries for case review.

1 endpoint3 known toolsFirst detected August 15, 2026Last detected August 15, 2026

ENDPOINT 1

https://www.chartely.com/api/mcp

No auth detected

MCP server metadata

Name
chartely
Version
1.0.0
Capabilities
tools

Known tools 3

build_chronology

Build a full page-cited medical-record chronology from a case record set.

Inferred read-only
extract_medical_events

Lightweight extraction: pass already-extracted record text and get back just the structured events array (date, provider, facility, type, summary, page_ref, confidence) - no persistence, no narrative synthesis pass.

Inferred read-only
get_chronology

Fetch one previously built chronology by id, including its events.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.chartely]
url = "https://www.chartely.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "chartely": {
      "type": "http",
      "url": "https://www.chartely.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: chartely
Remote MCP URL: https://www.chartely.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "chartely": {
      "url": "https://www.chartely.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "chartely": {
      "type": "http",
      "url": "https://www.chartely.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "chartely",
  "transport": "streamable-http",
  "url": "https://www.chartely.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for chartely.com was fetched 2026-08-21T15:06:57.827Z.

Trust status Neutral

chartely.com is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.