SAP MultiHopper Mandate Vault 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sap_derive_hierarchyC | Derives deterministic OOBE SAP v2, MultiHopper Core/Orchestrator, and SAP Mandate Vault PDAs. |
| mandate_evaluate_and_encodeC | Evaluates Steve Capital >=20 USDC gate, rolling 24h cap, anti-wash rules, and encodes the Anchor authorize_multihopper_route instruction. |
| multihopper_quote_fee_splitB | Computes exact BigInt 0.50% MultiHopper fee and 0.25% atomic integrator revenue share wired to 32647Bri8KhJQE11x26iF7fpae9nouCJSZ8Y2VPpq5yM. |
| multihopper_verify_webhookC | Verifies x-multihopper-signature HMAC-SHA256 webhook payload in constant time. |
| solana_verify_mainnet_programsC | Verifies live Solana Mainnet-Beta executable status of OOBE SAP v2 and MultiHopper programs. |
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 targets a clearly different operation: PDA derivation, mandate policy evaluation plus instruction encoding, fee-split BigInt math, HMAC webhook verification, and on-chain program status checks. The only mild overlap is between sap_derive_hierarchy and solana_verify_mainnet_programs, which both touch on-chain program/PDA state, but their purposes remain distinct.
All names are snake_case and follow a subsystem-prefix + verb_noun pattern (sap_derive_hierarchy, mandate_evaluate_and_encode, multihopper_quote_fee_split, multihopper_verify_webhook, solana_verify_mainnet_programs). The prefixes vary by subsystem (sap_/mandate_/multihopper_/solana_), which is readable but slightly less uniform than a single global verb_noun convention.
Five tools is well-scoped for a narrow, specialized mandate-vault/fee-quoting workflow. Each tool covers a distinct piece of the pipeline (derive, evaluate/encode, quote, verify webhook, verify programs) with no filler.
The surface covers derivation, policy evaluation/encoding, fee quoting, and two verification paths, but there is no read/query tool for mandate state, rolling 24h usage, or existing routes, and no way to sign/dispatch or check the status of an encoded instruction. Agents can work around some of this off-chain, but key lifecycle steps are missing.