specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Fiddler
providerId: fiddler
generated: '2026-08-29'
method: searched
source: https://www.telerik.com/fiddler/fiddler-everywhere/documentation/agent-tools/fiddler-mcp-server
created: '2026-05-04'
modified: '2026-08-29'
tags:
  - API Debugging
  - HTTP Debugging
  - Rate Limiting
description: >-
  Honest zero. Fiddler publishes NO rate limits, quotas, throttling windows or
  rate-limit response headers for any of its interfaces. REPLACES a 2026-05-04
  bulk-sweep scaffold that asserted an X-RateLimit-* header family, a 429
  throttling response and per-tier requests-per-minute figures — none of which
  Progress Telerik has ever published. Those values were invented by the sweep,
  not read from the provider.
limits: []
limit_count: 0
headers: {}
responseCodes: {}
searched:
  - url: https://www.telerik.com/fiddler/fiddler-everywhere/documentation/agent-tools/fiddler-mcp-server
    status: 200
    finding: >-
      The MCP server reference documents authentication, tools, sanitization and
      an admin kill switch. No request quota, throttle, window or rate-limit
      header is documented.
  - url: https://www.telerik.com/purchase/fiddler
    status: 200
    finding: >-
      Plans are priced per named user per month with "unlimited capturing
      capabilities" on every tier. Nothing is metered by request, so there is no
      rate-limit surface to publish.
note: >-
  Structural reason for the zero: Fiddler's only programmatic interface is a
  loopback MCP server bound to the developer's own machine
  (http://localhost:8868/mcp). There is no shared multi-tenant endpoint to
  protect, so the absence of published limits is expected rather than a gap.
  Gating is by LICENCE (Pro or higher) and by an administrator DisableMCP policy,
  not by throughput.