Repository navigation
Add Definitive Healthcare plugin (third_party/definitive-healthcare) - #1131
Draft
cursor[bot] wants to merge 1 commit into
Draft
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Danny Jiang <djiang-jq@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unreviewed plugin submission. Nothing here has been reviewed or tested against a live MCP server. Do not merge until someone has followed up with the publisher.
Submission
definitive-healthcare)What this adds
third_party/definitive-healthcare/mcp.json: remote HTTP MCP server using the submittedplugin_urlexactly as given..cursor-plugin/plugin.jsonwith"mcpServers": "./mcp.json", categoryintegrations..cursor-plugin/marketplace.json..claude-plugin/marketplace.jsonis unchanged.Needs follow-up before this can ship
plugin_urlis the company homepage, not an MCP endpoint. The publisher says the MCP server is "incoming" and asked for a discovery call, somcp.jsonwill need the real server URL once they have one.logo_urlis the homepage, not an image. definitivehc.com blocked automated requests (TLS reset), Google/DuckDuckGo favicon services were also blocked, a public favicon mirror had no entry, and there is no official Definitive Healthcare GitHub organization (thedefinitivehcaccount is an unlinked personal account, so its avatar wasn't used).plugin.jsonlogopoints at the best URL found,https://www.definitivehc.com/favicon.ico(not verified).Validation
node scripts/validate-plugins.mjs: All plugins validated successfully.Note
Medium Risk
Scaffold lists an unverified remote MCP URL (company homepage) for a healthcare data integration; users could install something that does not connect until the publisher provides a real endpoint and review completes.
Overview
Adds a new Definitive Healthcare third-party integration under
third_party/definitive-healthcare/, wired like other hosted MCP plugins viaplugin.json,mcp.json, and a plugin README with install steps.The plugin is registered in the marketplace (
.cursor-plugin/marketplace.json) and the root README plugin table so Cursor can discover and install it.The HTTP MCP config currently uses the submitted homepage URL (
https://www.definitivehc.com/), not a dedicated MCP endpoint; the README flags that the server is upcoming and the logo is an unverified favicon URL until the publisher confirms details.Reviewed by Cursor Bugbot for commit 244b729. Bugbot is set up for automated code reviews on this repo. Configure here.