io.usefulapi/parabol
REMOTE · PARABOL.USEFULAPI.IO · SCANNED SEP 20
Start Parabol retrospectives, standups and sprint poker; read teams/meetings/tasks; create tasks.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2452 tokens (~116/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/parabol MCP server?
io.usefulapi/parabol 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'
{
"mcpServers": {
"io-usefulapi-parabol": {
"url": "https://parabol.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-parabol": {
"type": "http",
"url": "https://parabol.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-parabol] url = "https://parabol.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-parabol": {
"type": "remote",
"url": "https://parabol.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-parabol --url 'https://parabol.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-parabol:
url: "https://parabol.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-parabol": {
"Transport": "http",
"Url": "https://parabol.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-parabol -t streamable-http -u 'https://parabol.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-parabol": {
"type": "http",
"url": "https://parabol.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +67
- Transport: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.93 ▲ functional
- 7 Sept 26 −10
- Transport: pass → unverified ▼ security
- 5 Sept 26 +10
- Transport: unverified → pass ▲ security
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 20 Sept 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 | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 509be3f5e6a7fd2f13fea93b0d02bed8 |
| SANs: usefulapi.io, parabol.usefulapi.io, *.parabol.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. | present | 57355 | 8 | Verified |
| usefulapi.io. | 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="OAuth", resource_metadata="https://parabol.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://parabol.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://parabol.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://parabol.usefulapi.io/mcp |
| Authorisation server | https://parabol.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://parabol.usefulapi.io/mcp | Inconclusive | 401 |
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 Add a comment ~194
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.
create_reflection Create a reflection ~188
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.
create_task Create a task ~283
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.
get_meeting Get a meeting ~78
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.
get_organization Get an organization ~51
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.
get_team Get a team ~73
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.
get_viewer Get current user (viewer) ~69
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.
invite_to_team Invite users to a team ~109
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.
list_active_meetings List active meetings ~57
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.
list_meetings List meetings (history) ~177
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.
list_organization_users List organization users ~131
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.
list_organizations List organizations ~40
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.
list_tasks List tasks ~196
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.
list_team_members List team members ~88
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.
list_teams List teams ~63
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_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_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.
start_checkin Start a check-in meeting ~84
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.
start_retrospective Start a retrospective ~87
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.
start_team_prompt Start a standup (team prompt) ~90
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.
update_task Update a task ~185
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.
What is the io.usefulapi/parabol MCP server?
io.usefulapi/parabol is an MCP server 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 io.usefulapi/parabol MCP server safe to use?
io.usefulapi/parabol scores 86 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 io.usefulapi/parabol MCP server expose?
io.usefulapi/parabol exposes 21 tools: get_viewer, list_teams, get_team, list_team_members, list_organizations, and 16 more. Their descriptions and schemas cost roughly 2,452 tokens of context every time the server is loaded.
Does the io.usefulapi/parabol MCP server require authentication?
Yes. io.usefulapi/parabol 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 io.usefulapi/parabol MCP server still maintained?
io.usefulapi/parabol is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.