RU
Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.
Nothing to run from here
Paxmod is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
Content moderation for chat and comments: free test keys, message checks, plain-English policies.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http paxmod-mcp https://www.paxmod.com/mcp
# 2 — ask your agent for something these tools do
# get_integration_guide, create_test_api_key, moderate_text and 8 more
Paxmod costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PAAll 1 server
paxmod1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http paxmod-mcp https://www.paxmod.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The full Paxmod API guide for coding agents: endpoints, request and response shapes, error codes, rate limits and code samples (Node, Python, Unity, Roblox and more).
No parameter schema on file.
Creates a working text-moderation API key with no account: 100 messages over 72 hours, standard mode, every category on. Returns api_key and claim_url; opening claim_url keeps the key in a Paxmod account. Limited to 3 keys per address per day.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Optional project name, for example the game's name. |
| source | string | no | Optional: the agent or tool asking, for example claude-code. |
Checks one chat message with Paxmod, using the project's categories and thresholds. Returns flagged or not_flagged with a score per category. Counts as one of the project's messages, like a live request. Needs a Paxmod API key (create_test_api_key gives one).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Paxmod API key for the project. |
| message | string | yes | The message to check, up to 5000 characters. |
| user_id | string | no | Optional: the player who sent it. |
| context_id | string | no | Optional: the chat, channel or match it was sent in. |
Runs example messages against an Advanced mode policy and says which would be flagged, with a score and reason for each. Send a draft policy to try changes before saving them; leave it out to test the saved policy. Mark each example with expect "flag" or "pass" and the summary counts how many came back as expected. The project's word rules run first, as they do live. Nothing is stored. No credits
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Paxmod API key for the project. |
| examples | array | yes | Messages to test, up to 50. |
| policy | string | no | Draft policy in plain English, up to 1,000 characters. Leave out to test the saved policy. |
| threshold | number | no | Flag above this score, 0 to 1. Leave out to use the project's setting. |
Shows what a project's word rules do to each message: block (flag without checking), bypass (pass without checking), or scan with the text rewritten by remove and replace rules. Send draft rules to try changes before saving them. No model call, nothing stored, no credits used.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | Paxmod API key for the project. |
| messages | array | yes | Messages to test, up to 50. |
| word_rules | array | no | Draft rules. Leave out to test the saved ones. Whole words, case insensitive. |
Lists the signed-in user's Paxmod projects: their own and those in organizations they belong to, with each project's id, name, type (text or image), mode (standard or advanced), organization and the user's role. API keys are not included.
No parameter schema on file.
Returns a project's moderation settings: type, mode, categories and thresholds, the Advanced mode policy, and word rules. The API key is not included.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The project's id, from list_projects. |
Returns how many messages a project has sent per day over the last 30 days (up to 90), plus the total for the current calendar month. Counts are updated through the day.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The project's id, from list_projects. |
| days | number | no | How many days back, 1 to 90. Default 30. |
Runs example messages against one of the user's Advanced mode projects, with a draft policy or the saved one, and says which would be flagged, with a score and reason for each. Mark each example with expect "flag" or "pass" and the summary counts how many came back as expected. The project's word rules run first, as they do live. Nothing is stored and no credits are used. Up to 50 examples per cal
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The project's id, from list_projects. |
| examples | array | yes | Messages to test, up to 50. |
| policy | string | no | Draft policy in plain English, up to 1,000 characters. Leave out to test the saved policy. |
| threshold | number | no | Flag above this score, 0 to 1. Leave out to use the project's setting. |
Lists a project's most recent flagged messages, newest first, with the reason, confidence, player id, context id and any reviewer verdict (TP or FP). Filter by date, category or player. Up to 50 per call. Not available for organizations that keep player data in a separate region unless Paxmod has enabled it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The project's id, from list_projects. |
| since | string | no | Only messages after this date or time (ISO 8601), for example 2026-11-01. |
| category | string | no | Only this flag reason, for example Harassment. |
| user_id | string | no | Only this player's messages (exact id). |
| limit | number | no | How many, 1 to 50. Default 20. |
Returns one player's flagged messages in a project, newest first (up to 50), with a count by reason. Use the player id the game or app sends as user_id. Not available for organizations that keep player data in a separate region unless Paxmod has enabled it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | string | yes | The project's id, from list_projects. |
| user_id | string | yes | The player's id (exact). |
| limit | number | no | How many messages, 1 to 50. Default 50. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Paxmod or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.1.0 · scanned 10 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestd47eea913c845b65a7fdf45c07d914339d2aa144a58f2a79f12ae7a4cb3bdda2
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_integration_guide | no tags | |
| create_test_api_key | state-write | state-write: declares readOnlyHint: false |
| moderate_text | state-write | state-write: declares readOnlyHint: false |
| test_policy | no tags | |
| test_word_rules | no tags | |
| list_projects | no tags | |
| get_project_settings | no tags | |
| get_usage | no tags | |
| test_policy_on_project | no tags | |
| list_flagged_messages | no tags | |
| get_player_history | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd47eea913c845b65
Scanned2026-11-10
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Paxmod can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.