fmsg
REMOTE · {API_KEY_MCP_ENDPOINT} · 3 COMPONENTS · SCANNED SEP 22
Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
Available components
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: this endpoint is not published over https, so there is no plaintext variant to compare against. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.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.
How do I install the fmsg MCP server?
fmsg is a hosted endpoint at https://{api_key_mcp_endpoint}/, 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 · {api_key_mcp_endpoint}
claude mcp add --transport http markmnl-fmsg-mcp 'https://{api_key_mcp_endpoint}/' {
"mcpServers": {
"markmnl-fmsg-mcp": {
"url": "https://{api_key_mcp_endpoint}/"
}
}
} {
"servers": {
"markmnl-fmsg-mcp": {
"type": "http",
"url": "https://{api_key_mcp_endpoint}/"
}
}
} [mcp_servers.markmnl-fmsg-mcp]
url = "https://{api_key_mcp_endpoint}/" {
"$schema": "https://opencode.ai/config.json",
"mcp": {
"markmnl-fmsg-mcp": {
"type": "remote",
"url": "https://{api_key_mcp_endpoint}/",
"enabled": true
}
}
} openclaw mcp add markmnl-fmsg-mcp --url 'https://{api_key_mcp_endpoint}/' --transport streamable-http mcp_servers:
markmnl-fmsg-mcp:
url: "https://{api_key_mcp_endpoint}/" {
"McpServers": {
"markmnl-fmsg-mcp": {
"Transport": "http",
"Url": "https://{api_key_mcp_endpoint}/"
}
}
} assistant mcp add markmnl-fmsg-mcp -t streamable-http -u 'https://{api_key_mcp_endpoint}/' {
"mcpServers": {
"markmnl-fmsg-mcp": {
"type": "http",
"url": "https://{api_key_mcp_endpoint}/"
}
}
} 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.
- 17 Sept 26 0
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 22 Sept 2026 · Probed https://{api_key_mcp_endpoint}
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of https://{api_key_mcp_endpoint}. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| https://{api_key_mcp_endpoint}. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://{api_key_mcp_endpoint} | Unreachable | ||
| http (plaintext) | Inconclusive |
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.
What is the fmsg MCP server?
fmsg is an MCP server listed in the public MCP registry as io.github.markmnl/fmsg-mcp. Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key. This page covers its hosted endpoint (https://{api_key_mcp_endpoint}).
Is the fmsg MCP server safe to use?
fmsg scores 0 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 fmsg MCP server require authentication?
Its publisher declares that fmsg requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.