Provenancewhere it came from, and what was verified
Published by the owner of pathrule.io, who proved control of the domain through the official MCP registry.
🛡 Permissions & trustwhat this server can touch before you run it
About
Path-scoped team memories, rules and skills for Claude Code, Cursor, Codex and other MCP clients.
Packages & transports
Metadata
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸pathrule_list_workspaces100A
▸pathrule_ping93A
▸pathrule_get_context100A
▸pathrule_goto92A
▸pathrule_get_tree90A
▸pathrule_get_node100A
▸pathrule_list_memories100A
▸pathrule_read_memory100A
▸pathrule_read_rule100A
▸pathrule_read_skill100A
▸pathrule_write_memory86A
▸pathrule_update_memory100A
▸pathrule_delete_memory100A
▸pathrule_write_rule100A
▸pathrule_update_rule96A
▸pathrule_delete_rule100A
▸pathrule_write_skill100A
▸pathrule_update_skill100A
▸pathrule_delete_skill100A
▸pathrule_import_pattern100A
▸pathrule_remove_pattern100A
▸pathrule_list_organizations100A
▸pathrule_create_workspace100A
▸pathrule_setup93A
▸pathrule_take_snapshot89A
▸pathrule_list_snapshots92A
▸pathrule_read_snapshot75B
▸pathrule_list_pending_refreshes100A
▸pathrule_get_refresh_brief100A
▸pathrule_resolve_refresh100A
▸pathrule_log_activity78B
▸pathrule_get_local_runtime_upgrade100A
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +25 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
Push to the repo or cut a release. Activity within the last 30 days earns the full 45.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
- 4 of 4 params have no description: `snapshot_id`, `workspace_id`, `include_file_tree`, `include_sampled_contents`. Describe each one.
- 8 of 9 params have no description: `scope`, `action`, `domain`, `verbose`, +4 more. Describe each one.
- 4 of 7 params have no description: `title`, `source`, `content`, `allow_duplicate`. Describe each one.
- 7 of 16 params have no description: `branch`, `git_head`, `file_count`, `project_name`, +3 more. Describe each one.
Already earned (3) ▾Already earned (3) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.pathrule/pathrule-remote-mcp)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"pathrule_remote": {
"command": "npx",
"args": [
"-y",
"pathrule-remote-mcp"
]
}
}
}▶ Try itlive against mcp.pathrule.io
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.