agenticpay
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTICPAY_BRIDGE_RPC | No | Solana JSON-RPC URL | https://api.devnet.solana.com |
| AGENTICPAY_BRIDGE_TOOLS | No | JSON array of paid tool definitions to expose as MCP tools | [] |
| AGENTICPAY_BRIDGE_KEYPAIR | Yes | 64-byte JSON array — Solana keypair the bridge uses to sign x402 payments | |
| AGENTICPAY_BRIDGE_NETWORK | No | CAIP-2 network identifier (default: Solana devnet) | solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 |
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 |
|---|---|
| agenticpay_infoB | Placeholder tool for Glama introspection handshake. |
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 1 tool
Only one tool exists, so there is no ambiguity between tools.
With a single tool, naming is trivially consistent; the name uses a clear verb_noun pattern.
One placeholder tool is far too few for a server named 'agenticpay', which implies a payment domain requiring multiple operations.
The server lacks any functional tools; a payment server should have tools for transactions, balances, etc., but there is only a placeholder.