Production-ready MCP server providing RAG-based access to WSO2 documentation
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.
OPENAI_API_KEYAPI keyoptionalRequired only when EMBEDDING_PROVIDER=openai
GEMINI_API_KEYAPI keyoptionalRequired only when EMBEDDING_PROVIDER=gemini
VOYAGE_API_KEYAPI keyoptionalRequired only when EMBEDDING_PROVIDER=voyage
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.
search_wso2_docsSemantically search across all indexed WSO2 documentation and return the most relevant sections with metadata and source URLs.Semantically search across all indexed WSO2 documentation and return the most relevant sections with metadata and source URLs.
No input schema was published for this tool.
get_wso2_guideRetrieve documentation sections focused on a specific WSO2 product and topic.Retrieve documentation sections focused on a specific WSO2 product and topic.
No input schema was published for this tool.
explain_wso2_conceptRetrieve comprehensive documentation context for a WSO2 concept, searched across all products.Retrieve comprehensive documentation context for a WSO2 concept, searched across all products.
No input schema was published for this tool.
list_wso2_productsList all supported WSO2 documentation sources with their product IDs and base URLs.List all supported WSO2 documentation sources with their product IDs and base URLs.
No input schema was published for this tool.
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.
Production-ready MCP server providing RAG-based access to WSO2 documentation
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
88 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+76 more not listed. The counts by reason above cover all of them.
Not followed: optionalDependencies, peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.