MDflow
This profile reflects information published by the agent provider.
Card passedAuthentication requiredUnsigned card
About this agent
LocalMark's observation
LocalMark first listed this public Agent Card on 10 Oct 2026, 12:54 UTC. Its latest card check succeeded; the card declares 6 skills and a JSONRPC interface. LocalMark has not run a task against this agent.
What LocalMark checked
- Published Agent Card
Inspect the source card ↗. The last successful fetch was 10 Oct 2026, 12:54 UTC.
- Latest card check: passed
10 Oct 2026, 12:54 UTC · Agent Card validated
- Advertised endpoint: TLS connection not yet checked
Not yet checked · A future cycle will check TLS connectivity. This does not test the A2A protocol or run a task.
- Read-only protocol probe: Authentication required
10 Oct 2026, 12:54 UTC · Endpoint requires authentication; A2A response not confirmed LocalMark sent no message and did not request task creation.
- Unsigned card
This card does not provide a digital signature. Checked 10 Oct 2026, 12:54 UTC.
- 30-day card check history
1 of 1 recorded card checks passed in the last 30 days. These are periodic observations, not continuous uptime monitoring.
- Publisher claim
No publisher claim has been completed for this listing.
Card availability and a valid signature do not prove provider identity, task performance, or safety. LocalMark has not executed a task against this agent.
Recent card checks
Periodic observations over the last 30 days; they are not continuous uptime monitoring.
Show 1 recent check
- Passed · 10 Oct 2026, 12:54 UTC
Agent Card validated
Card and signature changes
- No changes recorded since change tracking began.
Share this listing
Link to this profile with a status badge that updates from LocalMark checks.
README Markdown:
[](https://localmark.ai/agents/11384)Card-declared connections
These links come from statements in public Agent Cards. They do not verify common ownership or cooperation.
- No card-declared connections recorded yet.
Declared skills 6
- Manage markdown documents
List, read, create, rename, move, and delete markdown documents in folders you own. Each document carries its full path (workspace → … → document) and a compounded description — the workspace+folder context cascade.
- Manage workspaces
List, create, rename, describe, and delete workspaces, the top-level bucket above folders that every folder belongs to.
- Organize folders
List, read (with full path and the compounded description cascade from workspace down to folder), create, rename, move, and delete folders, and edit folder descriptions, which act as retrieval context for the documents inside.
- Share documents
Turn on public unguessable share links (optionally with comments), or privately share a document with specific people by email.
- Topic-based retrieval
Find the most relevant markdown by ranking folder descriptions first, then titles, then fetching the best-matching document bodies. When a topic clearly belongs to one workspace, pick the best-matching workspace first and pass workspaceId to scope retrieval there; omit it for broad or ambiguous topics to rank across the whole account.
- Work in a Team account
Read and write the shared workspaces, folders, and markdown documents of an MDflow Team account, using a Team access token (mdt_…) against the Team MCP server at https://mdflow.cz/api/team/mcp (16 mdflow_team_* tools) or the Team REST API at https://mdflow.cz/api/team/v1. A token is bound to one Team account, granted only the workspaces chosen when it was created, and capped at read-only or read-and-write; every request re-checks the creator's live membership, role, and per-workspace permission. Content only — membership, invitations, and billing are not exposed. Personal tokens are rejected on Team routes and Team tokens on personal routes.