io.usefulapi/parabol

REMOTE · PARABOL.USEFULAPI.IO · SCANNED AUG 3

Start Parabol retrospectives, standups and sprint poker; read teams/meetings/tasks; create tasks.

Available components

+6 this week 73 73 Trust /100

Trust breakdown (6 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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability76

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 Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · parabol.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-parabol https://parabol.usefulapi.io/mcp

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-parabol]
url = "https://parabol.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-parabol": {
      "type": "remote",
      "url": "https://parabol.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-parabol --url https://parabol.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-parabol:
    url: "https://parabol.usefulapi.io/mcp"

// mcp.json

{
  "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.

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
2 Aug 26 +54
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
1 Aug 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
28 Jul 26 +3
- Authorization: fail → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +55
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 4 earlier entries Hide earlier entries

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 3 Aug 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	18 Jul 2026	16 Oct 2026	ECDSA 256	ECDSA-SHA256	d659a5745d5bc8c30e0586f8d41fd44f
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

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

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

MCP tools — 21 exposed · ~2,452 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.

Tool Tokens

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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).

Input Output Examples

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).

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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 Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	67
28 Jul	70
29 Jul	70
30 Jul	69
31 Jul	71
1 Aug	18
2 Aug	72
3 Aug	73