MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.pathrule/pathrule

Path-scoped project memories, rules and skills for coding agents, on your machine or Pathrule Cloud. — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: developer-tools · AI-classifiedPricing: freemium · AI-classifiedversion 1.0.6TypeScriptApache-2.0standard input/output, streamable HTTP33 tools

Summary

io.pathrule/pathrule is a remote and local MCP server listed in the official MCP registry at version 1.0.6. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 33 tools, 0 resources and 0 prompts.

Record checks

9 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#11,172 of 15,112 packages by monthly downloads, tied with 42 others
Not ranked by stars: 4 stars (ranked from 10)
#1,023 of 1,074 packages meeting all 9 record checks, by downloads, tied with 1 other

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote and local package
Transport: standard input/output, streamable HTTP
Package: npm · listed version behind the latest release
License: Apache-2.0
Dependencies: no known high or critical advisories
Repository: public
Tools: 33
Described as changing data: 19 of 33 toolsAI-classified
Mainly works on: files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic: developer-toolsAI-classified
Pricing: freemiumAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

19 tools are described as changing something (pathrule_review_learning, pathrule_write_memory, pathrule_record_learning, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
The registry lists 1.0.6; 1.0.7 is newer (1 release).
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 1.0.6, published 2026-10-19 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-19 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.6 (published 2026-10-19).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

33tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

19 of 33 tools are described as changing something (creating, editing, deleting, sending or running).

pathrule_pingon 1 other serverreads or searches
“Sanity check that Pathrule's MCP server is wired up.”
1 input
- messagestring“Optional message to echo back.”
pathrule_get_contexton 1 other serverreads or searches
“Unified Pathrule context tool.”
11 inputs
- cwdstring“Absolute working directory.”
- user_intentstring“The user's most recent message verbatim (or a one-sentence summary if very long).”
- known_protocol_versionstring“ETag from a prior response — skips protocol retransmission.”
- known_overview_versionstring“ETag from a prior response — skips workspace_overview retransmission.”
- debugboolean“When true, include routing_latency_ms + routing_fallback + cwd echo in the response.”
- omit_protocolboolean“When true, server omits the protocol block regardless of ETag state.”
- activities_scopestring“Scope for recent_activities.”
- subtree_limitinteger“Budget for descendant memory title metadata on discovery-shaped calls.”
- session_idstring“The agent/hook session id for this turn.”
- known_item_versionsarray“`item_versions` from earlier responses in this conversation.”
- include_deliveredboolean“Send a preloaded memory body even when the Pathrule hook already delivered the same version in this session.”
pathrule_review_historyreads or searches
“Read bounded historical review evidence from this checkout's GitHub origin through the existing gh CLI login.”
4 inputs
- cwdstring“Bound local checkout; origin must point to github.com.”
- pull_numbersarray“Read up to three specific PRs.”
- pageinteger“Bounded discovery page; defaults to the most recently updated closed PRs.”
- include_seenboolean“Default false skips excerpts already cited in saved learning; verification receipts are refreshed either way.”
pathrule_review_learningreads or searchesdescribed as changing data
“Inspect current, stale and conflicting learning hypotheses, including the statements withheld from context.”
4 inputs, 1 required
- cwdstring
- node_pathstring
- actionstringrequired
- idstring
pathrule_get_treeon 1 other serverreads or searches
“Return the workspace node tree.”
3 inputs, 1 required
- workspace_idstringrequired“Workspace UUID.”
- root_pathstring“Scope to this subtree (workspace-relative, e.g.”
- depthinteger“Max levels below root_path (0 = only the root node itself).”
pathrule_get_nodeon 1 other serverreads or searches
“Return a single node plus the ids of every memory, rule, and skill attached to it.”
1 input, 1 required
- node_idstringrequired“Tree node UUID.”
pathrule_resolvereads or searches
“Cheaply map a memory TITLE or rule/skill NAME (the label you already see in the compiled knowledge / injected context) to its editing handle: `{ id, node_path, version_id }`.”
7 inputs, 1 required
- querystringrequired“The memory title or rule/skill name to resolve (exact, prefix, or substring).”
- kindstring“Restrict to one kind.”
- node_pathstring“Restrict to items attached at this workspace-relative path (e.g.”
- workspace_idstring“Workspace UUID.”
- cwdstring“Absolute working directory used to resolve the workspace when workspace_id is omitted.”
- limitinteger“Max matches to return (default 8).”
- include_bodyboolean“For a single unambiguous match, also return its full `content` (default true — the row is read for version_id anyway, so the body is free).”
pathrule_readreads or searches
“Read several memories/rules/skills in ONE call.”
3 inputs
- memory_idsarray“Memory UUIDs to read.”
- rule_idsarray“Rule UUIDs to read.”
- skill_idsarray“Skill UUIDs to read.”
pathrule_knowledge_mapon 1 other serverreads or searches
“Read-only map of this workspace's memories, rules and skills, grouped into regions by links and meaning.”
10 inputs, 2 required
- workspace_idstringrequired“Workspace UUID.”
- viewstringrequired“atlas: all regions; region: one region's page; related: neighbours of the given seeds.”
- region_idstring“Region (rg_) or sub-region (sr_) id from the atlas (view=region).”
- pageinteger“Region page (view=region).”
- purposestring“audit appends the audit checklist to region pages.”
- item_idsarray“Memory, rule or skill ids to start from (view=related).”
- titlesarray“Titles or names to start from (view=related).”
- filesarray“Workspace-relative file paths (view=related).”
- querystring“Free-text query to start from (view=related).”
- limitinteger“Max related entries (default 8).”
pathrule_list_memorieson 1 other serverreads or searches
“Return the MainMemory.md-style index (title + preview) for every memory under a node.”
1 input, 1 required
- node_idstringrequired“Tree node UUID.”
pathrule_read_memoryon 1 other serverreads or searches
“Return a single memory.”
2 inputs
- memory_idstring“Memory UUID.”
- idstring“Same as memory_id.”
pathrule_write_memoryon 1 other servercreates or changes datadescribed as changing data
“Create a memory at a workspace path (missing nodes auto-create).”
9 inputs, 3 required
- workspace_idstring“The workspace UUID from pathrule_get_context or the UserPromptSubmit hook metadata.”
- cwdstring“Absolute working directory, used to resolve the workspace when `workspace_id` is omitted.”
- node_pathstringrequired“Workspace-relative path like '/apps/mobile' or '/src/components/Button.tsx'.”
- titlestringrequired“Short memory title.”
- contentstringrequired“Memory body (markdown).”
- verboseboolean“Set to true to receive the full memory row in the response.”
- allow_duplicateboolean“When omitted/false, the write is rejected with code 'duplicate' if a memory with the same normalised title already exists at this node.”
- related_pathsarray or null“Optional list of workspace-relative paths this memory is also relevant to (e.g.”
- atomsarray“Optional typed knowledge, every string copied VERBATIM from content: remedy{condition,action}, selection{prefer,over}, procedure{operation,steps}, context{fact…”

Show 21 more tools

pathrule_record_learningcreates or changes datadescribed as changing data
“Save a source-backed project synthesis in Pathrule's separate advisory learning layer.”
8 inputs, 5 required
- cwdstring“Directory inside the checkout whose sources you read.”
- node_pathstringrequired“Specific workspace-relative scope, starting with /; no glob.”
- replaces_idstring“Claim to correct atomically.”
- topicstringrequired“Stable name for the architectural topic; reuse it for revisions.”
- statementstringrequired“Concise synthesis in your own words.”
- categorystringrequired
- review_sourcesarray“Exact source references from pathrule_review_history.”
- sourcesarrayrequired
pathrule_remember_preferencecreates or changes datadescribed as changing data
“Remember how the USER prefers to work (style, process, communication), as opposed to a project decision (use write_memory for those).”
9 inputs, 3 required
- workspace_idstring“Workspace UUID, or pass cwd.”
- cwdstring“Absolute working directory, to resolve the workspace.”
- kindstringrequired“selection = prefers A over B; procedure = how they like work done in steps; context = a fact about how they work.”
- claimstringrequired“The preference in one sentence, for the next agent.”
- quotesarrayrequired“Verbatim spans of the user's own words.”
- whenarray“Verbatim spans naming a NARROWER kind of work it applies to ("for database migrations").”
- alwaysboolean“true when the user says it holds for all the work they ask for ("for any code you write for me", "always").”
- lastingboolean“true when the user stated it as a lasting way of working ("a habit of mine", "from now on"), not a remark about this task: it then applies in this workspace at…”
- same_asstring“Id of a stored candidate this repeats.”
pathrule_update_memoryon 1 other servercreates or changes datadescribed as changing data
“Update an existing memory, OR restore a soft-deleted one.”
13 inputs, 1 required
- memory_idstringrequired“Memory UUID.”
- contentstring“New memory body (markdown), full replacement.”
- content_editobject“Surgical edit applied to the CURRENT body server-side — send only the delta instead of the whole content.”
- restoreboolean“Restore a soft-deleted memory (sets deleted_at = null).”
- titlestring“New title.”
- expected_version_idstring“Optimistic concurrency token from a prior read.”
- move_to_pathstring“Optional — workspace-relative target path (e.g.”
- refresh_idstring“Pathrule refresh task UUID from pathrule_get_refresh_brief — when set, this update auto-resolves that task (status='applied').”
- refresh_notestring“Optional short note paired with refresh_id, stored with the resolved refresh task.”
- verboseboolean“Set to true to receive the full updated memory in the response.”
- allow_duplicateboolean“When omitted/false, a title rename or move that would collide with an existing memory's normalised title is rejected with code 'duplicate'.”
- related_pathsarray or null“Optional list of workspace-relative paths this memory is also relevant to (secondary links; the memory stays at its own path).”
- atomsarray“Optional typed knowledge, every string copied VERBATIM from content: remedy{condition,action}, selection{prefer,over}, procedure{operation,steps}, context{fact…”
pathrule_delete_memoryon 1 other serverdeletesdescribed as changing data
“Soft-delete a memory by id.”
3 inputs, 1 required
- memory_idstringrequired“Memory UUID.”
- hardboolean“Permanently delete (cannot be restored).”
- expected_version_idstring“Optimistic concurrency token from a prior read.”
pathrule_read_ruleon 1 other serverreads or searches
“Return a single rule.”
2 inputs
- rule_idstring“Rule UUID.”
- idstring“Same as rule_id.”
pathrule_write_ruleon 1 other servercreates or changes datadescribed as changing data
“Create a new rule (constraint) at a workspace path.”
12 inputs, 5 required
- workspace_idstring“The workspace UUID from pathrule_get_context or the UserPromptSubmit hook metadata.”
- cwdstring“Absolute working directory, used to resolve the workspace when `workspace_id` is omitted.”
- node_pathstringrequired“Workspace-relative path like '/apps/api'.”
- namestringrequired“Short imperative rule name.”
- contentstringrequired“Rule body (markdown, bullet form preferred).”
- scope_typestringrequired“folder = applies under a specific directory; file_type = applies to a file glob; project = applies everywhere.”
- prioritystringrequired“high = violations cause bugs/security/regressions; medium = default; low = stylistic.”
- constraintobject“Optional executable constraint.”
- constraint_intentobject“Optional executable constraint expressed as STRUCTURED INTENT rather than a regex.”
- checkobject“Optional executable CHECK.”
- verboseboolean“Set to true to receive the full rule row in the response.”
- allow_duplicateboolean“When omitted/false, the write is rejected with code 'duplicate' if a rule with the same normalised name already exists in this workspace.”
pathrule_update_ruleon 1 other servercreates or changes datadescribed as changing data
“Update an existing rule, OR restore a soft-deleted one.”
10 inputs, 1 required
- rule_idstringrequired“Rule UUID.”
- expected_version_idstring“Optimistic concurrency token.”
- patchobject“Fields to change.”
- content_editobject“Surgical edit applied to the CURRENT body server-side — send only the delta instead of the whole content.”
- restoreboolean“Restore a soft-deleted rule (sets deleted_at = null).”
- move_to_pathstring“Optional — workspace-relative target path (e.g.”
- refresh_idstring“Pathrule refresh task UUID from pathrule_get_refresh_brief — when set, this update auto-resolves that task.”
- refresh_notestring“Optional note paired with refresh_id, stored with the resolved refresh task.”
- verboseboolean“Set to true to receive the full updated rule in the response.”
- allow_duplicateboolean“When omitted/false, a rename that would collide with another rule's normalised name in the workspace is rejected with code 'duplicate'.”
pathrule_delete_ruleon 1 other serverdeletesdescribed as changing data
“Soft-delete a rule by id.”
3 inputs, 1 required
- rule_idstringrequired“Rule UUID.”
- hardboolean“Permanently delete (cannot be restored).”
- expected_version_idstring“Optimistic concurrency token from a prior read.”
pathrule_read_skillon 1 other serverreads or searches
“Return a single skill's stored package primary SKILL.md body.”
2 inputs
- skill_idstring“Skill UUID.”
- idstring“Same as skill_id.”
pathrule_write_skillon 1 other servercreates or changes datadescribed as changing data
“Create a new skill (pass EITHER `workspace_id` OR `cwd`; with neither the server resolves the workspace from its own working directory) (a reusable checklist/pattern/template) at a workspace path.”
10 inputs, 3 required
- workspace_idstring“The workspace UUID from pathrule_get_context or the UserPromptSubmit hook metadata.”
- cwdstring“Absolute working directory, used to resolve the workspace when `workspace_id` is omitted.”
- node_pathstringrequired“Workspace-relative path the skill attaches to.”
- namestringrequired“Skill name (matches frontmatter.name).”
- descriptionstring or null“One-sentence summary for the skill index (matches frontmatter.description).”
- contentstringrequired“Full SKILL.md body (frontmatter + markdown).”
- sourcestring“'manual' (default) = content is authoritative; 'github_ref' = content is fetched from github_url on read; 'template' reserved for the built-in template library.”
- github_urlstring or null“Required when source='github_ref'.”
- tagsarray“Kebab-case tags, up to 10.”
- verboseboolean“Set to true to receive the full skill row in the response.”
pathrule_update_skillon 1 other servercreates or changes datadescribed as changing data
“Update an existing skill, OR restore a soft-deleted one.”
7 inputs, 1 required
- skill_idstringrequired“Skill UUID.”
- expected_version_idstring“Optimistic concurrency token.”
- patchobject“Fields to change.”
- content_editobject“Surgical edit applied to the CURRENT body server-side — send only the delta instead of the whole content.”
- restoreboolean“Restore a soft-deleted skill (sets deleted_at = null).”
- move_to_pathstring“Optional — workspace-relative target path (e.g.”
- verboseboolean“Set to true to receive the full updated skill in the response.”
pathrule_delete_skillon 1 other serverdeletesdescribed as changing data
“Soft-delete a skill by id.”
3 inputs, 1 required
- skill_idstringrequired“Skill UUID.”
- hardboolean“Permanently delete (cannot be restored).”
- expected_version_idstring“Optimistic concurrency token from a prior read.”
pathrule_import_patternon 1 other servercreates or changes datadescribed as changing data
“Import an official Pathrule pattern (a bundle of memories, rules, and skills) into the workspace when the user pastes a `::pathrule:package:<slug>` token.”
5 inputs, 2 required
- workspace_idstringrequired“The workspace UUID from pathrule_get_context.”
- slugstringrequired“Pattern slug — the part after 'package:' in ::pathrule:package:<slug>.”
- node_pathstring“Base path to re-root the whole bundle under, chosen to match this workspace (e.g.”
- dry_runboolean“True returns the pattern's appliesTo + pieces (with resolved paths) WITHOUT writing.”
- verboseboolean“Set true for per-piece detail.”
pathrule_remove_patternon 1 other serverdeletesdescribed as changing data
“Remove a previously-imported Pathrule pattern bundle in one call — the reverse of pathrule_import_pattern.”
4 inputs, 2 required
- workspace_idstringrequired“The workspace UUID from pathrule_get_context.”
- slugstringrequired“Pattern slug — the part after 'package:' in ::pathrule:package:<slug>.”
- node_pathstring“The base path the bundle was imported under.”
- verboseboolean“Set true for per-piece detail.”
pathrule_log_activityon 1 other servercreates or changes datadescribed as changing data
“Log a file-modifying response with structured taxonomy and file paths.”
13 inputs, 4 required
- workspace_idstring“Workspace UUID.”
- cwdstring“Absolute working directory — server resolves to workspace_id via user_workspace_paths.”
- node_pathstring“Workspace-relative path, e.g.”
- domainstringrequired“What area: ui, backend, database, infra, config, test, docs”
- actionstringrequired“What was done: create, update, fix, refactor, delete, style”
- scopestringrequired“What kind of thing: component, page, hook, store, api, migration, service, model, util, project”
- subjectsarray“Free-form keywords, lowercase.”
- task_summarystringrequired“One concise sentence describing the completed work.”
- files_touchedobject“Files involved (optional).”
- ai_clientstring
- session_idstring“Hook session_id from UserPromptSubmit metadata.”
- applied_memory_idsarray“Optional.”
- verboseboolean“Set to true to receive the full activity row in the response.”
pathrule_list_pending_refresheson 1 other serverreads or searches
“List the open refresh tasks in this workspace: memories or rules an agent flagged with `pathrule_request_refresh`.”
2 inputs, 1 required
- workspace_idstringrequired“Workspace UUID.”
- include_in_progressboolean“Include tasks previously claimed (status='in_progress').”
pathrule_get_refresh_briefon 1 other serverreads or searchesdescribed as changing data
“Claim a refresh task and return its full brief — subject body, plain-language reason, raw detection signals and AI instructions.”
2 inputs, 1 required
- refresh_idstringrequired“Refresh task UUID from pathrule_list_pending_refreshes.”
- claimed_bystring“Optional — identify the AI client (e.g.”
pathrule_resolve_refreshon 1 other servercreates or changes datadescribed as changing data
“Mark a refresh task as applied (you successfully updated the memory/rule) or rejected (the suggestion was wrong or no longer relevant).”
4 inputs, 2 required
- refresh_idstringrequired“Refresh task UUID.”
- statusstringrequired“'applied' when you updated the memory/rule; 'rejected' when you decided the suggestion is wrong or obsolete.”
- notestring“Optional — short note to the user about what you changed or why you rejected.”
- claimed_bystring“Optional — overwrite the claimant identifier (e.g.”
pathrule_request_refreshcreates or changes datadescribed as changing data
“Call this when you notice that an existing memory or rule has drifted from the current codebase, contradicts what you just read, or is too narrow/unclear to be useful.”
4 inputs, 3 required
- subject_typestringrequired“Whether you're flagging a memory or a rule.”
- subject_idstringrequired“UUID of the memory or rule.”
- reasonstringrequired“One short sentence saying what drifted, read by the session that picks up the task, e.g.”
- kindstring“Optional category.”
pathrule_runtime_eventsreads or searches
“Read the runtime errors and events an application reported to this workspace (Pathrule Local or Cloud), grouped by fingerprint, newest first, with each group's verification state after a fix (unobser…”
10 inputs
- workspace_idstring“Workspace id from pathrule_get_context.”
- cwdstring“Absolute path inside the workspace, used when workspace_id is omitted.”
- group_idstring“One group, with its history.”
- pathstring“A workspace path; groups at it and below it.”
- kindstring
- environmentstring
- statusstring
- verificationstring
- limitinteger“Groups per page, 1 to 100 (default 20).”
- cursorstring“`next_cursor` from the previous page.”
pathrule_runtime_events_resolvecreates or changes datadescribed as changing data
“Record that a fix for one runtime event group shipped, so Pathrule verifies it against later releases: quiet after a day of a newer release without the issue, verified when the group's flow also succ…”
8 inputs, 3 required
- workspace_idstring“Workspace id from pathrule_get_context.”
- cwdstring“Absolute path inside the workspace, used when workspace_id is omitted.”
- group_idstringrequired“The group's id from pathrule_runtime_events.”
- expected_revisionintegerrequired“The group's `revision` as you read it.”
- idempotency_keystringrequired“One key per correction attempt, e.g.”
- baseline_releasestring“The release the fix was made against.”
- notestring“What was changed, in a sentence.”
- knowledge_refsarray“Ids of the memories, rules or skills the fix relied on.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 33 tools
Says what it returns: 78% of 32 tools
States limits, defaults or errors: 32% of 28 tools
Says when to use it: 100% of 33 tools
Items covered per tool: 3.2 of 4 on average

Counted from the listing

Parameters with a description: 94% of 190
Tools with a description: 100% of 33
Typical description length: 482 characters

The tool set

Counted from the listing

Tools: 33
Size of the list: about 17,663 tokens for an agent to load (characters ÷ 4)
Naming: 33 of 33 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 33 of 33 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @pathrule/mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "pathrule": {
      "command": "npx",
      "args": [
        "-y",
        "@pathrule/mcp@1.0.6"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pathrule": {
      "command": "npx",
      "args": [
        "-y",
        "@pathrule/mcp@1.0.6"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "pathrule": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pathrule/mcp@1.0.6"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"pathrule","type":"stdio","command":"npx","args":["-y","@pathrule/mcp@1.0.6"]}'

Claude Code

claude mcp add --transport stdio pathrule -- npx -y @pathrule/mcp@1.0.6

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @pathrule/mcp@1.0.6

This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://cloud.pathrule.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "pathrule": {
      "url": "https://cloud.pathrule.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "pathrule": {
      "type": "http",
      "url": "https://cloud.pathrule.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"pathrule","type":"http","url":"https://cloud.pathrule.io/mcp"}'

Claude Code

claude mcp add --transport http pathrule https://cloud.pathrule.io/mcp

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://cloud.pathrule.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 1.0.6
Latest stable: 1.0.7
Status: behind the latest release (1 releases, 1 days)
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-tjUSSKtL9MKYkneR7…
Signature: signed and attested
License: Apache-2.0

Source: the package registry · 2026-10-23.

Usage

Downloads: 164 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint cloud.pathrule.io/mcp	Endpoint answered and asked for sign-in	matches	our test · 2026-10-23
No credential declared as required	Required sign-in	differs	our test · 2026-10-23
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 1.0.6 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/pathrule/pathrule	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.pathrule · 2 servers
GitHub owner: an organization (pathrule)
Build record: signed and attested

Repository: github.com/pathrule/pathrule
Stars: 4
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

#11,172 of 15,112 packages by monthly downloads, tied with 42 others
Not ranked by stars: 4 stars (ranked from 10)
#1,023 of 1,074 packages meeting all 9 record checks, by downloads, tied with 1 other

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierApache-2.0
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists; a newer one is out.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.pathrule/pathrule

Answered from the data above

Is io.pathrule/pathrule safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 19 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.pathrule/pathrule free to use?

Its website (www.pathrule.io/pricing) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Has io.pathrule/pathrule been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.pathrule/pathrule do?

It lists 33 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and delete. We did not call any tool, so this describes the text, not the behaviour.

Can io.pathrule/pathrule change or delete data?

19 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.pathrule/pathrule publish a security policy?

Yes: its repository has a public security policy (github.com/pathrule/pathrule/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

No. The registry lists 1.0.6; the latest stable release on npm is 1.0.7.

Where is the source code of io.pathrule/pathrule?

In github.com/pathrule/pathrule, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.DeusData/codebase-memory-mcpCodebase Memoryalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.mobile-next/mobile-mcpalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.callstack/agent-deviceagent-devicealso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.A9T9/uivision-mcpUi.Vision MCPalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.Vrun-design/openflowkit-mcpalso has tools that creates or changes data, deletes, reads or searchescompare with this one
io.github.openflowkit/openflowkit-mcpalso has tools that creates or changes data, deletes, reads or searchescompare with this one

Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model. This server also has a remote test (1 of 18 applicable checks exercised).

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
98,784 msConnected after 0 redirects.
Read the inventory: 33 tools, 0 resources, 0 prompts.
100,111 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23

Pricing modelAI-classified

freemium

read from www.pathrule.io/pricing · 2026-10-23

“Solo is free.”

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

remote and local package

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

standard input/output, streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

164 downloads a month

package registry · 2026-10-23

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

either (remote or your machine)

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.pathrule/pathrule: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.pathrule/pathrule

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.pathrule/pathrule)](https://protocolprobe.com/mcp/servers/io.pathrule/pathrule)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology