Skip to main content
Glama
Whambammy

Agent Resilience & Networking MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BASE_RPC_URLYesBase L2 RPC URL, e.g., https://mainnet.base.org.
PAYMENT_WALLETYesRecipient payout wallet address for x402 Base L2 USDC payments.

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
temporal_event_stream_deduplicatorB

Sliding-window Bloom filter and event deduplicator for high-throughput streaming agent logs, eliminating duplicate messages with zero disk I/O. (0.030 USDC on Base L2)

resilient_http_probeB

Robust HTTP/S request engine with exponential backoff, jittered retries, smart timeout isolation, and header anti-bot rotation. (0.01 USDC on Base L2)

streaming_jsonlines_validatorB

Streams gigabyte-scale JSON Lines (JSONL) datasets, auto-repairing truncated strings, unescaped newlines, trailing commas, and encoding glitches. (0.025 USDC on Base L2)

stealth_tls_fingerprint_mimicB

Synthesizes JA3 and JA4 TLS Client Hello fingerprint configurations matching genuine Google Chrome and Apple Safari builds, preventing bot blocking. (0.045 USDC on Base L2)

resilient_cookie_jar_session_syncB

RFC-6265 compliant cookie jar engine managing cross-domain session tokens, SameSite policies, expiration schedules, and proxy synchronization. (0.030 USDC on Base L2)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a distinct networking/resilience concern: cookie/session management, event deduplication, HTTP request execution, JSONL validation, and TLS fingerprint mimicry. The only minor overlap is between the HTTP probe and TLS mimicry, both anti-bot related, but they operate at different layers.

Naming Consistency4/5

All names use snake_case and are descriptive compound nouns, but there is no consistent verb_noun action pattern; prefixes vary (resilient_, temporal_, streaming_, stealth_). Still, the convention is consistent enough to be readable.

Tool Count5/5

Five tools is well-scoped for a focused resilience and networking toolkit, covering distinct capabilities without redundancy.

Completeness4/5

The set covers key resilience primitives (session sync, deduplication, HTTP retries, data validation, TLS mimicry), but lacks tools for proxy management, rate limiting, or circuit breaking that might be expected in a broader resilience toolkit. Agents can work around by composing existing tools.

Maintenance

ActivityMaintained
ResponsivenessNo issues