l402-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUDIT_LOG_PATH | No | Path to audit log file (NDJSON, append-only). Default: ./l402-search-mcp-audit.log | ./l402-search-mcp-audit.log |
| HTTP_TIMEOUT_MS | No | HTTP timeout in milliseconds. Default: 15000 | 15000 |
| SEARCH_SERVICE_URL | No | URL of the L402 search endpoint. Default: https://llmops-search.fly.dev | https://llmops-search.fly.dev |
| CHALLENGE_TTL_SECONDS | No | Time-to-live for challenges in seconds. Default: 900 | 900 |
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 |
|---|---|
| searchA | No-KYC web search, paid per query in Lightning sats (L402). Call with just |
| search_service_infoA | Free: status of the configured L402 search endpoint — reachability, price, and how the payment flow works. |
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 2 tools
The two tools have clearly distinct purposes: 'search' performs a paid query, while 'search_service_info' provides free metadata about the service. There is no overlap in functionality.
Both tools start with 'search', but one is a single verb while the other is a compound noun. The pattern is mostly consistent, though not fully uniform.
With only 2 tools, the surface is minimal. For the niche L402 search domain, it may be sufficient, but it feels slightly thin compared to typical integration scopes.
The set covers the core workflow: check service status and perform a paid search. However, missing features like invoice management or search history create minor gaps for advanced use cases.