MCP server for advanced web search using Tavily
Tools
search_servers
Search the mcprush catalogue of MCP servers. Returns name, what it does, its security grade, its price and its id. The install line comes from install_command, one listing at a time.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
5
tools declared
—
trust score
remote
via our gateway
—
p95 latency
What it does
This is the marketplace's own server: we publish it and we run it. It answers five questions. **search_servers** finds servers by words in the name or description, optionally inside one category or only the free ones. **get_server** returns everything the catalogue holds about one of them: what it does, the tools it declares and what each reaches, the security grade and the number of findings behind it, and the price. **list_categories** returns every heading with a live count under it. **search_skills** does the same for agent skills. **install_command** returns the exact line to run — or the config block to write, and the file it goes in — for the client the caller is running, and says so plainly where that client cannot run the server at all. It reads the same database the pages read, with SELECTs and nothing else. It holds no credential of yours, writes nowhere, and returns no text from a third party — every string in an answer came out of this catalogue.
Quickstart
# 1 — sign in once: npx mcprush@latest login
# it asks for a key from mcprush.com/dashboard#access
# 2 — install
npx mcprush@latest add mcpdevpro/mcprush-catalogue
# 3 — ask your agent for something these tools do
# search_servers, get_server, list_categories and 2 more
Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither.
mcprush Catalogue costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
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 — this server runs on infrastructure we host behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
Claude Code has its own MCP command, and the key rides on it as a header — the gateway refuses a call that carries none. Claude Code reads MCPRUSH_KEY each time it connects, so the key stays out of its config: export your key from Access in your shell profile (macOS, Linux), or run setx MCPRUSH_KEY <your key> and open a new terminal (Windows). Or let npx mcprush@latest add mcpdevpro/mcprush-catalogue write the entry with the key for you; --scope user makes it available in every project.
claude mcp add --transport http --scope user mcprush-catalogue https://mcprush.com/gw/mcprush-catalogue/mcp --header 'Authorization: Bearer ${MCPRUSH_KEY}'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install on mcprush: no card. The gateway still answers a key, so you sign in once — which is also what gives you saved lists, release alerts and a budget cap.
What it writes
One config entry pointing at the gateway. The server itself runs on infrastructure we host, so nothing from this listing executes on your machine.
What you approve
5 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.
Search the mcprush catalogue of MCP servers. Returns name, what it does, its security grade, its price and its id. The install line comes from install_command, one listing at a time.
No parameter schema on file.
Everything the catalogue knows about one MCP server: what it does, the tools it declares, its security grade and findings, its price, and the command that installs it.
No parameter schema on file.
The headings the catalogue is filed under, with how many live servers sit in each.
No parameter schema on file.
Search the mcprush catalogue of agent skills — instructions an agent reads rather than servers it calls.
No parameter schema on file.
The exact line to run — or the config block to write — to add one server to one client. Thirteen clients are named and each takes its own form, so this returns the right one rather than a generic package name. Where a client cannot run the server at all, it says so and why.
No parameter schema on file.
Free
$0 forever
- Every tool, 500 calls a month at 60 a minute, and mcprush charges nothing
- A buyer key from your dashboard — the gateway refuses a call without one
- Answers through our gateway, so every call is in your log
- 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 mcprush Catalogue or to call it, and past the free tier's allowance a call is refused rather than charged.
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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
The gateway serves every install the publisher’s current release, so a release cannot be pinned or rolled back to here yet. The history below is for reading; the current release on file is 1.0.1.
1.0.1
1 Sep 2026
latest- Checks that the release reads the tool surface from the endpoint rather than from our table.
—
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 mcprush Catalogue 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.