Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Flowie Developer Docs

REMOTE · DOCS.GET-FLOWIE.COM

Search and read the Flowie Exchange API docs and OpenAPI contract. No sign-in needed.

+3 this week 81 Trust /100

Last scanned (19 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Code Search and Documentation

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security77
Transport & Reachability100
Schema Quality & AI Usability85
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 872 tokens (~51/item across 17 items; 5 tools + 12 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
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 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 20 Oct 26 74

    First indexed and scored.

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 4 Nov 2026 · Probed https://docs.get-flowie.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=docs.get-flowie.com CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 f4e69b4ae5565ea0138e99151759bb6b
SANs: docs.get-flowie.com
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

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of docs.get-flowie.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
get-flowie.com. present 2371 13 Verified
docs.get-flowie.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://docs.get-flowie.com/mcp Verified 200
http (plaintext) http://docs.get-flowie.com/mcp HTTPS enforced 301 https://docs.get-flowie.com/mcp
MCP tools · 5 exposed · ~437 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
docs_get_auth_guide ~67

Return the authentication walkthrough for agents: how to get a sandbox key with no signup, how a user hands an agent scoped access, error handling and revocation.

NameTypeReqDescription
sectionstring–Optional section to return: discover, register, claim, use, errors, revocation.

No output schema declared.

No examples provided.

docs_list_endpoints ~129

List the API's operations (method, path, summary) from the OpenAPI contract, optionally filtered by a substring of the path or summary.

NameTypeReqDescription
filterstring–Optional substring filter, e.g. 'documents' or 'lifecycle'.
formatstring–'list' for method/path/summary lines (default), or 'openapi' for the raw OpenAPI definition.
limitinteger–Max operations (default 50).
pathstring–With format=openapi, return just this path, e.g. /v1/documents/send.

No output schema declared.

No examples provided.

docs_read_page ~52

Read a documentation page as markdown. Accepts a full URL from search_docs, or a path such as /reference/ or /guides/send-invoice.

NameTypeReqDescription
urlstringyesPage URL or path.

No output schema declared.

No examples provided.

docs_search ~70

Search the Flowie Exchange API documentation and return the most relevant pages with their URLs and descriptions. Use this first when you need to find where something is documented.

NameTypeReqDescription
limitinteger–Max results (default 8).
querystringyesWhat to search for, in natural language or keywords.

No output schema declared.

No examples provided.

sandbox_create_credential ~119

Mint a working sandbox API key with no signup and no human in the loop. Returns an apiKey (flw_test_...), an organizationId, a seeded company with a Peppol id, and suggested next steps. Sandbox data is synthetic and never reaches a real network - never send real personal data to it. This key gives no access to any real account.

NameTypeReqDescription
includeNextStepsboolean–Include the suggested next-step instructions in the result. Default true. Set false when you already know the flow and only want the credential.

No output schema declared.

No examples provided.

Install

How do I install the Flowie Developer Docs MCP server?

Flowie Developer Docs is a hosted endpoint at https://docs.get-flowie.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · docs.get-flowie.com

# add to Claude Code
claude mcp add --transport http com-get-flowie-docs 'https://docs.get-flowie.com/mcp'
Common questions

What is the Flowie Developer Docs MCP server?

Flowie Developer Docs is an MCP server listed in the public MCP registry as com.get-flowie/docs. Search and read the Flowie Exchange API docs and OpenAPI contract. No sign-in needed. This page covers its hosted endpoint (https://docs.get-flowie.com/mcp).

Is the Flowie Developer Docs MCP server safe to use?

Flowie Developer Docs scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Flowie Developer Docs MCP server expose?

Flowie Developer Docs exposes 5 tools: docs_search, docs_read_page, docs_list_endpoints, docs_get_auth_guide, sandbox_create_credential. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.

Does the Flowie Developer Docs MCP server require authentication?

No. We connected to Flowie Developer Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Flowie Developer Docs MCP server still maintained?

Flowie Developer Docs is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.