Re:port Flow MCP
REMOTE · MCP.RE-PORT-FLOW.COM · 2 COMPONENTS · SCANNED SEP 20
Generate PDF reports from Re:port Flow templates via Claude and other AI agents.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 934 tokens (~233/item across 4 items; 2 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management19
- Stability check failed: schema churn in the 30 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Re:port Flow MCP server?
Re:port Flow MCP is a hosted endpoint at https://mcp.re-port-flow.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 · mcp.re-port-flow.com
claude mcp add --transport http re-port-flow-reportflow-mcp 'https://mcp.re-port-flow.com/mcp'
{
"mcpServers": {
"re-port-flow-reportflow-mcp": {
"url": "https://mcp.re-port-flow.com/mcp"
}
}
} {
"servers": {
"re-port-flow-reportflow-mcp": {
"type": "http",
"url": "https://mcp.re-port-flow.com/mcp"
}
}
} [mcp_servers.re-port-flow-reportflow-mcp] url = "https://mcp.re-port-flow.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"re-port-flow-reportflow-mcp": {
"type": "remote",
"url": "https://mcp.re-port-flow.com/mcp",
"enabled": true
}
}
} openclaw mcp add re-port-flow-reportflow-mcp --url 'https://mcp.re-port-flow.com/mcp' --transport streamable-http
mcp_servers:
re-port-flow-reportflow-mcp:
url: "https://mcp.re-port-flow.com/mcp" {
"McpServers": {
"re-port-flow-reportflow-mcp": {
"Transport": "http",
"Url": "https://mcp.re-port-flow.com/mcp"
}
}
} assistant mcp add re-port-flow-reportflow-mcp -t streamable-http -u 'https://mcp.re-port-flow.com/mcp'
{
"mcpServers": {
"re-port-flow-reportflow-mcp": {
"type": "http",
"url": "https://mcp.re-port-flow.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 9 Sept 26 +2
- Schema quality: 435 → 233 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 8 Sept 26 −12
- Stability: pass → fail ▼ security
- Schema quality: 262 → 435 ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 7 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 6 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 5 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 4 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 3 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 20 Sept 2026 · Probed https://mcp.re-port-flow.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=re-port-flow.com | CN=WE1,O=Google Trust Services,C=US | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4d16fa76159d56e10e15c412987f123c |
| SANs: re-port-flow.com, mcp.re-port-flow.com, *.mcp.re-port-flow.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 insecure
Validation of mcp.re-port-flow.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| re-port-flow.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="reportflow-mcp", resource_metadata="https://mcp.re-port-flow.com/.well-known/oauth-protected-resource"
Bearer realm="reportflow-mcp", resource_metadata="https://mcp.re-port-flow.com/.well-known/oauth-protected-resource"Protected resource metadata
| Document | https://mcp.re-port-flow.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.re-port-flow.com |
| Authorisation server | https://mcp.re-port-flow.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.re-port-flow.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.re-port-flow.com/mcp | HTTPS enforced | 301 | https://mcp.re-port-flow.com/mcp |
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 →
get_gallery_template ~163
公開テンプレートギャラリーのテンプレート詳細を slug で取得します（認証不要）。説明全文・カテゴリ・タグ・サムネイルURL・テンプレート版・複製実績数・作成者名を返します。slug は search_gallery_templates の結果から取得してください。重要: ギャラリーのテンプレートはまだワークスペースにありません。この slug では PDF 生成できないため、使う場合は copy_gallery_template で複製し、返された designId を get_design_parameters / generate_pdf_sync に渡してください。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | テンプレートの slug（search_gallery_templates の結果に含まれる識別子） |
No output schema declared.
No examples provided.
search_gallery_templates ~258
公開テンプレートギャラリーから、まだワークスペースに取り込んでいないテンプレートをキーワードで探します（認証不要）。タイトル・説明・タグ・カテゴリの部分一致で絞り込み、各候補の slug・title・description・category・tags・thumbnailUrl・duplicateCount を返します。ワークスペース内の既存デザインを探す場合はこのツールではなく list_templates / search を使ってください。重要: このツールが返す slug では PDF 生成できません。先に copy_gallery_template で自分のワークスペースへ複製し、返された designId を get_design_parameters / generate_pdf_sync に渡してください。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | カテゴリ code で絞り込み（任意。例: "invoice", "other"） |
| limit | integer | – | 返す最大件数（既定 20、上限 50。超過分は残り件数として通知） |
| query | string | yes | 検索キーワード（タイトル・説明・タグ・カテゴリの部分一致。1文字以上） |
No output schema declared.
No examples provided.
What is the Re:port Flow MCP server?
Re:port Flow MCP is listed in the public MCP registry as io.github.re-port-flow/reportflow-mcp. Generate PDF reports from Re:port Flow templates via Claude and other AI agents. This page covers its hosted endpoint (https://mcp.re-port-flow.com/mcp).
Is the Re:port Flow MCP server safe to use?
Re:port Flow MCP scores 80 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 Re:port Flow MCP server expose?
Re:port Flow MCP exposes 2 tools: search_gallery_templates, get_gallery_template. Their descriptions and schemas cost roughly 421 tokens of context every time the server is loaded.
Does the Re:port Flow MCP server require authentication?
Yes. Re:port Flow MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Re:port Flow MCP server still maintained?
Re:port Flow MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.