Item logo image for Mockarty Capture

Mockarty Capture

ExtensionDeveloper Tools
Item media 5 (screenshot) for Mockarty Capture
Item media 1 (screenshot) for Mockarty Capture
Item media 2 (screenshot) for Mockarty Capture
Item media 3 (screenshot) for Mockarty Capture
Item media 4 (screenshot) for Mockarty Capture
Item media 5 (screenshot) for Mockarty Capture
Item media 1 (screenshot) for Mockarty Capture
Item media 1 (screenshot) for Mockarty Capture
Item media 2 (screenshot) for Mockarty Capture
Item media 3 (screenshot) for Mockarty Capture
Item media 4 (screenshot) for Mockarty Capture
Item media 5 (screenshot) for Mockarty Capture

Overview

Capture, mock & intercept browser traffic: breakpoints, chaos, macros, replay — your in-browser Mockarty testing assistant.

Mockarty Capture is your in-browser API testing toolkit — inspect real traffic, mock it, break it, and automate it, all from a side panel next to the page you're testing. CAPTURE Start a session and the extension records every HTTP/HTTPS request the page makes — method, URL, headers, request and response bodies. Search and filter the live feed, copy any request as cURL, or export the whole session to a Postman collection, a HAR file, or Mockarty mocks. MOCK & INTERCEPT Turn any request into a canned response without touching your backend. Return custom status codes, headers and bodies; map a URL to a local response (Map-Local); rewrite or redirect requests; add or strip headers. Static rules run banner-free; advanced rules use Chrome's debugger to rewrite bodies on the fly. BREAKPOINTS Pause a request or response mid-flight, inspect it, edit it, then resume — like DevTools breakpoints, but for the network. CHAOS & THROTTLING Test how your app behaves under stress: inject latency, errors, timeouts, truncated or malformed responses, and slow streams. Apply 3G/4G throttle presets to emulate poor networks. TEMPLATED MOCKS Generate dynamic responses with Faker-style helpers and request-aware placeholders ({{uuid}}, {{request.query.id}}, fake names/emails/dates) so every call returns fresh, realistic data. MACROS — RECORD & REPLAY Click through a flow once, then replay it automatically on the page — a lightweight way to repeat a manual test run hands-free. Replay survives navigation. GRAPHQL-AWARE Match rules by GraphQL operation name — robustly handles batched queries, GET GraphQL, raw documents and comments. Operation names autocomplete from your captured traffic. COLLECTIONS, PROFILES & SHARING Organise rules into groups, save and switch profiles/environments, master-switch everything on or off, and share a rule set as a URL. AI AGENT THAT CAN ACT ON THE PAGE Ask the Mockarty agent to mock the request that just failed, explain what a page is doing, or write a test case for what is in front of you. It streams its answer as it works and shows which tools it is running. Switch on "Read the page" and it takes a structural snapshot of the tab you are on — headings, form fields with their labels, buttons, links — so it reasons about the real page instead of guessing from the address, and it works behind a login because it runs in your own session. Field VALUES are never read. Its answers do something: a rule it proposes is applied to THIS browser (a mock created inside Mockarty would not affect your page), and steps it proposes replay in the tab you are on, after you confirm. Anything unsafe — a pattern that would intercept every request, a step the replay engine does not have — is refused with the reason shown. Request and response bodies are never sent, and credential-looking headers are masked. TEAM CHAT IN THE PANEL The discussions from your Mockarty workspace, next to the page you are testing: search across messages, reactions, replies, editing, pinning, folders, participants, typing indicators. Each conversation has its own notification level — everything, mentions only, or muted. Drag a file in or paste a screenshot straight from the clipboard. Meetings are scheduled from the panel and exported to your calendar, and an incoming call rings in the panel itself. SCORE THE PAGE YOU ARE ON Run a performance and accessibility audit natively, with no server: Web Vitals from the page's own timing data, plus the full axe-core rule set (the engine behind Lighthouse and pa11y, bundled with the extension — nothing is fetched at audit time) on top of our own contrast, tap-target and landmark checks. Every finding points at the element that caused it and links to how to fix it. Download the report as Markdown. BUILT FOR THE KEYBOARD Drive the captured-request list without a mouse: j/k to move, Enter to open, Space to select for mocking, Esc to close, / to filter. The shortcuts are printed above the list. WORKS WITH OR WITHOUT A SERVER Everything above the AI/chat sections runs fully client-side — no account needed. Connect your own Mockarty server (pairing or an API token) to stream captures into mocks and test cases, get a notification hub with deep links, chat with your team, drive the agent, and see your running tests — right in the panel. PRIVACY Capture and interception only run while you turn them on. Your data goes only to the Mockarty server you configure — never to the extension authors or any third party. A modern, open alternative to the Postman Interceptor.

Details

  • Version
    1.1.1
  • Updated
    August 8, 2026
  • Size
    907KiB
  • Languages
    2 languages
  • Developer
    Website
    Email
    orlovich.artem@gmail.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization

Mockarty Capture has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

Mockarty Capture handles the following:

Authentication information
Web history
User activity
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes
Google apps