PayNow Component MCP Server
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": false
} |
| prompts | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_paynow_component_documentationA | Search PayNow Component documentation. Any non-English input will be auto-translated to English before populating the query. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| search_paynow_component_documentation | Search PayNow Component documentation and return matching sections |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly distinct and singular.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (search_paynow_component_documentation).
A single tool for a server named 'PayNow Component MCP Server' feels too thin and incomplete for the apparent domain. It suggests significant gaps in functionality beyond documentation search.
The server's name implies a domain related to PayNow components, but the tool only covers documentation search. There are obvious gaps, such as creating, updating, or managing components, which would be expected for a component server.