Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Summer

REMOTE · API.GOSUMMER.AI

Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools.

Available components

80 Trust /100

Last scanned (13 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 24 Oct 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security97
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 15099 tokens (~93/item across 161 items; 161 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 37% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 162 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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 Oct 26 +1
    • New tool “summer_account_photo_remove”, which the server declares destructive security
    • New tool “summer_investigations_plan_edit”, which the server declares destructive security
    • New tool “summer_reports_themes_generate”, which the server declares destructive security
    • New tool “summer_reports_themes_review”, which the server declares destructive security
    • New tool “summer_slack_account_disconnect”, which the server declares destructive security
    • New tool “summer_workflows_save”, which the server declares destructive security
    • Tool “summer_account_me” rewrote its description, which is the text the model reads security
    • Tool “summer_github_connection_start” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_list” rewrote its description, which is the text the model reads security
    • Tool “summer_reports_service_metrics” rewrote its description, which is the text the model reads security
    • Tool “summer_slack_sender_update” rewrote its description, which is the text the model reads security
    • Schema quality: 12176 → 15099 ▼ functional
    • New tool “summer_cases_discussions_list” functional
    • New tool “summer_cases_discussions_read” functional
    • New tool “summer_cases_engineering_list” functional
    • New tool “summer_cases_similar_list” functional
    • New tool “summer_github_issues_read” functional
    • New tool “summer_messenger_sms_create” functional
    • New tool “summer_messenger_sms_read” functional
    • New tool “summer_messenger_sms_update” functional
    • New tool “summer_plans_list” functional
    • New tool “summer_reports_agent_timing” functional
    • New tool “summer_reports_samples_list” functional
    • New tool “summer_reports_themes_get” functional
    • New tool “summer_reports_themes_list” functional
    • New tool “summer_slack_account_read” functional
    • New tool “summer_slack_discussions_channels” functional
    • New tool “summer_slack_reader_read” functional
    • New tool “summer_slack_reader_update” functional
    • New tool “summer_teammates_slack_dms_list” functional
    • New tool “summer_teammates_slack_dms_update” functional
    • New tool “summer_teammates_slack_link_create” functional
    • New tool “summer_workflows_history” functional
    • New tool “summer_workflows_list” functional
    • New tool “summer_workflows_request_text” functional
    • “summer_slack_sender_update” added an optional parameter “sender” cosmetic
    • “summer_slack_sender_update” reworded the description of “teammate_id” cosmetic
    • Tool “summer_account_me” changed its title: Show the signed-in person, Summer access status and this connection's grant → Show the signed-in person, Summer access status, profile photo path and this connection's grant cosmetic
    • Tool “summer_github_connection_start” changed its title: Get the Summer browser URL for a company administrator to install and authorize the read-only GitHub App → Get the Summer browser URL for a company administrator to install and authorize the Summer GitHub App cosmetic
    • Tool “summer_integrations_list” changed its title: List provider integrations, their categories, required fields and saved metadata → List provider integrations, their categories, required fields, alternative credential sets and saved metadata cosmetic
    • Tool “summer_reports_service_metrics” changed its title: Read current response and resolution metrics in the company timezone → Read response and resolution metrics, 90-day daily issue/message and timing trends, and weekday/hour incoming-message heatmaps in the company timezone cosmetic
    • Tool “summer_slack_sender_update” changed its title: Choose who posts approved vendor Slack replies: the Summer Ellis app (null) or a Summer Teammate, which then posts from its own Slack account → Choose who posts approved vendor Slack replies: the Summer Ellis app, a Summer Teammate (AI employee) from its own Slack account, or the person who approves each reply, from their own connected Slack account cosmetic
  • 23 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “summer_actions_approve”, which the server declares destructive security
    • New tool “summer_github_connection_disconnect”, which the server declares destructive security
    • New tool “summer_github_sources_save”, which the server declares destructive security
    • New tool “summer_github_sources_sync”, which the server declares destructive security
    • New tool “summer_human_tasks_update”, which the server declares destructive security
    • New tool “summer_imports_intercom_control”, which the server declares destructive security
    • New tool “summer_imports_intercom_preview”, which the server declares destructive security
    • New tool “summer_teammates_slack_disconnect”, which the server declares destructive security
    • Tool “summer_actions_prepare” rewrote its description, which is the text the model reads security
    • Tool “summer_assets_uploads_create” rewrote its description, which is the text the model reads security
    • Tool “summer_cases_get” rewrote its description, which is the text the model reads security
    • Tool “summer_cases_list” rewrote its description, which is the text the model reads security
    • Tool “summer_cases_search” rewrote its description, which is the text the model reads security
    • Tool “summer_client_status” rewrote its description, which is the text the model reads security
    • Tool “summer_company_settings_read” rewrote its description, which is the text the model reads security
    • Tool “summer_events_list” rewrote its description, which is the text the model reads security
    • Tool “summer_guides_authoring” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_save” rewrote its description, which is the text the model reads security
    • Tool “summer_investigations_list” rewrote its description, which is the text the model reads security
    • Tool “summer_knowledge_create” rewrote its description, which is the text the model reads security
    • Tool “summer_knowledge_list” rewrote its description, which is the text the model reads security
    • Tool “summer_runs_list” rewrote its description, which is the text the model reads security
    • Tool “summer_saved_replies_save” rewrote its description, which is the text the model reads security
    • Schema quality: 9319 → 12176 ▼ functional
    • Server version: 0.2.2 → 0.2.4 functional
    • New tool “summer_github_connection_read” functional
    • New tool “summer_github_connection_start” functional
    • New tool “summer_github_folders_list” functional
    • New tool “summer_github_repositories_list” functional
    • New tool “summer_github_sources_read” functional
    • New tool “summer_human_tasks_list” functional
    • New tool “summer_imports_intercom_list” functional
    • New tool “summer_imports_intercom_profiles” functional
    • New tool “summer_slack_channels_describe” functional
    • New tool “summer_slack_channels_list” functional
    • New tool “summer_slack_channels_posting_update” functional
    • New tool “summer_slack_sender_update” functional
    • New tool “summer_teammates_create” functional
    • New tool “summer_teammates_list” functional
    • New tool “summer_teammates_mailbox_get” functional
    • New tool “summer_teammates_mailbox_list” functional
    • New tool “summer_teammates_names_list” functional
    • New tool “summer_teammates_setup_status” functional
    • New tool “summer_teammates_slack_channels_join” functional
    • New tool “summer_teammates_update” functional
    • “summer_actions_prepare” added an optional parameter “replaces_execution” cosmetic
    • “summer_cases_list” added an optional parameter “sentiment” cosmetic
    • “summer_company_settings_update” added an optional parameter “email_subject” cosmetic
    • “summer_knowledge_list” added an optional parameter “tag” cosmetic
    • Tool “summer_actions_prepare” changed its title: Prepare the exact work in the current saved plan for human approval in Summer → Prepare the exact current plan and return its execution ID, approval hash and reviewed work cosmetic
    • Tool “summer_cases_list” changed its title: List company-owned cases or conversations with filters, ordering, page size, coverage and a cursor → List company-owned cases or conversations with emotion filters (sentiment: happy, neutral, upset, angry, sad, mixed or unknown), ordering, page size, coverage and a cursor cosmetic
    • Tool “summer_company_settings_read” changed its title: Read company-wide settings → Read company-wide settings, including the email subject customers see on new support emails cosmetic
    • Tool “summer_guides_authoring” changed its title: Get the reviewed company-specific guide-building instructions for your native coding agent → Read the company's reviewed guide-authoring brief, draft article references and publication state cosmetic
    • Tool “summer_integrations_save” changed its title: Save a custom integration's description, setup instructions and credential names → Save a custom integration's description, setup instructions and credential field names cosmetic
    • Tool “summer_investigations_list” changed its title: Read investigation runs, saved plans, approval state and execution receipts for a case → Read shared investigation runs, saved plans, approval state and execution receipts across the verified customer’s cases, including historical issues cosmetic
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “summer_cases_assignment_update”, which the server declares destructive security
    • New tool “summer_pharmacy_calls_settings_update”, which the server declares destructive security
    • New tool “summer_privacy_requests_create”, which the server declares destructive security
    • New tool “summer_quality_assessments_save”, which the server declares destructive security
    • New tool “summer_quality_scenarios_save”, which the server declares destructive security
    • New tool “summer_saved_replies_save”, which the server declares destructive security
    • New tool “summer_saved_views_delete”, which the server declares destructive security
    • New tool “summer_saved_views_save”, which the server declares destructive security
    • New tool “summer_support_policy_update”, which the server declares destructive security
    • New tool “summer_work_routing_update”, which the server declares destructive security
    • Tool “summer_cases_list” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_list” rewrote its description, which is the text the model reads security
    • Tool “summer_integrations_save” rewrote its description, which is the text the model reads security
    • Tool coverage: 52% → 41% ▼ functional
    • Schema quality: 5322 → 9319 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 0.2.0 → 0.2.2 functional
    • New tool “summer_agent_exclusions_list” functional
    • New tool “summer_cases_assignment_read” functional
    • New tool “summer_cases_customer_profile” functional
    • New tool “summer_cases_search” functional
    • New tool “summer_client_status” functional
    • New tool “summer_integrations_setup_prompt” functional
    • New tool “summer_messenger_conversations_get” functional
    • New tool “summer_messenger_conversations_list” functional
    • New tool “summer_messenger_email_check” functional
    • New tool “summer_messenger_email_create” functional
    • New tool “summer_messenger_email_read” functional
    • New tool “summer_messenger_email_update” functional
    • New tool “summer_messenger_leads_list” functional
    • New tool “summer_messenger_voice_read” functional
    • New tool “summer_messenger_voice_update” functional
    • New tool “summer_pharmacy_calls_settings_read” functional
    • New tool “summer_privacy_requests_list” functional
    • New tool “summer_quality_corrections_list” functional
    • New tool “summer_quality_scenarios_get” functional
    • New tool “summer_quality_scenarios_list” functional
    • New tool “summer_reports_commitments” functional
    • New tool “summer_reports_credits” functional
    • New tool “summer_reports_delivery” functional
    • New tool “summer_reports_service_metrics” functional
    • New tool “summer_runs_list” functional
    • New tool “summer_saved_replies_history” functional
    • New tool “summer_saved_replies_list” functional
    • New tool “summer_saved_views_list” functional
    • New tool “summer_slack_identity_read” functional
    • New tool “summer_slack_identity_update” functional
    • New tool “summer_support_policy_read” functional
    • New tool “summer_work_routing_read” functional
    • “summer_cases_list” added an optional parameter “autonomy” cosmetic
    • “summer_cases_list” added an optional parameter “category” cosmetic
    • “summer_cases_list” added an optional parameter “dismissals” cosmetic
    • “summer_cases_list” added an optional parameter “escalations” cosmetic
    • “summer_cases_list” added an optional parameter “followUps” cosmetic
    • “summer_cases_list” added an optional parameter “internal” cosmetic
    • “summer_cases_list” added an optional parameter “lane” cosmetic
    • “summer_cases_list” added an optional parameter “language” cosmetic
    • “summer_cases_list” added an optional parameter “mine” cosmetic
    • “summer_cases_list” added an optional parameter “pastSla” cosmetic
    • “summer_cases_list” added an optional parameter “plan” cosmetic
    • “summer_cases_list” added an optional parameter “responseDue” cosmetic
    • “summer_cases_list” added an optional parameter “reviewMine” cosmetic
    • “summer_cases_list” added an optional parameter “sandbox” cosmetic
    • “summer_cases_list” added an optional parameter “severity” cosmetic
    • “summer_cases_list” added an optional parameter “sort” cosmetic
    • “summer_cases_list” added an optional parameter “unmatched” cosmetic
    • “summer_cases_list” added an optional parameter “workstream” cosmetic
    • “summer_integrations_list” added an optional parameter “category” cosmetic
    • “summer_integrations_list” added an optional parameter “connection” cosmetic
    • “summer_integrations_list” added an optional parameter “search” cosmetic
    • “summer_integrations_save” added an optional parameter “description” cosmetic
    • “summer_integrations_save” added an optional parameter “instructions” cosmetic
    • Tool “summer_cases_list” changed its title: List company-owned cases or conversations, newest first, with coverage and a cursor → List company-owned cases or conversations with filters, ordering, page size, coverage and a cursor cosmetic
    • Tool “summer_integrations_list” changed its title: List provider integrations, their required fields and saved metadata → List provider integrations, their categories, required fields and saved metadata cosmetic
    • Tool “summer_integrations_save” changed its title: Define a custom integration's credential names and labels → Save a custom integration's description, setup instructions and credential names cosmetic
  • 21 Oct 26 79

    First indexed and scored.

Diagnostics

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 Oct 2026 · Probed https://api.gosummer.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.gosummer.ai CN=YR2,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 RSA 2048 SHA256-RSA 5b02d6e401a0f6a72fbadf52f538e4cda66
SANs: api.gosummer.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.gosummer.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
gosummer.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="summer", error="invalid_token", resource_metadata="https://api.gosummer.ai/.well-known/oauth-protected-resource/mcp", scope="setup cases.read investigations.request actions.prepare actions.approve workspace.write credentials.replace messaging.activate guides.publish automation.manage"

Bearer realm="summer", error="invalid_token", resource_metadata="https://api.gosummer.ai/.well-known/oauth-protected-resource/mcp", scope="setup cases.read investigations.request actions.prepare actions.approve workspace.write credentials.replace messaging.activate guides.publish automation.manage"
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff

Protected resource metadata

Document https://api.gosummer.ai/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.gosummer.ai/mcp
Authorisation server https://gosummer.ai

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.gosummer.ai/mcp Verified 200
http (plaintext) http://api.gosummer.ai/mcp HTTPS enforced 308 https://api.gosummer.ai/mcp
MCP tools · 161 exposed · ~13,767 tokens

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 →

Tool Tokens
summer_teammates_update ~127

Change a teammate's shown name, photo or status, with the expected revision and a reason. Retiring disconnects Slack and keeps the address reserved.

NameTypeReqDescription
avatar_url–yes–
companystringyes–
display_namestringyes–
idempotency_keystring–Reuse the same key when retrying the same change
reasonstringyes–
revisionintegeryesCurrent revision from teammates.list.
statusstringyesRetired teammates keep their address forever and disconnect from Slack.
teammatestringyes–

No output schema declared.

No examples provided.

summer_verification_run ~76

Run supported harmless checks. Unsupported checks are reported as unsupported, never as passed.

NameTypeReqDescription
companystringyesSummer company ID
environmentstringyesEnvironment that owns the resource
idempotency_keystring–Reuse the same key when retrying the same change
targetsarrayyes–

No output schema declared.

No examples provided.

summer_webhooks_list ~39

List webhook endpoints and delivery state.

NameTypeReqDescription
companystringyesSummer company ID
environmentstringyesEnvironment that owns the resource

No output schema declared.

No examples provided.

summer_webhooks_replay ~96

Queue past events after a cursor for delivery again to one endpoint. Receivers deduplicate by event ID.

NameTypeReqDescription
afterstringyes–
companystringyesSummer company ID
environmentstringyesEnvironment that owns the resource
idempotency_keystring–Reuse the same key when retrying the same change
limitinteger––
webhookstringyes–

No output schema declared.

No examples provided.

summer_webhooks_save ~147

Create, update, rotate or disable a signed webhook endpoint. A new signing secret goes to the trusted local helper only. Returns a local CLI command when a secret is involved.

NameTypeReqDescription
companystringyesSummer company ID
disableboolean––
environmentstringyesEnvironment that owns the resource
event_typesarrayyes–
expected_versionintegeryesCurrent version you expect; 0 when the resource does not exist yet
idempotency_keystring–Reuse the same key when retrying the same change
rotate_secretboolean––
urlstringyes–
webhookstringyes–

No output schema declared.

No examples provided.

summer_work_routing_read ~29

Read eligible teammates and automatic owner/reviewer routing settings.

NameTypeReqDescription
companystringyes–

No output schema declared.

No examples provided.

summer_work_routing_update ~97

Save automatic owner/reviewer routing with the expected version. Does not grant roles or approval authority.

NameTypeReqDescription
companystringyes–
idempotency_keystring–Reuse the same key when retrying the same change
issue_membersarrayyes–
issue_modestringyes–
review_membersarrayyes–
review_modestringyes–
versionintegeryes–

No output schema declared.

No examples provided.

summer_workflows_history ~43

Read the original revisions and authenticated edits for a saved workflow.

NameTypeReqDescription
companystringyes–
environmentstringyes–
workflowstringyes–

No output schema declared.

No examples provided.

summer_workflows_list ~46

Read built-in tasks and company/environment-owned workflow templates. Selecting one never runs work.

NameTypeReqDescription
companystringyes–
environmentstringyes–
retired–––

No output schema declared.

No examples provided.

summer_workflows_request_text ~68

Prepare editable operator guidance from an exact active workflow revision and feedback. Starts no investigation and executes no action.

NameTypeReqDescription
companystringyes–
environmentstringyes–
expected_revisionintegeryes–
feedbackstring––
idstringyes–

No output schema declared.

No examples provided.

summer_workflows_save ~115

Save, retire or restore a task template with its expected revision. Changes no case or effect authority.

NameTypeReqDescription
companystringyes–
descriptionstringyes–
environmentstringyes–
expected_revisionintegeryes–
idstringyes–
idempotency_keystring–Reuse the same key when retrying the same change
instructionsstringyes–
namestringyes–
reasonstringyes–
retiredbooleanyes–

No output schema declared.

No examples provided.

Install

How do I install the Summer MCP server?

Summer is a hosted endpoint at https://api.gosummer.ai/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 · api.gosummer.ai

# add to Claude Code
claude mcp add --transport http ai-gosummer-summer 'https://api.gosummer.ai/mcp'
Common questions

What is the Summer MCP server?

Summer is an MCP server listed in the public MCP registry as ai.gosummer/summer. Telehealth support for Claude, Codex and Cursor: investigate cases and connect your tools. This page covers its hosted endpoint (https://api.gosummer.ai/mcp).

Is the Summer MCP server safe to use?

Summer scores 80 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 Summer MCP server expose?

Summer exposes 161 tools: summer_github_issues_read, summer_github_connection_read, summer_github_connection_start, summer_github_repositories_list, summer_github_folders_list, and 156 more. Their descriptions and schemas cost roughly 13,767 tokens of context every time the server is loaded.

Does the Summer MCP server require authentication?

Yes. Summer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Summer MCP server still maintained?

Summer is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.