Comma
REMOTE · COMMAREPORTS.COM
Publish HTML reports to a share link, collect anchored comments, revise at the same URL.
Available components
Last scanned (20 hours ago)
Scores higher than 13% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (4)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- 4 Oct 26 0
First indexed and scored.
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 21 Nov 2026 · Probed https://commareports.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=commareports.com | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 4c8321ed12945b11134af108bea6fea8 |
| SANs: commareports.com, www.commareports.com, *.www.commareports.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of commareports.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| commareports.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="comma"
Bearer realm="comma" | Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=() |
| www-authenticate | Bearer realm="comma" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://commareports.com/api/mcp | Auth required | 401 | |
| http (plaintext) | http://commareports.com/api/mcp | Inconclusive | 403 |
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 →
add_comment ~115
Create a top-level comment on a report. Optionally anchor it to a text excerpt or block id.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor_prefix | string | – | Text before anchor_text (for disambiguation). |
| anchor_suffix | string | – | Text after anchor_text (for disambiguation). |
| anchor_text | string | – | Quoted text the comment is anchored to. |
| block_id | string | – | Stable block identifier in the rendered HTML. |
| body | string | yes | Comment text. |
| report_id | string | yes | Report id (UUID). |
No output schema declared.
No examples provided.
connect_integration ~105
Connect a GitHub PAT or Linear API key so Comma can post report links onto PRs/issues. The token is verified against the provider, then stored encrypted; the token itself is never returned. Re-connecting the same provider rotates the stored token.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The GitHub PAT or Linear API key. |
| account_label | string | – | Optional label. Derived from the provider account if omitted. |
| provider | string | yes | Which provider to connect. |
No output schema declared.
No examples provided.
create_connector ~141
Create a connector: an encrypted credential a skill can use. `kind` must be one of the catalog kinds from list_connectors; `config` and `secret` are validated against that kind's schema. The secret is encrypted at rest and never returned. (kind, label) must be unique per account.
| Name | Type | Req | Description |
|---|---|---|---|
| config | object | – | Non-secret config keyed by the kind's configSchema. |
| kind | string | yes | Connector kind (see list_connectors definitions). |
| label | string | yes | A name for this credential, unique within the kind. |
| secret | object | yes | Secret values keyed by the kind's secretSchema. Encrypted at rest. |
No output schema declared.
No examples provided.
create_notification ~178
Subscribe a webhook to report events. Omit report_id to subscribe to every report you own, were invited to, or share with your team (public link access doesn't count). `events` defaults to all three; `format` is 'slack' (default), 'discord', or 'plain'.
| Name | Type | Req | Description |
|---|---|---|---|
| events | array | – | Which events to deliver. Defaults to all three. |
| format | string | – | Payload format. Defaults to 'slack'. |
| name | string | – | Defaults to 'Untitled notification'. |
| report_id | string | – | Scope to one report, or omit for every report you own, were invited to, or share with your team. |
| signing_secret | string | – | Optional secret used to sign deliveries. Stored encrypted. |
| webhook_url | string | yes | http(s) URL Comma POSTs events to. |
No output schema declared.
No examples provided.
create_report ~643
Upload a new HTML report to Comma and get back an absolute share_url to give the user. By default anyone with the link can open the report (visibility='public'; share links are not indexed by search engines) and comment on it after a free sign-in (public_permission='comment'). Pass visibility='private' to keep it owner-only, or public_permission='view' for a read-only link. To include images or other files the HTML references by relative path (e.g. `<img src="images/chart.png">`), pass them in `assets` — they're uploaded and the HTML's relative refs are rewritten to public URLs automatically, all in this one call. Returns the report id, visibility, public_permission, and absolute edit_url (/r/:id) and share_url (/p/:id). Pass producer_name (e.g. 'Claude Code', 'Cursor') so the public share view can attribute the report to the agent that produced it. Only pass source_recipe.prompt when the user asks; it is shown to every viewer.
| Name | Type | Req | Description |
|---|---|---|---|
| assets | array | – | Optional inline assets (images, fonts, CSS, JS, …) the HTML references by *relative* path. Each is uploaded and the report's matching relative refs (src/href/srcset/url(...)) are rewritten to the sto… |
| description | string | – | Optional one-line description. |
| html | string | yes | Full HTML for the report (≤ 5 MB). |
| producer_icon_url | string | – | Optional http(s) URL to a small square icon for the producer. |
| producer_name | string | – | Display name of the agent that produced this report (e.g. 'Claude Code', 'Cursor', 'ChatGPT'). Surfaced as a watermark chip on /p/:id. |
| producer_url | string | – | Optional http(s) URL the watermark chip links to (e.g. https://claude.ai/code). |
| public_permission | string | – | What link/anonymous visitors may do. Defaults to 'comment' (commenting needs a free sign-in). 'edit' needs a token with the 'sharing' scope. Ignored (forced to 'none') when visibility='private'. |
| source_recipe | object | – | Structured payload (prompt + tools, etc.) the public viewer can use to re-run the same recipe on their own data. Convention: { prompt: string, tools?: string[] }. Shown to every viewer of the share l… |
| title | string | – | Optional title. Defaults to 'Untitled report'. |
| visibility | string | – | Who can reach the share link. Defaults to 'public' (anyone with the link). 'registered' = any signed-in user; 'private' = owner only. For 'team' or 'domain' (company email, with allowed_email_domains… |
No output schema declared.
No examples provided.
create_report_from_url ~241
Import a public web page into Comma as a report. Fetches the URL and inlines its images, styles and fonts into a single self-contained HTML document — JavaScript-rendered pages (SPAs, app-builder pages like base44, dashboards) are rendered in a headless browser first so their real content is captured. Creates a shareable report and returns its id, edit URL (/r/:id) and share URL (/p/:id). Use for requests like 'import this page/site/dashboard/app into Comma' or 'turn this URL into a Comma doc'. The page must be publicly reachable (no login); pages behind bot-protection (e.g. Cloudflare challenges) can't be captured.
| Name | Type | Req | Description |
|---|---|---|---|
| public_permission | string | – | What link visitors may do. Defaults to 'comment'. 'edit' needs a token with the 'sharing' scope. |
| title | string | – | Optional title. Defaults to the page's <title> (or hostname). |
| url | string | yes | Public http(s) URL of the page to import. |
| visibility | string | – | Who can reach the share link. Defaults to 'public'. |
No output schema declared.
No examples provided.
create_reviewer ~196
Register an agent-reviewer. Comma POSTs the report's content to `reviewer_url`; the reviewer replies with comments. Set report_id to scope it to one report, or omit it for an org-wide reviewer across all your reports. With auto_on_revision=true (default) it runs automatically whenever a new revision is pushed.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_on_revision | boolean | – | Run automatically on each new revision. Defaults to true. |
| enabled | boolean | – | Defaults to true. |
| name | string | – | Display name. Defaults to 'Untitled reviewer'. |
| prompt | string | – | Optional instructions passed to the reviewer. |
| report_id | string | – | Scope to one report (you must own it), or omit for org-wide. |
| reviewer_auth_header | string | – | Optional Authorization header value Comma sends to reviewer_url. Stored encrypted. |
| reviewer_url | string | yes | http(s) webhook Comma calls to review. |
No output schema declared.
No examples provided.
create_routine ~272
Create a routine that re-runs on a cron schedule against a report you can edit. Provide either `trigger_url` (Comma POSTs to your webhook each tick) or `skill_id` (Comma runs one of your skills). `schedule_cron` is a standard 5-field cron expression; routines run at any cadence on every plan, with no per-plan routine cap. Hosted runs draw down your prepaid credit balance (or run free on your own AWS Bedrock key).
| Name | Type | Req | Description |
|---|---|---|---|
| connector_ids | array | – | Optional connector UUIDs the skill may use. Must be owned by you. |
| enabled | boolean | – | Defaults to true. |
| name | string | – | Defaults to 'Untitled routine'. |
| payload | object | – | Optional JSON forwarded to trigger_url (≤ 8 KiB). |
| report_id | string | yes | UUID of the report this routine maintains. |
| schedule_cron | string | yes | 5-field cron expression, e.g. '0 9 * * 1'. |
| skill_id | string | – | UUID of a skill to run each tick (or use trigger_url). |
| trigger_auth_header | string | – | Optional Authorization header sent to trigger_url. Stored encrypted. |
| trigger_url | string | – | Webhook Comma POSTs each tick (or use skill_id). |
No output schema declared.
No examples provided.
create_skill ~258
Create a skill, either by authoring a new one (pass `name` + `prompt`) or by uploading a SKILL.md you already have (pass its full text as `skill_md` — its YAML frontmatter is parsed for name/description/prompt/required tools/model). The skill can then be attached to a routine (via create_routine's skill_id) so Comma runs it on a schedule. For .zip-bundle or GitHub-sourced skills, use the REST endpoint POST /api/v1/skills.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional one-line description. |
| model | string | – | Optional model override for the skill run. |
| name | string | – | Skill name. Required unless skill_md is provided. |
| prompt | string | – | The instructions/recipe the skill runs (≤ 100k chars). Required unless skill_md is provided. |
| required_tools | array | – | Optional list of tools the skill needs, e.g. [{ kind: 'connector' }]. |
| skill_md | string | – | Full text of an existing SKILL.md (with YAML frontmatter). Use this to upload a skill you already have. `name`/`description`/etc. below override the parsed values. |
No output schema declared.
No examples provided.
create_website ~134
Create a new website. Either a deploy target (then call deploy_website to push source), or pass external_url to link an EXISTING live site (embed + page-level comments, no deploy). framework is react|nextjs|vite|static (defaults to react).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| external_url | string | – | Link an existing live site by URL instead of deploying. Embeds it for page-level comments; no build. |
| framework | string | – | Build framework (for deploy targets). Defaults to 'react'. |
| name | string | – | Display name. Defaults to 'Untitled site'. |
No output schema declared.
No examples provided.
delete_connector ~35
Delete a connector you own. Routines referencing it keep their other connectors.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_id | string | yes | UUID of the connector. |
No output schema declared.
No examples provided.
delete_notification ~27
Remove a notification subscription by id.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | string | yes | UUID from list_notifications. |
No output schema declared.
No examples provided.
delete_report_asset ~85
Delete a previously-uploaded asset by its id. Removes both the storage object and the database row. The report's HTML is not modified — any `<img src>` etc. referencing the deleted asset will 404.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | UUID of the asset (from list_report_assets). |
| report_id | string | yes | UUID of the report the asset belongs to. |
No output schema declared.
No examples provided.
delete_reviewer ~41
Delete an agent-reviewer you own. Comments it already produced stay; their reviewer_id becomes null.
| Name | Type | Req | Description |
|---|---|---|---|
| reviewer_id | string | yes | UUID of the reviewer. |
No output schema declared.
No examples provided.
delete_routine ~31
Delete a routine you own and its run history.
| Name | Type | Req | Description |
|---|---|---|---|
| routine_id | string | yes | UUID of the routine. |
No output schema declared.
No examples provided.
delete_skill ~40
Delete a skill you own. Routines that reference it keep working but their skill_id becomes null.
| Name | Type | Req | Description |
|---|---|---|---|
| skill_id | string | yes | UUID of the skill. |
No output schema declared.
No examples provided.
deploy_website ~104
Deploy source files to a website. Provide the full source bundle as files:[{path, content}] (UTF-8 text; max 2000 files / 25 MB). The provider builds + hosts it; poll read_website for the live URL. Sites are taken down after their TTL — redeploy to bring one back.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Source files relative to the project root. |
| website_id | string | yes | UUID of the website to deploy. |
No output schema declared.
No examples provided.
disconnect_integration ~29
Remove a connected integration by id.
| Name | Type | Req | Description |
|---|---|---|---|
| integration_id | string | yes | UUID from list_integrations. |
No output schema declared.
No examples provided.
get_report ~36
Fetch a report by id. Returns metadata + the stored HTML. Requires view permission.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Report id (UUID). |
No output schema declared.
No examples provided.
get_report_signoffs ~89
List review verdicts (approved / changes_requested) on a report. Each entry carries the reviewer, optional note, and is_stale — true when the report's content has changed since the verdict was given. Check this before promoting or distributing a report: an approval with is_stale=true does not vouch for the current content.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | Report id (UUID). |
No output schema declared.
No examples provided.
list_comments ~108
List comments + replies on a report. Cursor-paginated; pass the returned nextCursor to fetch the next page. Each comment embeds up to 50 replies; replies_truncated=true means the thread has more (REST: GET /api/v1/comments/:id/replies).
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque nextCursor from a previous call. |
| limit | integer | – | Defaults to 50. Capped at 200. |
| report_id | string | yes | Report id (UUID). |
No output schema declared.
No examples provided.
list_connectors ~54
List your connectors (encrypted credentials for tools like PostHog, Databricks, Supabase, Slack, Stripe, Google Drive) plus the catalog of connector kinds and their config/secret schemas. Secrets are never returned.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_integrations ~33
List your connected GitHub / Linear integrations. Access tokens are never returned — only provider, account label, and status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_notifications ~48
List your notification subscriptions. Each one POSTs report events (revision.created, comment.created, comment.mentioned, signoff.submitted) to a webhook formatted for Slack, Discord, or plain JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_report_assets ~51
List all assets attached to a report, with their public URLs. Useful for discovering what's already uploaded before deciding whether to add more or reference existing files.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | UUID of the report. |
No output schema declared.
No examples provided.
list_reports ~86
List reports the authenticated user owns, most-recently-updated first. Returns id, title, description, timestamps, and share/edit URLs — not the HTML. Use get_report to fetch a report's body.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pass the nextCursor returned by a previous call to paginate. |
| limit | integer | – | Defaults to 25. Capped at 100. |
No output schema declared.
No examples provided.
list_reviewers ~55
List the agent-reviewers you own. A reviewer is a webhook (reviewer_url) Comma calls with a report's content; the reviewer posts back comments. Reviewers with report_id=null apply to every report you own.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_routines ~53
List the routines you own. A routine re-runs on a cron schedule, either by calling a webhook (trigger_url) or by running a skill inside Comma (skill_id), and can republish a report.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_skills ~45
List the skills you own. A skill is a reusable prompt/recipe a routine can run inside Comma. Returns the prompt, required tools, source, and model for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_website_comments ~128
List comments left on a website, with the full hidden enrichment a coding agent needs to fix each issue: page_path (the route), target_selector (the element), deployment_id (the build), and a metadata blob (element purpose, a DOM slice, viewport, recent console messages). Defaults to open comments; pass status:'all' to include resolved.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from a previous call. |
| limit | integer | – | Defaults to 50. |
| status | string | – | Defaults to 'open'. |
| website_id | string | yes | UUID of the website. |
No output schema declared.
No examples provided.
list_websites ~79
List the authenticated user's websites, most-recently-updated first. Returns id, name, framework, visibility, and the app URL (/websites/:id) — use read_website for the live URL and production deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | nextCursor from a previous call. |
| limit | integer | – | Defaults to 25. |
No output schema declared.
No examples provided.
read_report ~71
Fetch a report by id, optionally as plain text. Returns id, title, description, URL, html and text. Use to read another agent's prior report as context.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Which content shape to emphasize. Both are always returned. |
| id | string | yes | Report id (UUID). |
No output schema declared.
No examples provided.
read_website ~40
Fetch a website by id: metadata plus its production deployment and live URL. Requires view permission.
| Name | Type | Req | Description |
|---|---|---|---|
| website_id | string | yes | UUID of the website. |
No output schema declared.
No examples provided.
reply_to_comment ~38
Reply to an existing comment thread.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Reply text. |
| comment_id | string | yes | Parent comment id (UUID). |
No output schema declared.
No examples provided.
request_review ~102
Run every enabled agent-reviewer for a report against its current head revision. Returns the per-reviewer outcome (ok, comments_created, error?). Use when you've shipped a new revision and want a second agent to leave anchored critique before a human looks at it.
| Name | Type | Req | Description |
|---|---|---|---|
| report_id | string | yes | Report id (UUID). |
| reviewer_id | string | – | Optional: run a single reviewer by id. When omitted, runs every enabled reviewer the actor owns for this report. |
No output schema declared.
No examples provided.
run_routine ~73
Execute a routine immediately, without waiting for its next scheduled tick. Returns the run outcome plus the refreshed routine row (last_run_status, next_run_at, …). Skill-driven routines may run asynchronously (deferred); poll list_routines for the final status.
| Name | Type | Req | Description |
|---|---|---|---|
| routine_id | string | yes | UUID of the routine. |
No output schema declared.
No examples provided.
search_reports ~119
Trigram text search over reports the caller owns, was invited to, or shares with their team (not other people's public share links). Returns id, title, snippet, share URL and similarity. Use before drafting a new report to find prior work.
| Name | Type | Req | Description |
|---|---|---|---|
| include_html | boolean | – | If true, include rendered_html for up to the top 3 results (bounded to keep responses small). |
| limit | integer | – | Max results. Defaults to 5, capped at 20. |
| query | string | yes | Free-text query (1+ chars). |
No output schema declared.
No examples provided.
set_comment_status ~35
Resolve or reopen a comment thread.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | Comment id (UUID). |
| status | string | yes | – |
No output schema declared.
No examples provided.
set_report_sharing ~501
Publish or unpublish a report and control who can reach its share link (/p/:id). `visibility`: 'public' (anyone with the link), 'registered' (any signed-in user), 'domain' (anyone signed in with a verified email on one of `allowed_email_domains` — required with 'domain', e.g. ['acme.com']), 'team' (the report's team; the report must already be filed under one), or 'private' (owner + invited people only). To change the domain list, send visibility='domain' again with the full new list. `public_permission` is what link/anonymous visitors may do: 'none', 'view', 'comment', or 'edit'. To publish a report so anyone can open and comment on it, set visibility='public' and public_permission='comment'. `show_approved_only` enables staged publishing: view-only audiences see the last revision a reviewer approved (see set_report_signoff) while reviewers keep seeing head. `allowed_embed_origins` opts the report into embedding on other sites: pass the bare origins allowed to iframe it (e.g. ['https://acme.com']), or [] / null to turn embedding off. The response then carries `embed_snippet`, the exact markup to paste into the host page; the embed only renders while the report is public, its link permission isn't 'none', and it has no share password. Requires manage permission on the report (owner or admin).
| Name | Type | Req | Description |
|---|---|---|---|
| allowed_email_domains | array | – | Email domains allowed to view when visibility='domain' (e.g. ['acme.com']). Required with, and only accepted with, visibility='domain'; replaces the existing list. |
| allowed_embed_origins | array|null | – | Origins allowed to iframe this report via /embed/:id. Bare origins only — scheme + host + optional port, no path (https://acme.com, https://blog.acme.com:8443). https is required except for http://lo… |
| public_permission | string | – | What link/anonymous visitors may do. |
| report_id | string | yes | UUID of the report. |
| show_approved_only | boolean | – | Staged publishing: when true, view-only audiences see the last approved revision instead of head. |
| visibility | string | – | Who can reach the report. |
No output schema declared.
No examples provided.
set_report_signoff ~103
Submit or replace your review verdict on a report: 'approved' or 'changes_requested', with an optional one-line note. One current verdict per reviewer per report (PR-review semantics); it is pinned to a revision snapshotting the report's content at submission and goes stale when that content changes.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | Optional short note that travels with the verdict. |
| report_id | string | yes | Report id (UUID). |
| verdict | string | yes | – |
No output schema declared.
No examples provided.
set_website_comment_status ~49
Resolve or reopen a website comment. Use this to close out issues as you ship fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | UUID of the website comment. |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_report ~183
Edit a report's title, description, HTML, and/or producer attribution in place. At least one mutable field must be provided.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | – | Pass null to clear the description. |
| html | string | – | Replacement HTML (≤ 5 MB). |
| id | string | yes | Report id (UUID). |
| producer_icon_url | string|null | – | http(s) URL to a small producer icon. Pass null to clear. |
| producer_name | string|null | – | Display name of the producing agent. Pass null to clear. |
| producer_url | string|null | – | http(s) URL the watermark chip links to. Pass null to clear. |
| source_recipe | object|null | – | Structured recipe payload ({ prompt, tools?, ... }) consumed by the public viewer's 'Continue this run' modal. Pass null to clear. |
| title | string | – | – |
No output schema declared.
No examples provided.
update_reviewer ~105
Update an agent-reviewer you own. Pass any subset of name, reviewer_url, reviewer_auth_header (null clears), prompt (null clears), enabled, auto_on_revision.
| Name | Type | Req | Description |
|---|---|---|---|
| auto_on_revision | boolean | – | – |
| enabled | boolean | – | – |
| name | string | – | – |
| prompt | string|null | – | – |
| reviewer_auth_header | string|null | – | – |
| reviewer_id | string | yes | UUID of the reviewer. |
| reviewer_url | string | – | – |
No output schema declared.
No examples provided.
update_routine ~151
Update a routine you own. Pass any subset of name, schedule_cron, trigger_url (null clears), trigger_auth_header (null clears), skill_id (null clears), connector_ids, payload, enabled. Changing schedule_cron recomputes the next run time and is re-checked against your plan floor.
| Name | Type | Req | Description |
|---|---|---|---|
| connector_ids | array | – | – |
| enabled | boolean | – | – |
| name | string | – | – |
| payload | object|null | – | – |
| routine_id | string | yes | UUID of the routine. |
| schedule_cron | string | – | – |
| skill_id | string|null | – | – |
| trigger_auth_header | string|null | – | – |
| trigger_url | string|null | – | – |
No output schema declared.
No examples provided.
upload_report_asset ~264
Attach a binary asset (image, video, font, CSS, JS, etc.) to a report. The returned `url` is a stable public link suitable for `<img src>`, `<video src>`, CSS `url(...)`, or any other reference inside the report's HTML. Pass `content_base64` as raw base64 (or a `data:<mime>;base64,...` URL — both work). Re-uploading the same `relative_path` replaces the previous asset.
| Name | Type | Req | Description |
|---|---|---|---|
| content_base64 | string | yes | Asset bytes as base64. A `data:<mime>;base64,...` data URL is also accepted — the prefix is stripped automatically. Max 25 MB decoded. |
| content_type | string | – | Optional MIME type (e.g. 'image/png', 'video/mp4'). Defaults to 'application/octet-stream' if omitted. |
| relative_path | string | yes | Path the asset will be addressable by, relative to the report (e.g. 'images/hero.png', 'fonts/inter.woff2'). No leading slash, no '.'/'..' segments, no '%', '?' or '#'. Max 512 chars. |
| report_id | string | yes | UUID of the target report. You must have edit permission on it. |
No output schema declared.
No examples provided.
How do I install the Comma MCP server?
Comma is a hosted endpoint at https://commareports.com/api/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 · commareports.com
claude mcp add --transport http com-commareports-comma 'https://commareports.com/api/mcp'
What is the Comma MCP server?
Comma is an MCP server listed in the public MCP registry as com.commareports/comma. Publish HTML reports to a share link, collect anchored comments, revise at the same URL. This page covers its hosted endpoint (https://commareports.com/api/mcp).
Is the Comma MCP server safe to use?
Comma scores 31 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 Comma MCP server expose?
Comma exposes 45 tools: create_report, create_report_from_url, list_reports, get_report, update_report, and 40 more. Their descriptions and schemas cost roughly 5,374 tokens of context every time the server is loaded.
Does the Comma MCP server require authentication?
Yes. Comma 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 Comma MCP server still maintained?
Comma is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Comma MCP server?
VerifyMCP ran 4 checks on Comma, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about Comma: HTTPS, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.