
すぐFAX MCP server
Which MCP servers are すぐFAX's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.sugufax/fax-creditsverified in the MCP registry
The registry name sits under sugufax.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools5
- Server calls itselfsugufax
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 177 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- send_fax, create_upload_link change data without a sign-in: anyone with the address can call them.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer523 ms
- Space in an agent's context≈ 627 tokensthe definitions of all its tools (5), which an agent carries on every turn
- Tool definitionsA · 97 of 100
- Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
- No description an agent can choose by: 1 of 5
Worth a look
- Tools that change data, on a server that answers without a sign-in: send_fax, create_upload_link
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_fax_price送信先とページ数からFAXの料金(日本円・税込)を確認します。送信先が対応しているか(携帯電話番号・0990・0570などは不可)もわかります。何も送信されません。
send_faxAIクレジットを使って、実際にFAXを送信します(1クレジット=FAX1回、100ページまでページ数に関係なく1クレジット)。書類(いずれか1つ):"upload_id"(create_upload_link で作成、ユーザーの端末にあるファイル用)、"file"(ChatGPTで添付されたファイル、自動入力)、"document_url"(公開PDFの直接HTTPSリンク)、"document_base64"(700KBまでの小さなファイルのみ)。PDF・JPG・PNG、…
get_fax_statussend_fax の結果の token を使って、FAXの送信状況(お支払い待ち・予約中・送信中・完了など)を確認します。完了していれば送信完了レポートのURLも返します。
create_upload_linkFAX書類(PDF・JPG・PNG、最大10MB)をアップロードするための、安全なワンタイムURL(30分有効)を作成します。スマートフォンやパソコンからアップロードでき、カメラ撮影にも対応しています。ユーザーが upload_url でアップロードした後、upload_id を send_fax に渡します。リンクの作成では何も送信されず、料金もかかりません。
get_credit_balanceAIクレジットの残高を確認します。
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"fax-credits": {
"type": "http",
"url": "https://sugufax.com/api/mcp-credits.php"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http sugufax https://sugufax.com/api/mcp-credits.phpclaude.ai, ChatGPT and other clients: add https://sugufax.com/api/mcp-credits.php as a custom connector in the settings.
- com.sugufax/faxanswers, requires sign-inverified in the MCP registry
- com.sugufax/fax-payperuseanswers, 4 toolsverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.