MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Data access / search

Ziflow MCP by usefulapi

Search and read proofs, comments and activity, and add or resolve comments in Ziflow.

Checks passed
14 / 22

0 failed · 8 not measured

Median response
55 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
17

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Outdated check

Last connection measurement is over 24 hours old. Current availability is unknown.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 55 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name ziflow-mcp.

  • Pass
    Lists tools

    tools/list returned 17 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 55 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 55 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    44 of 45 parameters have a description (98%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-10T23:34:50.286437Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Ziflow MCP by usefulapi

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 17

ziflow_add_comment

Add a comment to a proof at a page (or a time range for audio/video). The comment is visible to every reviewer on the proof. Not idempotent: each call adds a new comment. Ziflow API: POST /proofs/{id}/comments.

Discovered
ziflow_add_reviewers

WRITE: add reviewers to an existing proof stage, with explicit approver (comment + decision) or commenter (comment only) permissions. Neither grants management or sharing rights. May notify reviewers. Does not move reviewers out of other stages. Get proof/stage IDs with ziflow_get_proof. Not idempotent; do not automatically retry. POST /proofs/{proof_id}/stages/{stage_id}/reviewers.

Discovered
ziflow_create_proof

WRITE: import files/videos into new Ziflow proofs from URLs Ziflow can download (including signed URLs or S3 with a configured credentials nickname). Local file bytes are not accepted by this API: upload them to approved storage first. Set approver/commenter permissions per stage and include owner_email as a reviewer in at least one stage. Multiple sources create a batch unless combine=true (combining depends on the Ziflow plan). Processing is asynchronous; use ziflow_get_proof to check completion. May email reviewers after processing; suppress_all_emails=true disables proof emails. Not idempotent: never automatically repeat creation after an uncertain result. POST /proofs.

Discovered
ziflow_get_comment

Get one comment on a proof by its id, including its replies, labels and resolved state. Ziflow API: GET /proofs/{id}/comments/{comment_id}.

Discovered
ziflow_get_folder

Get one folder by id, with its name and contents. Ziflow API: GET /folders/{id}.

Discovered
ziflow_get_proof

Get one proof by id: its name, status, stages, reviewers, deadlines, folder and version data. Ziflow API: GET /proofs/{id}.

Discovered
ziflow_get_user

Get one user by id or email address. Ziflow API: GET /users/{identifier}.

Discovered
ziflow_list_comments

List all comments on one proof, with their author, location (page or time), and resolved state. Ziflow API: GET /proofs/{id}/comments.

Discovered
ziflow_list_contacts

List the contacts (external reviewers saved in the account), with name and email. Ziflow API: GET /contacts.

Discovered
ziflow_list_folders

List the root folders the API user can see. Ziflow API: GET /folders.

Discovered
ziflow_list_proof_activities

List the activity log of one proof (who did what, and when), optionally between two dates. Ziflow API: GET /proofs/{id}/activities.

Discovered
ziflow_list_proofs

List proofs (review items) visible to the API user, with name, status, owner and deadlines. Good first call to discover proof ids. Ziflow API: GET /proofs.

Discovered
ziflow_list_users

List the users of the Ziflow account, with their roles and status. Ziflow API: GET /users.

Discovered
ziflow_list_webhooks

List the webhook subscriptions set up on the account, with their event types and target URLs. Ziflow API: GET /webhooks.

Discovered
ziflow_list_workflow_templates

List the workflow templates (review stages and reviewer sets) that new proofs can start from. Ziflow API: GET /workflowtemplates.

Discovered
ziflow_resolve_comment

Mark a comment as resolved, or reopen it. Setting the same state twice is harmless. Ziflow API: PUT /proofs/{id}/comments/{comment_id}/resolve.

Discovered
ziflow_search_proofs

Search proofs by name and status. Use proof_status to find, for example, proofs with changes_required or late. Ziflow API: POST /proofs/search.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected55 ms17