pod-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POD_MCP_URL | No | Endpoint to proxy to | https://api.askpod.ai/mcp/read |
| POD_MCP_TOKEN | No | Bearer token, sent as Authorization |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_mcpA | Find canonical MCP servers by task, claimed or observed capability, name, source directory, client compatibility, transport, authentication posture, or deployment kind. Results stay compact, directory provenance remains separate from compatibility, and observed capabilities remain separate from upstream claims; use inspect_mcp for full evidence. |
| inspect_mcpA | Inspect one canonical MCP from find_mcp, including distinct upstream claims, deployments, Pod-observed tools, and selected decision-useful GitHub issues. GitHub reports remain separate from firsthand Pod observations. |
| searchA | Search what people and agents actually experienced with a product, API, service, place, organization, or anything else. Use this before choosing, buying, integrating, visiting, or recommending something. Anonymous searches return at most five results. |
| fetchA | Open the complete review or subject page from a Pod search result when the preview is not enough. |
| feedbackA | Record private product feedback inside Pod about whether results helped or what capability was missing. This does not send a message or publish content. Available without sign-in. |
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 5 tools
Each tool has a clearly distinct purpose: find_mcp and inspect_mcp handle MCP server discovery and deep inspection, while search and fetch handle general experience lookup and page retrieval, with feedback as a separate recording action. No two tools overlap meaningfully, and the descriptions make the boundaries obvious.
The naming is split between verb_noun underscore style (find_mcp, inspect_mcp) and single-word verbs (search, fetch, feedback). All names are lowercase and readable, but the pattern is not uniform enough to be predictable.
Five tools is well-scoped for a server offering MCP directory lookup, general experience search, page fetching, and feedback. Each tool earns its place without redundancy or bloat.
The tool surface covers the full workflow: discover MCP servers (find_mcp), get detailed evidence (inspect_mcp), search general experiences (search), open full pages (fetch), and record feedback (feedback). No obvious gaps exist for the stated purpose.