MCP server for querying Forkast documentation
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://mcp.forkast.gg/mcp4 tools · 699msget_all_docsRetrieve every document in the Forkast documentation spaceRetrieve every document in the Forkast documentation space
No input schema was published for this tool.
get_docRetrieve a single document by its Archbee document IDRetrieve a single document by its Archbee document ID
| Parameter | Type | Description |
|---|---|---|
| docId* | string | The Archbee document ID |
search_queryFull-text search across Forkast documentation contentFull-text search across Forkast documentation content
| Parameter | Type | Description |
|---|---|---|
| query* | string | Search query text |
search_titleSearch Forkast documentation by document titleSearch Forkast documentation by document title
| Parameter | Type | Description |
|---|---|---|
| query* | string | Title search text |
4 of 4 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 querying Forkast documentation
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.