すぐFAX SuguFAX – Fax to Japan from AI
REMOTE · SUGUFAX.COM
Fax PDFs/photos to Japan from Claude/ChatGPT. OAuth: pay per fax from ¥400 or credits. AIから日本へFAX
Available components
Last scanned (1 hour ago)
Scores higher than 39% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Communication
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 12 Oct 26 39
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 17 Oct 2026 · Probed https://sugufax.com/api/mcp-oauth.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 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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://sugufax.com/.well-known/oauth-protected-resource/api/mcp-oauth.php", scope="fax", error_description="すぐFAXにログインしてください。"
Bearer resource_metadata="https://sugufax.com/.well-known/oauth-protected-resource/api/mcp-oauth.php", scope="fax", error_description="すぐFAXにログインしてください。"| 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=() |
| www-authenticate | Bearer resource_metadata="https://sugufax.com/.well-known/oauth-protected-resource/api/mcp-oauth.php", scope="fax", error_description="すぐFAXにログインしてください。" |
Protected resource metadata
| Document | https://sugufax.com/.well-known/oauth-protected-resource/api/mcp-oauth.php |
|---|---|
| Retrieved | Yes |
| Resource | https://sugufax.com/api/mcp-oauth.php |
| Authorisation server | https://sugufax.com |
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-oauth.php | Auth required | 401 | |
| http (plaintext) | http://sugufax.com/api/mcp-oauth.php | HTTPS enforced | 301 | https://sugufax.com/api/mcp-oauth.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 →
No tool schema has been captured from this endpoint yet.
How do I install the すぐFAX SuguFAX – Fax to Japan from AI MCP server?
すぐFAX SuguFAX – Fax to Japan from AI is a hosted endpoint at https://sugufax.com/api/mcp-oauth.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 'https://sugufax.com/api/mcp-oauth.php'
What is the すぐFAX SuguFAX – Fax to Japan from AI MCP server?
すぐFAX SuguFAX – Fax to Japan from AI is an MCP server listed in the public MCP registry as com.sugufax/fax. Fax PDFs/photos to Japan from Claude/ChatGPT. OAuth: pay per fax from ¥400 or credits. AIから日本へFAX. This page covers its hosted endpoint (https://sugufax.com/api/mcp-oauth.php).
Is the すぐFAX SuguFAX – Fax to Japan from AI MCP server safe to use?
すぐFAX SuguFAX – Fax to Japan from AI scores 39 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.
Does the すぐFAX SuguFAX – Fax to Japan from AI MCP server require authentication?
Yes. すぐFAX SuguFAX – Fax to Japan from AI 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 すぐFAX SuguFAX – Fax to Japan from AI MCP server still maintained?
すぐFAX SuguFAX – Fax to Japan from AI is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.