gatehouse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_toolsA | Find agent tools (MCP servers, Claude Code skills, plugins, subagents, agent frameworks) in the Gatehouse registry. Filter by free-text query, category, kind, or vetting status. Returns a ranked list (vetted first) with each tool's status and health. Use get_tool for the full record or check_tool for a quick "is it safe" verdict. |
| check_toolA | The quick trust verdict for one agent tool: has Gatehouse hands-on vetted it, and what did it find? Call this at the moment of deciding whether to install/enable a tool. Returns the vetting status, the one-paragraph verdict, liveness, and the install line. For the full audit write-up use get_tool. |
| get_toolA | The complete Gatehouse record for one agent tool: metadata, compatibility, liveness/health, the vetting verdict, and — when it exists — the full first-hand audit write-up (how it was tested, what it injects, the caveats). Use check_tool instead if you only need the quick safe/not verdict. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: search_tools for discovery, check_tool for quick trust verdict, and get_tool for full audit details. No overlap in functionality.
Tools follow verb_noun pattern, but 'search_tools' uses plural while 'check_tool' and 'get_tool' are singular, introducing minor inconsistency.
Three tools are well-scoped for a read-only registry: search, quick check, and full retrieval. No unnecessary tools and no missing essentials.
Covers the complete lifecycle for a tool registry: discovery (search), quick assessment (check), and detailed record (get). No obvious gaps given the read-only domain.