Parabol MCP by usefulapi
REMOTE · PARABOL.USEFULAPI.IO
Start Parabol retrospectives, standups and sprint poker; read teams/meetings/tasks; create tasks.
Available components
Last scanned (7 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
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.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- 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 not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 1 Nov 26 −49
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_reflections_and_comments_to_a_meeting” functional
- New prompt “create_or_update_a_task” functional
- New prompt “find_tasks_by_team_person_or_status” functional
- New prompt “review_past_meetings_of_a_team” functional
- New prompt “see_who_is_on_a_team_and_invite_people” functional
- New prompt “start_a_retrospective_standup_or_check_in” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 +1
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 0
- Server version: 1.27.0 → 1.28.0 functional
- Server version: 1.26.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 26 Oct 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 0.
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.3 → 1.23.0 functional
- Server version: 1.22.1 → 1.22.3 functional
- Server version: 1.22.0 → 1.22.1 functional
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 5 Nov 2026 · Probed https://parabol.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 parabol.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://parabol.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/parabol/ |
| http (plaintext) | http://parabol.usefulapi.io/mcp | Inconclusive | 302 | http://parabol.usefulapi.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 →
parabol_add_comment Add a comment ~196
MUTATES Parabol data: add a comment to a meeting discussion thread. Required: content (stringified TipTap/ProseMirror JSON document), discussionId, threadSortOrder (Int). Optionally isAnonymous or threadParentId (to reply). Parabol GraphQL: addComment(comment) → union. Requires COMMENTS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Comment body as a stringified TipTap/ProseMirror JSON document (required). |
| discussionId | string | yes | The discussion (meeting thread) id (required). |
| fields | object | – | Additional documented GraphQL input fields to send verbatim in this mutation's input (merged OVER the typed fields above). |
| isAnonymous | boolean | – | Post the comment anonymously. |
| threadParentId | string | – | Parent comment id, to post a threaded reply. |
| threadSortOrder | integer | – | Position within the thread (Int). Defaults to 0. |
No output schema declared.
No examples provided.
parabol_create_reflection Create a reflection ~190
MUTATES Parabol data: add a reflection card to a running retrospective's reflect phase. Required: meetingId, promptId (the reflect-prompt/column), sortOrder (Float). `content` (optional) is a stringified TipTap/ProseMirror JSON document (<=2000 chars). Parabol GraphQL: createReflection(input). Requires MEETINGS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Reflection text as a stringified TipTap/ProseMirror JSON document. |
| fields | object | – | Additional documented GraphQL input fields to send verbatim in this mutation's input (merged OVER the typed fields above). |
| meetingId | string | yes | The retrospective meeting id (required). |
| promptId | string | yes | The reflect-prompt (column) id (required). |
| sortOrder | number | – | Sort order within the column (Float). Defaults to 0. |
No output schema declared.
No examples provided.
parabol_create_task Create a task ~285
MUTATES Parabol data: create a task on a team. Required: teamId and status (active|stuck|done|future). Provide `plaintextContent` for the task text (and/or `content`, which is a stringified TipTap/ProseMirror JSON document). Optionally assign to a userId or link to a meetingId/discussionId. Parabol GraphQL: createTask(newTask, area). Requires TASKS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional AreaEnum context for the task (e.g. 'teamDash', 'meeting'). |
| content | string | – | Rich-text content as a stringified TipTap/ProseMirror JSON document. |
| discussionId | string | – | Link the task to this discussion id (meeting thread). |
| fields | object | – | Additional documented GraphQL input fields to send verbatim in this mutation's input (merged OVER the typed fields above). |
| meetingId | string | – | Link the task to this meeting id. |
| plaintextContent | string | – | Plain-text task content. |
| sortOrder | number | – | Sort order (Float). |
| status | string | – | Task status (TaskStatusEnum). Defaults to 'active'. |
| teamId | string | yes | The team id to create the task on (required). |
| userId | string | – | Assign the task to this user id. |
No output schema declared.
No examples provided.
parabol_get_meeting Get a meeting ~80
Fetch one meeting by id with its phases and stages. For a retrospective it also returns the reflection groups and reflections plus vote/topic/task/comment counts. Uses __typename so you can tell meeting types apart. Parabol GraphQL: viewer.meeting(meetingId). Requires MEETINGS_READ.
| Name | Type | Req | Description |
|---|---|---|---|
| meetingId | string | yes | The meeting id. |
No output schema declared.
No examples provided.
parabol_get_organization Get an organization ~53
Fetch one organization by id, including its teams. Parabol GraphQL: viewer.organization(orgId). Requires ORGS_READ (+ TEAMS_READ for teams).
| Name | Type | Req | Description |
|---|---|---|---|
| orgId | string | yes | The organization id. |
No output schema declared.
No examples provided.
parabol_get_team Get a team ~75
Fetch one team by id: metadata, its team members (with each member's user), active meetings, and organization. Parabol GraphQL: viewer.team(teamId). Requires TEAMS_READ (+ MEETINGS_READ for activeMeetings, ORGS_READ for organization).
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | yes | The team id. |
No output schema declared.
No examples provided.
parabol_get_viewer Get current user (viewer) ~71
Fetch the authenticated Parabol user (the token owner): id, preferredName, email, tier, and the team ids (tms) they belong to. Parabol GraphQL: query { viewer { ... } }. Requires the USERS_READ scope. Start here to discover your identity and team ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
parabol_graphql Run a GraphQL operation (query or mutation) ~100
MUTATES Parabol data (potentially): escape hatch to run an arbitrary Parabol GraphQL operation — including any mutation — against action.parabol.co/graphql with optional variables. Use for operations not covered by the curated tools. Your token must carry the scope the operation requires. Prefer parabol_query for read-only calls.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A GraphQL query or mutation document. |
| variables | object | – | Variables object for the operation. |
No output schema declared.
No examples provided.
parabol_invite_to_team Invite users to a team ~112
MUTATES Parabol data: send team invitations by email. Required: teamId and invitees (an array of email addresses). Optionally scope to a meetingId. Parabol GraphQL: inviteToTeam(teamId, invitees). Requires TEAMS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| invitees | array | yes | Email addresses to invite (required). |
| meetingId | string | – | Optionally associate the invitation with a meeting id. |
| teamId | string | yes | The team id to invite into (required). |
No output schema declared.
No examples provided.
parabol_list_active_meetings List active meetings ~59
List a team's currently-active (in-progress) meetings. Parabol GraphQL: viewer.team(teamId).activeMeetings. Requires TEAMS_READ + MEETINGS_READ.
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | yes | The team id. |
No output schema declared.
No examples provided.
parabol_list_meetings List meetings (history) ~179
List past/ongoing meetings for one or more teams (Relay connection), newest first. `teamIds` is required. `meetingTypes` defaults to all four (retrospective, action, poker, teamPrompt). `before` bounds the window (defaults to now); paginate older with `after`. Parabol GraphQL: viewer.meetings. Requires MEETINGS_READ.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | DateTime cursor — return meetings before this ISO timestamp (older page). |
| before | string | – | DateTime upper bound (ISO). Defaults to now. |
| first | integer | – | Max meetings to return (default 20). |
| meetingTypes | array | – | Meeting types to include (MeetingTypeEnum). Defaults to all four. |
| teamIds | array | yes | Team ids to fetch meetings for (required). |
No output schema declared.
No examples provided.
parabol_list_organization_users List organization users ~133
List the users in an organization (Relay connection): each org-user's role, joinedAt, tier, and underlying user (preferredName, email). Paginate with `first` + `after` (pass the last edge's `cursor`). Parabol GraphQL: viewer.organization(orgId).organizationUsers. Requires ORGS_READ + USERS_READ.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Cursor for the next page (the `cursor` of the last edge from a prior call). |
| first | integer | – | Max org-users to return (page size). |
| orgId | string | yes | The organization id. |
No output schema declared.
No examples provided.
parabol_list_organizations List organizations ~42
List the organizations the viewer belongs to: id, name, tier, billingTier. Parabol GraphQL: viewer.organizations. Requires ORGS_READ.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
parabol_list_tasks List tasks ~198
List the viewer's tasks (Relay connection), optionally filtered by team, user, status, archived state, or a text query. Paginate with `first` + the `after` DateTime cursor. Parabol GraphQL: viewer.tasks. Requires TASKS_READ.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | DateTime cursor for the next (older) page (the last edge's cursor). |
| archived | boolean | – | Include archived tasks (default false). |
| filterQuery | string | – | Free-text filter on task content. |
| first | integer | – | Max tasks to return (default 20). |
| includeUnassigned | boolean | – | Include unassigned tasks (default false). |
| statusFilters | array | – | Filter by task status (TaskStatusEnum: active, stuck, done, future). |
| teamIds | array | – | Filter to these team ids. |
| userIds | array | – | Filter to tasks assigned to these user ids. |
No output schema declared.
No examples provided.
parabol_list_team_members List team members ~90
List the members of a team, each with role flags (isLead, isOrgAdmin) and the underlying user (preferredName, email). Parabol GraphQL: viewer.team(teamId).teamMembers. Requires TEAMS_READ.
| Name | Type | Req | Description |
|---|---|---|---|
| sortBy | string | – | Optional field to sort members by (e.g. 'preferredName'). |
| teamId | string | yes | The team id. |
No output schema declared.
No examples provided.
parabol_list_teams List teams ~65
List the teams the viewer belongs to, with each team's id, name, orgId, tier, and team lead. Parabol GraphQL: viewer.teams. Requires the TEAMS_READ scope.
| Name | Type | Req | Description |
|---|---|---|---|
| includeArchived | boolean | – | Include archived teams (default false). |
No output schema declared.
No examples provided.
parabol_query Run a GraphQL query (read-only) ~109
Escape hatch: run an arbitrary Parabol GraphQL QUERY (read-only) against action.parabol.co/graphql with optional variables. Mutations are REJECTED — use the dedicated write tools or parabol_graphql for those. Useful for fields not covered by the curated read tools. Requires the matching read scope(s) on your token.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A GraphQL query document (must be a query, not a mutation). |
| variables | object | – | Variables object for the query. |
No output schema declared.
No examples provided.
parabol_start_checkin Start a check-in meeting ~86
MUTATES Parabol data: start a new Check-in (Action) meeting for a team (returns the new meetingId). Required: teamId. Optionally name it. Parabol GraphQL: startCheckIn → union. Requires MEETINGS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional meeting name. |
| teamId | string | yes | The team id (required). |
No output schema declared.
No examples provided.
parabol_start_retrospective Start a retrospective ~89
MUTATES Parabol data: start a new retrospective meeting for a team (returns the new meetingId). Required: teamId. Optionally name it. Parabol GraphQL: startRetrospective → union. Requires MEETINGS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional meeting name. |
| teamId | string | yes | The team id to run the retro for (required). |
No output schema declared.
No examples provided.
parabol_start_team_prompt Start a standup (team prompt) ~92
MUTATES Parabol data: start a new async Standup (Team Prompt) meeting for a team. Required: teamId. Optionally name it (default 'Standup'). Parabol GraphQL: startTeamPrompt → union. Requires MEETINGS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Optional meeting name (default 'Standup'). |
| teamId | string | yes | The team id (required). |
No output schema declared.
No examples provided.
parabol_update_task Update a task ~187
MUTATES Parabol data: update an existing task. Required: id. Optionally change content (stringified TipTap JSON), status, assignee (userId), or sortOrder. Only included fields change. Parabol GraphQL: updateTask(updatedTask, area). Requires TASKS_WRITE.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional AreaEnum context. |
| content | string | – | New rich-text content as a stringified TipTap/ProseMirror JSON document. |
| fields | object | – | Additional documented GraphQL input fields to send verbatim in this mutation's input (merged OVER the typed fields above). |
| id | string | yes | The task id (required). |
| sortOrder | number | – | New sort order (Float). |
| status | string | – | New status (TaskStatusEnum). |
| userId | string | – | Reassign the task to this user id. |
No output schema declared.
No examples provided.
How do I install the Parabol MCP by usefulapi server?
Parabol MCP by usefulapi is a hosted endpoint at https://parabol.usefulapi.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 · parabol.usefulapi.io
claude mcp add --transport http io-usefulapi-parabol 'https://parabol.usefulapi.io/mcp'
What is the Parabol MCP by usefulapi server?
Parabol MCP by usefulapi is listed in the public MCP registry as io.usefulapi/parabol. Start Parabol retrospectives, standups and sprint poker; read teams/meetings/tasks; create tasks. This page covers its hosted endpoint (https://parabol.usefulapi.io/mcp).
Is the Parabol MCP by usefulapi server safe to use?
Parabol MCP by usefulapi scores 18 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 Parabol MCP by usefulapi server expose?
Parabol MCP by usefulapi exposes 21 tools: parabol_get_viewer, parabol_list_teams, parabol_get_team, parabol_list_team_members, parabol_list_organizations, and 16 more. Their descriptions and schemas cost roughly 2,491 tokens of context every time the server is loaded.
Does the Parabol MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Parabol MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Parabol MCP by usefulapi server still maintained?
Parabol MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 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 Parabol MCP by usefulapi server?
VerifyMCP ran 4 checks on Parabol MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Parabol MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 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.