MCP server for advanced web search using Tavily
pit.world 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.
What it does
MCP server for private web search (no API key) and Moshpit name lookups. No logs, no cookies.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user pit-world-mcp '--' npx -y pitworld mcp
# 2 — ask your agent for something these tools do
# search, moshpit_resolve, listing and 22 more
pit.world costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts pit.world as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user pit-world-mcp '--' npx -y pitworld mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take PIT_URL (pit.world instance to query (default https://pit.world)) if you want to set it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
25 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Search the web through pit.world: no logs, no tracking. Also resolves Moshpit names (label.ending) through the Moshpit registry.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
Look up a Moshpit network name (for example chovy.hacker) in the Moshpit registry: whether it is registered and where it points.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
Look up a business listing on pit.world by domain (example.com or a Moshpit name): name, description, who operates it (agent/person handle, company), category, service area, services, price range, hours, phone, links, its feed, whether it is in the pit.world web ring, whether it takes quote…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
Search the pit.world pro directory: businesses and independent pros. claimed=true means the owner verified their own site; seeded=true means pit.world listed it from public records (e.g. a CSLB contractor license, shown in license) and the owner has not claimed it yet. No paid placement and no…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | — |
| category | string | no | — |
| near | string | no | — |
| limit | integer | no | — |
The pit.world web ring: every site in it (claimed pit.world listings plus the Moshpit network sites), in ring order, with direct and pit.world proxy URLs and feeds.
No parameter schema on file.
Edit a pit.world business listing you own, with the edit key (pitk_...) you got when you claimed it. Only the fields you pass change. operator is an agent or person handle (name@host) or an https URL; contactEmail is the private address quote requests go to (confirmed by email before it is used;…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
| key | string | yes | — |
| name | string | no | — |
| description | string | no | — |
| operator | string | no | — |
| company | string | no | — |
| companyUrl | string | no | — |
| category | string | no | — |
| services | array | no | — |
| area | string | no | — |
| city | string | no | — |
| region | string | no | — |
| country | string | no | — |
| price | string | no | — |
| hours | string | no | — |
| phone | string | no | — |
| links | array | no | — |
| contactEmail | string | no | — |
| ring | string | no | — |
Live numbers for the Moshpit network: endings claimed, registry events, recent claims, endings for sale.
No parameter schema on file.
Promotion campaigns (operators): list them.
No parameter schema on file.
A promotion campaign at a glance: members by state, outreach holds, placements by state, measurement windows, reports, drafts, spend.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign | string | yes | promotion campaign id (pcm_...) or its OutreachGraph campaign id |
The campaign roster: every business, its source lead ids, website, listing URL, verification status and planned action, plus unresolved leads. Private (contains lead ids).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| offset | integer | no | — |
Import a complete or partial campaign snapshot (the JSON scripts/outreachgraph-campaign-export.sh writes). dryRun shows every row disposition without writing. Re-importing the same snapshot changes nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| snapshot | yes | — | |
| dryRun | boolean | no | — |
One campaign business: leads, outreach hold, verification, windows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
Resolve a campaign business: displayOrder (campaign order, null to clear), priority (false removes its directory priority without touching the listing), priorContact (a documented earlier contact, which makes the draft a follow-up), holdAttestation (an operator attests upstream outreach is held).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| displayOrder | integer | no | — |
| priority | boolean | no | — |
| priorContact | string | no | — |
| holdAttestation | string | no | — |
Exclude a business (domain) or a lead (lead id) from the campaign, with a reason.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | — |
| reason | string | yes | — |
Preview a launch: which businesses launch, which are blocked and why, every planned post with its text and time, and the version launch needs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign | string | yes | promotion campaign id (pcm_...) or its OutreachGraph campaign id |
Launch with the version from promo_preview: publishes the roundup and creates the posting calendar. Refuses a stale preview.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| version | string | yes | — |
Pause (no new posts or sends; reports and listings stay), resume (active) or stop a campaign.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | yes | — |
Posts and pages of a campaign with state (scheduled, published, verified, failed, uncertain...), public URL, evidence and error.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | string | no | — |
| domain | string | no | — |
Put a failed placement back in line (at most three attempts).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| placement | string | yes | — |
One business: its measurement windows and the numbers so far (views, website clicks, phone taps, views from campaign links), with the latest report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | — |
Reports of a campaign; generate=true first runs the hourly pass and writes reports for every window that has ended.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| generate | boolean | no | — |
One report (frozen snapshot, versioned) as JSON or Markdown.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report | string | yes | — |
| format | string | no | — |
Outreach drafts of a campaign (written from reports after windows end; never sent unless sending is authorized).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| campaign | string | yes | promotion campaign id (pcm_...) or its OutreachGraph campaign id |
Write the outreach draft for a report (one per report version).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report | string | yes | — |
Send one draft. Refused unless the campaign authorizes sending, the window has ended, the report is current and the recipient is not suppressed upstream.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| draft | string | yes | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 pit.world or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (25 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search | no tags | |
| moshpit_resolve | no tags | |
| listing | no tags | |
| pros | no tags | |
| ring | no tags | |
| edit_listing | no tags | |
| moshpit_network | no tags | |
| promo_campaigns | no tags | |
| promo_overview | no tags | |
| promo_roster | no tags | |
| promo_import | no tags | |
| promo_member | no tags | |
| promo_update_member | no tags | |
| promo_exclude | no tags | |
| promo_preview | no tags | |
| promo_launch | no tags | |
| promo_pause | no tags | |
| promo_placements | no tags | |
| promo_retry_placement | no tags | |
| promo_results | no tags | |
| promo_reports | no tags | |
| promo_report | no tags | |
| promo_drafts | no tags | |
| promo_create_draft | no tags | |
| promo_deliver | 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
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.5.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
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.
Any signed-in account that does not publish pit.world can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.