すぐFAX SuguFAX – Pay per fax (no account)
REMOTE · SUGUFAX.COM
Fax to Japan from AI, no account: Stripe link per fax, from ¥400, up to 100 pages. 1回払いでFAX送信
Available components
Last scanned (7 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Documents and Files
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (send_fax). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1185 tokens (~296/item across 4 items; 4 tools + 0 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 Management20
- Stability observed for 6 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 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
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.
- 18 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 65
First indexed and scored.
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 18 Oct 2026 · Probed https://sugufax.com/api/mcp.php
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sugufax.com | CN=YE1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6c0890752a8d2d74613cc30d3b9b50959e2 |
| SANs: sugufax.com, www.sugufax.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sugufax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sugufax.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sugufax.com/api/mcp.php | Verified | 200 | |
| http (plaintext) | http://sugufax.com/api/mcp.php | HTTPS enforced | 301 | https://sugufax.com/api/mcp.php |
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 →
create_upload_link アップロード用リンクを作成 ~111
FAX書類（PDF・JPG・PNG、最大10MB）をアップロードするための、安全なワンタイムURL（30分有効）を作成します。スマートフォンやパソコンからアップロードでき、カメラ撮影にも対応しています。ユーザーが upload_url でアップロードした後、upload_id を send_fax に渡します。リンクの作成では何も送信されず、料金もかかりません。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fax_price FAX料金を確認 ~143
送信先とページ数からFAXの料金（日本円・税込）を確認します。送信先が対応しているか（携帯電話番号・0990・0570などは不可）もわかります。何も送信されません。
| Name | Type | Req | Description |
|---|---|---|---|
| fax_number | string | yes | 送信先のFAX番号。日本の形式（03-1234-5678）または国際形式（+81312345678） |
| pages | integer | – | ページ数（省略時1） |
| promo_code | string | – | 任意：クーポンコード（割引後の料金を確認） |
No output schema declared.
No examples provided.
get_fax_status FAXの状況を確認 ~84
send_fax の結果の token を使って、FAXの送信状況（お支払い待ち・予約中・送信中・完了など）を確認します。完了していれば送信完了レポートのURLも返します。
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | send_fax が返した token（32文字） |
No output schema declared.
No examples provided.
send_fax FAXを送信 ~508
FAXの送信を受け付け、Stripeのお支払いURL（checkout_url、日本円）を返します。お支払いが完了すると自動で送信されます。書類（いずれか1つ）："upload_id"（create_upload_link で作成、ユーザーの端末にあるファイル用）、"file"（ChatGPTで添付されたファイル、自動入力）、"document_url"（公開PDFの直接HTTPSリンク）、"document_base64"（700KBまでの小さなファイルのみ）。PDF・JPG・PNG、最大10MB・100ページ。scheduled_at を指定すると、その日時（日本時間）に送信します。
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | – | 小さなファイル（700KBまで）のみ：PDF・JPG・PNGのbase64またはdata: URI。通常は create_upload_link をお使いください。 |
| document_name | string | – | 任意：書類のファイル名（送信完了レポートに表示） |
| document_url | string | – | 公開されているPDFの直接HTTPSリンク（ログインやプレビューのページは不可） |
| string | – | 任意：確認メールと送信完了レポートの送信先（省略時はお支払い画面で入力） | |
| fax_number | string | yes | 送信先のFAX番号（例：03-1234-5678 または +81312345678） |
| file | object | – | ChatGPT：チャットに添付されたFAX書類（PDF・JPG・PNG）。ChatGPTが自動で入力します。 |
| promo_code | string | – | 任意：すぐFAXのクーポンコード（例：SUGU15-AB2CD3）。ユーザーがクーポンを持っている場合のみ。割引後の金額で checkout_url が作成されます。 |
| scheduled_at | string | – | 任意：送信日時（日本時間）。例：2026-10-10T09:00（オフセットなし＝日本時間）。15分後〜30日後まで。省略すると今すぐ送信。 |
| upload_id | string | – | create_upload_link が返した upload_id（ユーザーがアップロードした後）。1回のみ使用可能。 |
No output schema declared.
No examples provided.
How do I install the すぐFAX SuguFAX – Pay per fax (no account) MCP server?
すぐFAX SuguFAX – Pay per fax (no account) is a hosted endpoint at https://sugufax.com/api/mcp.php, 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 · sugufax.com
claude mcp add --transport http com-sugufax-fax-payperuse 'https://sugufax.com/api/mcp.php'
What is the すぐFAX SuguFAX – Pay per fax (no account) MCP server?
すぐFAX SuguFAX – Pay per fax (no account) is an MCP server listed in the public MCP registry as com.sugufax/fax-payperuse. Fax to Japan from AI, no account: Stripe link per fax, from ¥400, up to 100 pages. 1回払いでFAX送信. This page covers its hosted endpoint (https://sugufax.com/api/mcp.php).
Is the すぐFAX SuguFAX – Pay per fax (no account) MCP server safe to use?
すぐFAX SuguFAX – Pay per fax (no account) scores 68 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 すぐFAX SuguFAX – Pay per fax (no account) MCP server expose?
すぐFAX SuguFAX – Pay per fax (no account) exposes 4 tools: get_fax_price, send_fax, get_fax_status, create_upload_link. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Does the すぐFAX SuguFAX – Pay per fax (no account) MCP server require authentication?
No. We connected to すぐFAX SuguFAX – Pay per fax (no account) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the すぐFAX SuguFAX – Pay per fax (no account) MCP server still maintained?
すぐFAX SuguFAX – Pay per fax (no account) is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.