website-intelligence-provider
by CaBsCrypto
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The server binds to 127.0.0.1:8787 by default. Set PORT to override it. | 8787 |
| X402_STELLAR_PAY_TO | No | Must be a valid Stellar G- or C-address controlled by the Testnet recipient and able to receive the configured USDC asset. | |
| X402_PUBLIC_BASE_URL | No | Must be an explicit canonical HTTPS origin and must also appear exactly in X402_ALLOWED_PUBLIC_BASE_URLS. Localhost, HTTP, credentials, paths, queries and fragments fail closed. | |
| X402_SETTLEMENT_ENABLED | No | Settlement is disabled by default. Keep false while running tests. Change to true only for an explicitly authorized Testnet settlement run. | false |
| STELLAR_X402_FACILITATOR_URL | No | The URL of the Stellar x402 facilitator. The default is OpenZeppelin Channels for Stellar Testnet. | https://channels.openzeppelin.com/x402/testnet |
| X402_ALLOWED_PUBLIC_BASE_URLS | No | Must contain the exact X402_PUBLIC_BASE_URL. Localhost, HTTP, credentials, paths, queries and fragments fail closed. | |
| STELLAR_X402_FACILITATOR_API_KEY | No | Server-only secret for the facilitator's supported, verify, and settle calls. The API key must remain only in ignored local environment configuration. | |
| X402_MANUAL_SINGLE_PROCESS_TESTNET | No | true only for an explicitly authorized local Testnet E2E in one controlled Node process. It never enables a Vercel/Lambda runtime. | false |
| WEBSITE_INTELLIGENCE_REDIS_REST_URL | No | Required for a Vercel/multi-instance runtime. Upstash-compatible Redis REST store URL. | |
| WEBSITE_INTELLIGENCE_REDIS_REST_TOKEN | No | Required for a Vercel/multi-instance runtime. Upstash-compatible Redis REST store token. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CaBsCrypto/website-intelligence-provider'
If you have feedback or need assistance with the MCP directory API, please join our Discord server