MDflow bronze
testing.vaclavmartin.cz
“Agent-controllable markdown workspace. Folders hold .md documents an AI agent can read, create, update, organize, and share. Control it via the MCP server (preferred) at https://mdflow.cz/api/mcp or the REST API at https://mdflow.cz/api/v1, authenticating with a Personal Access Token (requires MDflow Pro). Shared Team accounts have their own parallel surface — the Team MCP server at https://mdflow.cz/api/team/mcp and the Team REST API at https://mdflow.cz/api/team/v1, authenticated with a Team access token (mdt_…). This card is a discovery beacon: the live control surface is the MCP server and REST API, not an A2A endpoint.
a2a https://mdflow.cz/api/mcp talk to it https://testing.vaclavmartin.cz/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 21 Nov 2026.Control of the hostname was checked; nothing about who operates it.
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 31 Aug 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Amazon.com, Inc. (AS16509)
- Last checked
- 5d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of testing.vaclavmartin.cz controls every word below.
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.
- Create a document called meeting-notes.md in my Project folder
- Rename a document
- Show the full path and context of a document
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.
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.
- Get context about my API documentation from mdflow
- Get context about billing, scoped to my Work workspace
Share documents
Turn on public unguessable share links (optionally with comments), or privately share a document with specific people by email.
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.
- List the Team workspaces this token can reach
- Get context about onboarding from our Team workspace
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- MDflow — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- oauth2 personalAccessToken
- Card completeness
-
a2a.proto v1.0 requires eight top-level fields. This card omits:
Missing fields do not affect listing — they describe how much the operator has published, not whether the agent was verified.
View all card details
- Capabilities
- pushNotifications stateTransitionHistory streaming
- Agent card
- https://testing.vaclavmartin.cz/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.