mcpbeat

FaxSeal MCP Server

io.github.grichardomi/faxseal
answering

FaxSeal is answering right now. Last checked moments ago. 35 installs a week from npm. Last commit 2 Jul 2026.

Send, receive, and verify faxes from AI assistants and agents via FaxSeal.

Installs per day peak 30 · avg 9 · -47% w/w
a month agotoday
Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
357 ms
Response time
average over 24h
35
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add faxseal --transport http https://mcp-server-production-8f66.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "faxseal": {
      "url": "https://mcp-server-production-8f66.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.faxseal]
url = "https://mcp-server-production-8f66.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "faxseal": {
      "url": "https://mcp-server-production-8f66.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "faxseal": {
      "url": "https://mcp-server-production-8f66.up.railway.app/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp-server-production-8f66.up.railway.app/mcp streamable-http needs key 318 ms 0 min ago

FaxSeal — questions

Answers built from our own checks of this server.

Why is there no tool list for FaxSeal?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is FaxSeal working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 357 ms. The bar chart above shows every period we have measured.
How do I connect FaxSeal?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does FaxSeal need an API key?
Yes. Every time we knock, FaxSeal answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is FaxSeal?
It answers our handshake in 357 ms on average, which is faster than 39% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use FaxSeal?
The npm package faxseal-mcp was installed 35 times in the last week. Week over week that is -47%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is FaxSeal open source?
Yes — written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.