MCP server for fmsg: send and receive federated messages from any AI agent via a deployed fmsg Web API
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
FMSG_API_KEYAPI keyrequiredfmsg API key (fmsgk_...) for the address to send as
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
whoamiReport the fmsg address this server acts as (derived from the API key), the fmsg Web API URL,Report the fmsg address this server acts as (derived from the API key), the fmsg Web API URL,
No input schema was published for this tool.
resolve_addressResolve a short name to a full fmsg address without sending anything: a literal @user@domain is returnedResolve a short name to a full fmsg address without sending anything: a literal @user@domain is returned
No input schema was published for this tool.
list_messagesList messages received by this address, newest first. Each item carries the id, sender, recipients, topic,List messages received by this address, newest first. Each item carries the id, sender, recipients, topic,
No input schema was published for this tool.
list_sentList messages sent by this address (including unsent drafts, shown with time null), newest first, withList messages sent by this address (including unsent drafts, shown with time null), newest first, with
No input schema was published for this tool.
get_messageFetch one message with its full body (for text-like types), headers, recipients, added recipients,Fetch one message with its full body (for text-like types), headers, recipients, added recipients,
No input schema was published for this tool.
get_threadReconstruct the conversation a message belongs to: the direct lineage from the thread root down to the givenReconstruct the conversation a message belongs to: the direct lineage from the thread root down to the given
No input schema was published for this tool.
delivery_statusPer-recipient delivery state for a message this address sent: delivered time and the receiving host'sPer-recipient delivery state for a message this address sent: delivered time and the receiving host's
No input schema was published for this tool.
mark_readMark received messages as read. Reading a message with get_message does not mark it read.Mark received messages as read. Reading a message with get_message does not mark it read.
No input schema was published for this tool.
download_attachmentDownload one attachment of a message. Up to max_inline_bytes the bytes are returned inline as an embeddedDownload one attachment of a message. Up to max_inline_bytes the bytes are returned inline as an embedded
No input schema was published for this tool.
send_messageNo description publishedThis tool published no description. Forge does not invent one.
replyNo description publishedThis tool published no description. Forge does not invent one.
add_recipientsAdd recipients to a message that was already sent (one you sent or received as a primary recipient).Add recipients to a message that was already sent (one you sent or received as a primary recipient).
No input schema was published for this tool.
reactSet or clear your emoji reaction on a message (one reaction per person; a new emoji replaces the previous).Set or clear your emoji reaction on a message (one reaction per person; a new emoji replaces the previous).
No input schema was published for this tool.
wait_for_messageBlock until the next inbound message arrives (pushed over the fmsg host's WebSocket) and return it with itsBlock until the next inbound message arrives (pushed over the fmsg host's WebSocket) and return it with its
No input schema was published for this tool.
12 of 14 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for fmsg: send and receive federated messages from any AI agent via a deployed fmsg Web API
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.