RequestBin MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REQUESTBIN_API_KEY | Yes | Your API key from requestbin.net/api-keys | |
| REQUESTBIN_BASE_URL | No | Custom API base URL (for self-hosted instances) | https://requestbin.net |
| REQUESTBIN_MOCK_DOMAIN | No | Domain that hosts mock endpoints (override for self-hosted) | rbmock.dev |
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 |
|---|---|
| list_binsA | List all your webhook bins with their URLs and stats |
| create_binA | Create a new webhook bin to capture HTTP requests. Returns the bin URL you can use as a webhook endpoint. |
| get_binA | Get details of a specific bin including recent interactions |
| delete_binB | Delete a webhook bin (soft delete) |
| list_interactionsA | List captured HTTP requests (interactions) for a bin |
| replay_requestB | Send an HTTP request to any URL (replay/test webhook delivery). The request is executed server-side. |
| get_replay_statusB | Check the status of a replay job |
| list_serversA | List available servers (needed for creating bins). Returns server IDs you can use with create_bin. |
| list_mock_endpointsA | List your mock API endpoints (custom HTTP responses at {slug}.rbmock.dev). Useful for finding endpoint IDs and current rule counts. |
| create_mock_endpointA | Create a mock API endpoint. Returns a live URL ({slug}.rbmock.dev) that responds to HTTP requests with rules you configure. A starter rule (any-method any-path → 200 JSON) is added automatically. Custom slugs require PRO/TEAM; otherwise an auto-slug is generated. |
| add_mock_ruleA | Append a routing rule to a mock endpoint. Rules are matched in priority order; the first match wins. After adding rules, call deploy_mock to publish them. |
| deploy_mockA | Publish the current rule set of a mock endpoint to the live mock server. Bumps the configVersion and invalidates edge caches so new requests see the latest rules. |
| list_mock_capturesA | List recent captured requests that hit a mock endpoint. Use this to verify your integration is actually calling the mock URL — shows method, path, status, and time for each capture. Returns up to 50 by default. |
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 13 tools
Tools clearly separate bin and mock endpoint domains, but some overlap exists between list_interactions and list_mock_captures; descriptions help distinguish them.
All tool names follow a consistent verb_noun pattern with snake_case, e.g., create_bin, list_mock_endpoints, replay_request.
13 tools is well-scoped for managing webhook bins and mock endpoints, covering creation, listing, rules, and replay without being excessive.
Core workflows are present, but notable gaps exist: no delete_mock_endpoint, no update/remove rule operations, and mock endpoint details are limited to listing.