Skip to main content
Glama

Server Details

Simceptor is an AI-native Mock API simulation platform with a built-in MCP server. It enables AI agents to create, inspect, update, and test dynamic mock APIs, conditional response rules, stateful session simulations, and network latency directly from context.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2024-11-05
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 39 tools

Disambiguation3/5

Several tool pairs have near-identical scope: get_mock_detail and get_mock_by_slug both fetch a full mock by slugId, list_issues and list_open_issues_for_mock both enumerate issues, and debug_last_request overlaps heavily with get_request_logs. Long usage guidelines do steer the agent (e.g. add_mock_rule vs update_mock vs remove_mock_rule), but the retrieval/issue/inspection tools still have fuzzy boundaries.

Naming Consistency5/5

Every tool follows a consistent snake_case verb_noun pattern (create_mock, list_projects, set_traffic_chaos, resolve_issue, export_project). Verb families (get/list/create/update/delete/set/clear) map predictably onto resource nouns, with no camelCase or style mixing.

Tool Count2/5

39 tools is heavy for a single server, and the surface spans many sub-domains (projects, mocks, rules, chaos, state, issues, playground, export/import, debug). While the breadth is real, several tools are narrow variants of others, so the count exceeds what the core workflow needs.

Completeness4/5

Coverage is broad: full project/mock/rule CRUD, state get/set/delete, chaos status/set/clear for both rule and traffic, issue listing/comment/resolve, saved requests, export/import, test and debug. Minor gaps exist—no way to create or delete labels or saved requests, and no issue-creation tool—but agents can work around these.

Publisher details

Operator
Not available
Vendor relationship
Not available
Privacy policy
Not provided
Trust center
Not available
Restrictions
Simceptor · Publisher source

Available Tools

39 tools
add_issue_commentAInspect

Post a new comment to a review issue thread (marked as AI-generated). Returns the created comment object. USAGE GUIDELINE: Whenever you finish updating a mock or rule to address an open issue, you MUST call add_issue_comment on that issueSlugId to explain what was changed and how you verified it (e.g. via test_mock), then ask the user to review and resolve the issue.

Inputs: content (required), issueSlugId (required).

add_mock_ruleAInspect

Append a single new conditional response rule to an existing mock API endpoint without replacing or resending its existing rules array. Returns the full updated mock object (including the newly created rule's assigned database 'id' and 'slugId', the complete 'rules' array, and 'responseBodyWarning' if the rule's JSON responseBody looks malformed). USAGE GUIDELINES: Prefer add_mock_rule over update_mock whenever adding a new scenario to an existing mock — it is much more token-efficient and avoids accidentally overwriting existing rules or reassigning their rule IDs. Before calling, inspect existing rule priorities via get_mock_detail so you can set the new rule's 'priority' integer appropriately (rules are evaluated in ascending priority order; first match wins). After adding the rule, call test_mock with a matching request payload and verify the 'X-Rule-Matched' response header.

Inputs: rule (required), mockId (required), projectId (required).

bulk_create_mocksAInspect

Create multiple mock API endpoints in a single atomic batch request under a project workspace. Automatically creates any referenced 'collectionName' folders that do not yet exist. Returns a JSON array of all created mock objects, each populated with its database 'id', 'slugId', ready-to-use public 'mockUrl', and nested 'rules' (plus a 'responseBodyWarning' field on any mock whose JSON responseBody looks structurally malformed). USAGE GUIDELINES: Prefer bulk_create_mocks over repeated create_mock calls whenever scaffolding 2 or more endpoints (e.g., setting up an entire service contract or multi-step stateful workflow). Before calling, run search_mocks or list_mocks to avoid creating duplicate method+path endpoints. After creation, verify key scenarios using test_mock.

Inputs: mocks (required), projectId (required).

check_relay_statusAInspect

Check if the user currently has an active Local Webhook Relay session (WebSocket tunnel) running. ALWAYS call this tool before setting webhookUrl on any mock if the user is working locally or might want local delivery. If active is true, you can use the 'simceptor://local/' URL scheme to deliver webhooks directly to their local server. If active is false: NEVER generate or read the required Personal Access Token yourself — it must come from the user, who generates it from their dashboard ('Developer Keys', with the 'Local Webhook Relayer' scope). Once they share that token with you, how you proceed depends on whether you have direct local shell/terminal execution access on the SAME machine the user is developing on (e.g. Claude Code): if you do, you may run npx @simceptor/cli listen --token <PAT> --to http://localhost:<port> yourself — but first tell the user this opens a persistent background network tunnel from Simceptor's cloud to their machine, and how to stop it (the process can simply be killed) when they're done. If you do NOT have local shell access (e.g. a hosted/remote connector like the claude.ai web app), you cannot run this on the user's machine at all — instruct them to run the command in their own terminal instead, then call this tool again to confirm the session shows active.

Inputs: no named parameters.

clear_rule_chaosAInspect

Remove Rule-level Chaos from a specific conditional rule. After calling this, the rule will always fire its normal response when conditions match (no more probabilistic behavior).

Inputs: mockId (required), ruleId (required), projectId (required).

clear_traffic_chaosAInspect

Disable and completely remove the Global Traffic Chaos configuration from a mock API. After calling this, all requests will be served normally through the standard rule evaluation pipeline.

Inputs: mockId (required), projectId (required).

create_mockAInspect

Create a new mock API endpoint in a project. IMPORTANT: Always use the 'rules' field to set up conditional response logic (the Rule Engine). The Rule Engine allows ONE mock endpoint to return DIFFERENT responses based on request content — this is the primary way to simulate multiple scenarios (success, error, validation failure, auth failure, etc.) without creating separate mocks. Rules are evaluated in ascending 'priority' order; the FIRST rule whose conditions match wins. If NO rule matches, the mock's top-level responseBody/responseStatus is used as the default fallback. Use the 'stateLookupExpr' and 'stateCaptureExpr' fields to enable stateful simulation (e.g., simulate a database that persists data across calls). If collectionName is provided but doesn't exist, it will be auto-created.

Inputs: name (required), path (required), method (required), projectId (required), +18 more.

create_projectAInspect

Create a new project workspace for organizing and mocking API endpoints. Each project gets a unique slug used to route requests through the mock engine at: https://api.simceptor.com/mock/{slug}/{path}. Don't reconstruct this URL by hand for a specific mock — every create_mock/update_mock/get_mock_detail/list_mocks/get_mock_by_slug response includes a ready-to-use mockUrl field with the real, complete public URL for that mock.

Inputs: name (required), userNotes, description.

debug_last_requestAInspect

Inspect the most recent captured HTTP request log for a mock endpoint and generate a step-by-step Rule Engine diagnostic trace in Markdown. The trace displays the incoming request's method, path, timestamp, headers, body, final HTTP status code, matched outcome (Rule '' or Fallback), and an ordered evaluation breakdown of every rule configured on the mock (sorted by ascending priority) showing each rule's conditions, join operators, and whether it fired ('[MATCHED]') or was skipped/failed ('[DID NOT MATCH]'). If no request logs exist for the mock yet, returns an informational prompt to send a request via test_mock first. USAGE GUIDELINES: Call debug_last_request immediately when test_mock returns an unexpected status code, when the 'X-Rule-Matched' header is missing or shows the wrong rule, or when diagnosing why an incoming request fell back to the default response. To inspect multiple historical requests rather than just the latest one, use get_request_logs.

Inputs: mockId (required), projectId (required).

delete_mockAInspect

Permanently delete a single mock API endpoint from a project workspace, including all of its conditional response rules, chaos configuration, and captured request logs. WARNING: This action is irreversible. If you only want to remove a single rule scenario from the mock, use remove_mock_rule instead.

Inputs: mockId (required), projectId (required).

delete_projectAInspect

Permanently delete an entire project workspace, including all its collections, mock API endpoints, conditional rules, stateful Redis data, and captured request logs. WARNING: This action is irreversible. Before deleting, consider calling export_project if a backup of the project configuration might be needed.

Inputs: projectId (required).

delete_stateAInspect

Delete and clear a specific stateful session entry from Redis for a project workspace. Use this tool to reset a stateful test flow back to a clean initial state (e.g. before re-running a multi-step registration or payment scenario) without waiting for the 15-minute Redis TTL to expire.

Inputs: sessionKey (required), projectSlug (required).

export_projectAInspect

Export an entire project workspace configuration (project metadata, collections, mock endpoints, webhooks, stateful config, and rules) as a portable, ID-stripped JSON document. Use this tool to create backups before destructive changes or to clone/migrate a project workspace via import_project.

Inputs: projectId (required).

get_issueAInspect

Retrieve the full details of a specific review issue by its issueSlugId (e.g. 'ISS-xxxxxx'), including title, description, status, targetSlugId, and comment thread. Set includeComments: false for a token-efficient summary when you only need the issue metadata.

Inputs: issueSlugId (required), includeComments.

get_mock_by_slugAInspect

Retrieve the complete configuration of a single mock API endpoint directly by its unique slugId (e.g. 'MOCK-5cbb91d3') without needing projectId or mockId. Returns the full mock object including default response, headers, rules array (with each rule's id and slugId), stateful expressions, webhook config, and ready-to-use mockUrl. Use this when the user shares a MOCK-xxxxxxxx badge from the Simceptor UI.

Inputs: slugId (required).

get_mock_detailBInspect

Get the full detail of a single mock API endpoint, including all its rules, stateful configuration, webhook settings, slugId, and description. PREFERRED: provide slugId (e.g. 'MOCK-5cbb91d3') without needing projectId/mockId.

Inputs: mockId, slugId, projectId.

get_project_contextAInspect

Retrieve the active project workspace context briefing for the authenticated user, including project metadata, pinned AI Context Notes (userNotes), and workspace summary. Call this at the start of a session to understand the active project's conventions and notes.

Inputs: no named parameters.

get_request_logsAInspect

Retrieve recent incoming HTTP requests captured by a mock endpoint. Each log entry shows: request headers, body, query params, matched rule label, response status returned, and response time. Use this to: (1) debug why a rule did or didn't match, (2) inspect the actual request payload structure your service sends, (3) verify the correct rule scenario was triggered. The 'matchedRuleLabel' field tells you which rule fired for each request.

Inputs: mockId (required), size, status, ruleLabel.

get_rule_chaos_statusAInspect

Read the current Rule-level Chaos configuration for a specific rule, without needing to fetch the whole mock via get_mock_detail. Token-efficient counterpart to get_traffic_chaos_status. Call this instead of get_mock_detail when you just need to check one rule's chaosConfig.

Inputs: mockId (required), ruleId (required), projectId (required).

get_saved_requestsAInspect

Retrieve saved request samples from the Playground. The Playground allows developers to save example request bodies, headers, and descriptions for specific mock endpoints. Use this tool to discover what request payloads are expected by a mock, read field names and data structures, and understand the different scenarios that have been documented. This is very useful to: (1) know what JSON fields to reference in rule conditions, (2) understand what test cases exist for a mock, (3) use saved request bodies when calling test_mock to verify rule behavior. Each saved request includes: name, method, URL, request headers, body, description, and associated mock/collection/project names.

Inputs: no named parameters.

get_simulator_specAInspect

Retrieve the complete reference specification for the Simceptor simulator, including: all dynamic expression placeholders (request extractors, random/UUID/date generators, multi-locale faker keys, environment/state variables, '__repeat' array loops, and Handlebars helpers), all rule condition field prefixes and comparison operators, Rule Engine evaluation order, stateful session simulation guide, outbound webhook capabilities, Local Webhook Relay setup, and standard response headers. ALWAYS call this tool first when setting up mocks for a new task to understand all supported syntax and features.

Inputs: no named parameters.

get_stateAInspect

Inspect the current stateful session data stored in Redis for a specific project and sessionKey. Returns the full JSON state object containing 'request' (last captured request snapshot), 'response' (last captured response snapshot), and any custom variables saved via stateCaptureVariables or set_state. Use this tool after firing test_mock on a stateful endpoint (or after calling set_state) to verify that stateCaptureExpr and stateCaptureVariables saved the expected values before testing downstream mocks that rely on stateLookupExpr.

Inputs: sessionKey (required), projectSlug (required).

get_traffic_chaos_statusAInspect

Read the current Global Traffic Chaos configuration for a specific mock API. Returns whether chaos is enabled, the distribution mode (probabilistic or exact round-robin), the list of traffic targets (drop/error/rule/default) with their percentages, and the error status code. Call this before set_traffic_chaos to understand the current state.

Inputs: mockId (required), projectId (required).

import_projectAInspect

Import a portable project configuration JSON string (previously produced by export_project) to create a new project workspace and bulk-populate all of its collections, mock endpoints, and conditional rules. Returns the newly created project details including its assigned projectId and slug.

Inputs: data (required), name, description.

list_issuesAInspect

List review issues reported against a specific mock endpoint or rule target. Provide either 'targetSlugId' (to filter issues for one specific MOCK-xxxxxx or RULE-xxxxxx badge) or 'mockId' (to retrieve all issues across the mock and all of its rules). Returns an array of issue objects including issue slugId (e.g. 'ISS-xxxxxx'), title, description, status ('OPEN' or 'RESOLVED'), and targetSlugId.

Inputs: mockId, targetSlugId.

list_labelsAInspect

List all available labels (tags) created by the authenticated user across scopes: PROJECT, COLLECTION, MOCK, RULE. Returns an array of label objects with id, name, color, and type. Use this to discover existing tag names before filtering with list_mocks or tagging mocks in create_mock/update_mock.

Inputs: type.

list_mocksBInspect

List all mock API endpoints in a project, organized by collections. Returns each mock's ID, name, method, path, response config, its rules, and slugId. Set slim: true for a token-efficient response containing only basic details.

Inputs: projectId (required), path, slim, label, +1 more.

list_open_issues_for_mockAInspect

List all currently OPEN (unresolved) review issues across an entire mock endpoint, including issues attached to its default response and any of its conditional rules. Filters out resolved issues automatically for token efficiency. Use this when auditing a mock for pending human review feedback that needs to be fixed.

Inputs: mockId (required).

list_projectsAInspect

List all active mock API projects belonging to the authenticated developer. Returns project IDs, names, and slugs. The slug is used when calling test_mock to hit the engine.

Inputs: no named parameters.

remove_mock_ruleAInspect

Remove a single conditional rule from an existing mock API endpoint by its rule ID, without needing to resend the full rules array. Returns the full updated mock object with the remaining rules. Token-efficient counterpart to add_mock_rule — use this instead of update_mock when deleting one rule so other rules keep their existing database IDs and slugIds. Obtain the target ruleId from get_mock_detail.

Inputs: mockId (required), ruleId (required), projectId (required).

resolve_issueAInspect

Mark a review issue's status as RESOLVED. IMPORTANT RESTRICTION: Do NOT call this tool automatically after fixing an issue. Only the human user is allowed to approve and resolve issues (or explicitly instruct you to call resolve_issue). Instead, post your fix summary using add_issue_comment and recommend that the user resolve the issue.

Inputs: issueSlugId (required).

save_requestAInspect

Save a reusable sample HTTP request payload (method, path, headers, body, and scenario description) to the Simceptor Playground. Returns the created saved-request object. Call this after verifying a mock scenario with test_mock so developers and future AI sessions can discover and replay the exact test payload via get_saved_requests or the Playground UI.

Inputs: url (required), name (required), method (required), body, +6 more.

search_mocksAInspect

Search mock APIs across all of the authenticated user's projects by keyword, tags, or HTTP method. Use this BEFORE creating new mocks to avoid duplicates. Results are scoped to the token owner's projects only.

Inputs: tags, query, method.

set_rule_chaosAInspect

Configure Rule-level Chaos for a specific conditional rule inside a mock. Unlike Global Traffic Chaos (which intercepts all requests), Rule-level Chaos only activates when the rule's conditions have already matched. For example: rule matches 'name=agung', then 30% chance the connection is killed instead of returning the rule's normal response. Supports two modes: 'probability' (random per-request) and 'sequential_fail' (fail first N requests, then pass, cycling).

Inputs: mode (required), mockId (required), ruleId (required), behavior (required), +4 more.

set_stateAInspect

Directly write/overwrite session state in Redis for a project, without needing to fire a real request through stateCaptureExpr first. Useful for forcing a stateful test scenario into a specific state (e.g. jump straight to 'settled' or 'completed') without building fake helper mock endpoints. Merges with (does not replace) any existing variables already saved under the same sessionKey — pass only the fields you want to add or overwrite.

Inputs: variables (required), sessionKey (required), projectSlug (required), ttlMinutes.

set_traffic_chaosAInspect

Configure Global Traffic Chaos for a mock API. This enables probabilistic or exact round-robin traffic distribution across multiple outcome channels: 'drop' (kills TCP connection — client gets connection reset), 'error' (returns HTTP error status), 'rule' (routes traffic to a specific conditional rule), and 'default' (serves the normal mock response). IMPORTANT: The 'rate' of all targets MUST add up to exactly 100. If they do not, this tool will return an error. For 'rule' type targets, obtain the ruleId by calling get_mock_detail first. Chaos is evaluated BEFORE any rule conditions — if a request is dropped, it never reaches rule logic.

Inputs: mockId (required), enabled (required), targets (required), projectId (required), +3 more.

test_mockAInspect

Fire a real HTTP request to the local mock engine to verify a mock endpoint returns the expected response. Use this AFTER creating or updating a mock to self-verify correctness. Test EACH rule scenario by sending different request bodies/headers that should match each rule. Check the 'X-Rule-Matched' response header to confirm which rule fired. If the wrong rule fires or no rule fires, use get_request_logs to debug the condition mismatch. You can also use bodies from get_saved_requests as test inputs.

Inputs: path (required), method (required), projectSlug (required), body, +1 more.

update_mockAInspect

Update an existing mock API endpoint. Replaces all fields including rules. IMPORTANT: When updating rules, you MUST provide the full updated rules array — partial updates are not supported. Use get_mock_detail first to read the current state before modifying. This also supports adding/removing stateful simulation fields (stateLookupExpr, stateCaptureExpr, stateCaptureVariables).

Inputs: name (required), path (required), method (required), mockId (required), +20 more.

update_project_notesAInspect

Update or overwrite the AI Context Notes pinned on a project workspace's dashboard banner. Returns the updated project object. Use this tool to persist architectural notes, API contract references, test session keys, or helper endpoint conventions so future AI sessions and human teammates have immediate project context (retrievable via get_project_context or list_projects).

Inputs: projectId (required), userNotes (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources