_ registry / mcp + a2a streamable-http · checked 4h ago

unseen-workflow-compiler

https://unseendocs.in

Registry code: 7a7ad94b5fe3703c

api record

Compile SOPs, policies, and playbooks into source-grounded visual flowcharts (SVG, Mermaid, JSON).

from a public catalogue that lists it, not from the operator

endpoint
https://unseendocs.in/mcp
door code
4764b3aacdb75c9b
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is unseen-workflow-compiler live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is unseen-workflow-compiler free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does unseen-workflow-compiler have?
9 tools: autofix_workflow, detect_workflows, get_workflow, compile_workflow, revise_workflow, enhance_workflow, auth_request_otp, auth_verify_otp, ….
Is unseen-workflow-compiler safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
783ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
8 auth-required 1 never probed 8 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • detect_workflows auth-required 4h ago

    Discover distinct operational workflows from multi-section documents or raw text before compiling. Returns candidate workflows (`id`, `title`, `description`, `sourceIds`) audited by TypeSafe Jev.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "text": {
      "type": "string",
      "description": "Optional raw document text if `sources` is not pre-segmented."
    },
    "sources": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "locator",
          "excerpt"
        ],
        "properties": {
          "id": {
            "type": "string"
          },
          "excerpt": {
            "type": "string"
          },
          "locator": {
            "type": "string"
          }
        }
      },
      "description": "Array of source excerpts `{id, locator, excerpt}` from the document."
    },
    "authToken": {
      "type": "string",
      "description": "Optional session token (`utok_...`) if not passed via Authorization header."
    }
  }
}
    arguments 36 lines
  • get_workflow auth-required 4h ago

    Retrieve an existing VisualSpec workflow by jobId or visualId, returning the spec, SVG layout, and Mermaid diagram.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The jobId or visualId of the workflow to retrieve"
    },
    "authToken": {
      "type": "string",
      "description": "Optional session token (`utok_...`) if not passed via Authorization header."
    }
  }
}
    arguments 16 lines
  • compile_workflow auth-required never probed

    Turn supplied document evidence or raw operational text into a publication-ready workflow diagram with source references, clean vector SVG, Mermaid, Excalidraw scene, and interactive Studio deep link (`studioUrl`). HOW TO STRUCTURE TEXT INPUTS: Either pass `sources` (array of 1..60 verbatim chunks `{id, locator, excerpt}` where each excerpt is <= 2000 chars with exact numbers/actors/thresholds preserved) OR pass raw `text` and Unseen will automatically segment it into source chunks. EDITING GUIDANCE: For cosmetic/styling/annotation edits, edit the returned `<svg>` XML directly. For structural/topological edits (adding/removing nodes or rerouting branches), edit `spec` (VisualSpec JSON) and call `autofix_workflow` ($0 deterministic connector healing + fresh SVG/Mermaid/Excalidraw) or `revise_workflow`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "schemaVersion",
    "userGoal",
    "sources"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "Optional raw document or user text. If provided when `sources` is omitted or empty, Unseen automatically segments `text` into faithful `sources[]` chunks."
    },
    "jobId": {
      "type": "string",
      "description": "Optional job ID when resuming a workflow after clarification"
    },
    "sources": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "locator",
          "excerpt"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "Unique chunk ID (e.g. 's1', 's2')"
          },
          "name": {
            "type": "string",
            "description": "Document or file name"
          },
          "excerpt": {
            "type": "string",
            "description": "Faithful document excerpt (do not rewrite)"
          },
          "locator": {
            "type": "string",
            "description": "Heading, page, or section locator"
          }
        }
      },
      "description": "Array of faithful source excerpts with locators from the input document (1..60 chunks, <=2000 chars each). Preserve exact thresholds, actors, and IF/ELSE branches."
    },
    "userGoal": {
      "type": "string",
      "description": "The overarching operational goal or process description (e.g. 'Driver Onboarding SOP' or 'Vendor Risk Assessment')"
    },
    "authToken": {
      "type": "string",
      "description": "Optional session token (`utok_...`) obtained from `auth_verify_otp` or `auth_login` if not already supplied in the HTTP `Authorization: Bearer` header."
    },
    "requestId": {
      "type": "string",
      "description": "Optional client request correlation ID"
    },
    "hostContext": {
      "type": "object",
      "properties": {
        "actors": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "ambiguities": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "assumptions": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "userContext": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "contradictions": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "description": "Optional advisory context observed by the host agent"
    },
    "priorAnswers": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "questionId",
          "answer",
          "source"
        ],
        "properties": {
          "answer": {
            "description": "User's answer to the clarification question"
          },
          "source": {
            "enum": [
              "user",
              "document",
              "host-context"
            ],
            "type": "string"
          },
          "questionId": {
            "type": "string"
          }
        }
      },
      "description": "Answers to prior Unseen clarification questions when resuming a compilation"
    },
    "desiredOutput": {
      "type": "object",
      "properties": {
        "depth": {
          "enum": [
            "macro",
            "detailed",
            "choose"
          ],
          "type": "string",
          "description": "Desired workflow abstraction depth"
        },
        "orientation": {
          "enum": [
            "portrait",
            "landscape",
            "choose"
          ],
          "type": "string",
          "description": "Desired visual orientation"
        }
      }
    },
    "schemaVersion": {
      "enum": [
        "0.1"
      ],
      "type": "string",
      "description": "Protocol envelope version (must be '0.1')"
    }
  }
}
    arguments 154 lines
  • revise_workflow auth-required never probed

    Apply targeted delta revisions to an existing VisualSpec workflow diagram (e.g. modify node labels, adjust roles like step vs decision, add/remove edges, or heal connections) while preserving Visual Contract v0.1 validity and source grounding.

    mcp-tool

    {
  "type": "object",
  "required": [
    "spec",
    "instruction"
  ],
  "properties": {
    "spec": {
      "type": "object",
      "description": "The existing VisualSpec object to revise"
    },
    "authToken": {
      "type": "string",
      "description": "Optional session token (`utok_...`) if not passed via Authorization header."
    },
    "instruction": {
      "type": "string",
      "description": "Clear revision instruction (e.g. 'Change node-2 role to decision and label to Finance Approval?', 'Remove orphan node-4', 'Autofix layout connections')"
    },
    "additionalSources": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "id",
          "locator",
          "excerpt"
        ],
        "properties": {
          "id": {
            "type": "string",
            "description": "Unique chunk ID"
          },
          "excerpt": {
            "type": "string",
            "description": "Faithful document excerpt"
          },
          "locator": {
            "type": "string",
            "description": "Heading or section locator"
          }
        }
      },
      "description": "Optional additional source evidence excerpts to support the revision"
    }
  }
}
    arguments 47 lines
  • enhance_workflow auth-required never probed

    Bundled free semantic verification and repair powered by TypeSafe Jev. Audits the VisualSpec against its cited `sources[]` for unsupported claims, missing decision branches, and role accuracy, applies targeted repair if actionable issues are found, and returns the enhanced `spec`, `svg`, `mermaid`, `excalidraw`, `studioUrl`, and Jev quality metrics.

    mcp-tool

    {
  "type": "object",
  "required": [
    "spec"
  ],
  "properties": {
    "spec": {
      "type": "object",
      "description": "The current VisualSpec JSON object (including its `sources` array) to audit and enhance."
    },
    "visualId": {
      "type": "string",
      "description": "The `jobId` or `visualId` returned when the workflow was compiled."
    },
    "authToken": {
      "type": "string",
      "description": "Optional session token (`utok_...`) if not passed via Authorization header."
    }
  }
}
    arguments 20 lines
  • auth_request_otp auth-required never probed

    Step 1 of Agent & Human Login (Email + OTP): Sends a 6-digit Login OTP (`UNSEEN_LOGIN_OTP`) to the user's email address. This is a passwordless Login OTP (NOT a password reset). Once called, the agent can either read the 6-digit `UNSEEN_LOGIN_OTP` directly from the user's email (when the user has granted email access) or ask the user in chat for the 6-digit code, then call `auth_verify_otp`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "description": "The user's email address to receive the 6-digit Login OTP."
    }
  }
}
    arguments 12 lines
  • auth_verify_otp auth-required never probed

    Step 2 of Agent & Human Login (Email + OTP): Verifies the 6-digit Login OTP sent to `email` and returns `{ token: 'utok_...', user }` (30 free credits / 3 visuals per month on new accounts). Pass the returned `token` as `Authorization: Bearer <token>` or in the `authToken` argument of subsequent MCP tool calls.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email",
    "otp"
  ],
  "properties": {
    "otp": {
      "type": "string",
      "description": "The 6-digit Login OTP read from the user's email (`UNSEEN_LOGIN_OTP`) or supplied by the user."
    },
    "email": {
      "type": "string",
      "description": "The user's email address."
    }
  }
}
    arguments 17 lines
  • auth_login auth-required never probed

    Authenticate an existing Unseen account using `email` and `password` (or create one if `register: true`), returning `{ token: 'utok_...', user }` for use in `Authorization: Bearer <token>` or `authToken`.

    mcp-tool

    {
  "type": "object",
  "required": [
    "email",
    "password"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Optional display name when registering."
    },
    "email": {
      "type": "string",
      "description": "The user's email address."
    },
    "password": {
      "type": "string",
      "description": "Account password (min 8 characters)."
    },
    "register": {
      "type": "boolean",
      "description": "Set to true to register a new Email + Password account if it does not exist yet."
    }
  }
}
    arguments 25 lines
  • autofix_workflow unknown 4h ago

    Deterministic connector healing and full visual re-rendering ($0 compute cost, instant, unlimited). Rescues orphan nodes, heals broken or missing decision branches, recomputes deterministic orthogonal layout, and returns fresh `spec`, `svg`, `mermaid`, `excalidraw`, and `studioUrl`. Use this tool after making direct structural edits to `VisualSpec` JSON (`nodes` / `edges`), or when a user asks to autofix connectors.

    mcp-tool

    {
  "type": "object",
  "required": [
    "spec"
  ],
  "properties": {
    "spec": {
      "type": "object",
      "description": "The VisualSpec JSON object to deterministically heal and re-render into SVG, Mermaid, and Excalidraw."
    },
    "authToken": {
      "type": "string",
      "description": "Optional session token (`utok_...`) if not passed via Authorization header."
    },
    "orientation": {
      "enum": [
        "portrait",
        "landscape"
      ],
      "type": "string",
      "description": "Optional layout orientation (defaults to portrait)."
    }
  }
}
    arguments 24 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7a7ad94b5fe3703c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7a7ad94b5fe3703c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7a7ad94b5fe3703c/badge.svg)](https://brick.blue/agent/7a7ad94b5fe3703c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
282ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.