MCP server for advanced web search using Tavily
Nothing to run from here
HODDS 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
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Find software, SaaS and APIs for a need in a sourced catalogue organised by business process.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hodds-mcp https://hodds.ai/mcp
# 2 — ask your agent for something these tools do
# search_solutions, get_solution, list_processes and 18 more
HODDS costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HOAll 1 server
hodds1 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 hodds-mcp https://hodds.ai/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
21 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.
Searches the HODDS catalogue of software, SaaS, APIs and online services, organised by business process, for records that match a need written in English or French (for example "transcribe my meetings" or "automatiser mes workflows"). Returns a request_id, a status and up to limit options; each option has an id, a label, a short description and source URLs (provenance). Ranking combines lexical
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | yes | The need in natural language, English or French: the task to get done. |
| limit | integer | no | Maximum number of options to return (1-50, default 10). |
| process | string | no | Optional process id that restricts the search (ids from list_processes, e.g. "automate-workflows"). |
| lang | string | no | Language of option descriptions: "en" (default) or "fr". |
Returns one HODDS catalogue record by id (an option id returned by search_solutions): name, homepage, summary in English and French, processes (the first is primary), keywords, pricing models without amounts (empty means unknown) with the pricing page, interfaces (public API, MCP server, self-hosting: yes, no or unknown), markets, publisher, dated sources and status. Status non_attested means the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Solution id, e.g. "n8n". |
Returns the HODDS process taxonomy: groups (for example "Run the business") and processes (for example "invoice-and-get-paid"), with English and French labels and the number of catalogue records per process. A process id is accepted as the process filter of search_solutions. Read-only.
No parameter schema on file.
Stores a declarative outcome report for an option returned by search_solutions: outcome YES (the option met the need), PARTLY or NO, with the request_id and the option id exactly as returned. It is the only HODDS tool that writes data without a token; the watch tools (watch_need and the others) write only with an organisation token. The report is stored as an unverified caller statement and never
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | request_id returned by search_solutions (req_...). |
| option_id | string | yes | id of the option being reported. |
| outcome | string | yes | YES: the option met the need. PARTLY: in part. NO: it did not. |
Opens a watch on a need for the organisation of the token: constraints and software by id or name (any process). CATEGORY follows a process. Returns the watch, initially not_computed; public rules produce a challenger and switch brief. Alerts arrive on following calls; unknown constraints stay uninterpreted. The FREE plan follows one active watch per organisation. Error codes beyond the free watch
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | no | The need in natural language, English or French (absent for a CATEGORY watch). |
| level | string | no | NEED (default when need is given) or CATEGORY (process required, no need). |
| process | string | no | Process id (from list_processes); deduced from the need when absent. |
| context | object | no | — |
| current_choice_name | string/null | no | Free name instead of id; exact unique matches resolve, others stay unlinked. |
| current_choice | string | no | Active catalogue id; any process accepted. |
| delivery | object | no | — |
| alert_budget | integer | no | Alerts per calendar month (1-20, default 5); beyond, one DIGEST per day. |
| lang | string | no | Language of the summary: "en" or "fr". |
Returns one watch of the organisation: constraints, solution in place, challenger with its switch brief and HODDS status, challenger_reason when there is none, and the 50 most recent alerts, unacknowledged first (all: true for 200). Reading does not acknowledge. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | Watch id returned by watch_need or list_watches (w_...). |
| all | boolean | no | true: the 200 most recent alerts. |
Lists the watches of the organisation with their challenger and number of pending alerts; include_closed adds the watches closed in the last 30 days. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_closed | boolean | no | true: include watches closed in the last 30 days. |
Sets a solution by id or free name (any process), null clears. Returns the watch; challenger recomputed later. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | Watch id returned by watch_need or list_watches (w_...). |
| current_choice_name | string/null | no | Free name instead of id, or null. |
| current_choice | string/null | no | Catalogue id, or null. |
Acknowledges alerts of one watch (alert_ids, or all: true for every alert of this watch); the only call that empties the pending delivery. Returns the number acknowledged and the number remaining for the organisation; a replay changes nothing. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | Watch id returned by watch_need or list_watches (w_...). |
| alert_ids | array | no | Alert ids (a_...). |
| all | boolean | no | true: every alert of this watch. |
Marks one alert relevant or not_relevant, with an optional note of at most 500 characters. It never changes ranking. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | Watch id returned by watch_need or list_watches (w_...). |
| alert_id | string | yes | Alert id (a_...). |
| rating | string | yes | relevant or not_relevant. |
| note | string | no | Optional note. |
Closes a watch; its need, constraints and alerts are erased 30 days after closing. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| watch_id | string | yes | Watch id returned by watch_need or list_watches (w_...). |
Returns the demand data subscription of the organisation of the token: plan NONE or SUBSCRIBED, subscribed processes, pending removals, the coming invoice, payment provider and invoices. €10 excl. VAT per process per month, invoiced by VORAN, paid through Stripe; no effect on ranking. Contract 0.3.1. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the err
No parameter schema on file.
Replaces the list of subscribed processes. Without an active subscription the result has status 402 and a Stripe Checkout destination for a person to open. With one, an addition through this tool also answers status 402 with the Plan page as destination: nothing is charged here, only the page charges, after a person confirms it. Removals apply at once and the removed processes stay readable until
| Parameter | Type | Required | Notes |
|---|---|---|---|
| processes | array | yes | — |
Returns, for a subscribed process, the gaps formulated by HODDS and the client aggregates above the anonymity threshold (watched needs, organisations watching, NO_MATCH, current choices, constraints, challengers delivered, GAP_RESOLVED). No need text, no organisation, no agent. Contract 0.3.1. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error toke
| Parameter | Type | Required | Notes |
|---|---|---|---|
| process | string | yes | Process id of /catalogue/processes.json. |
Stops the subscription at the end of the paid period. Listings, claims, declarations and ranking are unchanged; the coarse demand table stays free. Contract 0.3.1. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
No parameter schema on file.
Returns the plan of the organisation of the token: FREE, PAID, PAST_DUE, ENDING or ENDED; watched solutions billed in the current Stripe period, the coming invoice, the payment provider and the invoices. 1 watched solution free, then €0.50 per watched solution per month, €2 monthly minimum (excl. VAT), invoiced by VORAN, paid through Stripe. A paid watch is billed for a period when it is active at
No parameter schema on file.
Stops the paid plan at the end of the Stripe period. Then the paid watches are CLOSED and stay readable 30 days; the free watch and the agent tokens are unchanged. Without a paid plan the tool answers not_paid. Contract 0.5.0. Needs an organisation token (Authorization: Bearer hodds_...); without it the tool returns the error token_required.
No parameter schema on file.
Compare 2–3 catalogue IDs by required capabilities, offer, context and dated sources. Unknown/stale/conflict stay explicit; unknown price is never zero. Discover IDs at /api/capabilities and details at /api/solutions/{id}/specification. Costs require all assumptions. Large result: repeat arguments with view; restart on 409. Public read, no billing/business writes; one call per POST.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| solution_ids | array | yes | — |
| priority | no | — | |
| priority_required | boolean | no | — |
| criteria | array | no | — |
| requirements | array | no | — |
| context | object | no | — |
| cost_scenario | no | — | |
| locale | string | no | — |
| view | object | no | — |
Find alternatives by required priority, optionally relative to one solution. IDs/context: /api/capabilities. A match satisfies every requirement in one configuration. Evaluates the whole pilot before limit, separating match/unresolved/mismatch and stating catalogue coverage, not market coverage. Large result: repeat arguments with view; restart on 409. Public read, no billing/business writes; one
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference_id | no | — | |
| priority | object | yes | — |
| criteria | array | no | — |
| requirements | array | no | — |
| context | object | no | — |
| cost_scenario | no | — | |
| locale | string | no | — |
| limit | integer | no | — |
| view | object | no | — |
Public read: capabilities discovers IDs and context vocabulary; candidates finds IDs for a priority; compare compares 2–3 IDs; specification reads one dossier. Same operation/input with representation detail, transport.resume and reference reads a snapshot field or page. On 409 restart summary. No account or writes. Sources, unknowns and dated limits remain explicit. Read the single JSON content.t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | — |
| input | object | no | — |
| representation | string | no | — |
| resume | object | no | — |
| reference | object | no | — |
Requires a Bearer token and an existing owned NEED watch. bind explicitly attaches a canonical comparison request at expected_revision (optional explicit reset_baseline); review checks the current accepted documentary build; get reads the retained state and events with after/limit (1–50). No new watch, purchase or notification. A conflict requires an explicit caller decision; no automatic retry or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation | string | yes | — |
| watch_id | string | yes | — |
| request | object | no | — |
| expected_revision | integer | no | — |
| reset_baseline | boolean | no | — |
| after | integer | no | — |
| limit | integer | no | — |
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 HODDS 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 0.4.0 · scanned 27 Oct 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 digest48612ce8fe68c21cfb008a8f74b38e215e0ad049787d02598bd7d5fa9bafc012
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 |
|---|---|---|
| search_solutions | no tags | |
| get_solution | no tags | |
| list_processes | no tags | |
| send_feedback | state-write | state-write: declares readOnlyHint: false |
| watch_need | state-write | state-write: declares readOnlyHint: false |
| get_watch | no tags | |
| list_watches | no tags | |
| set_current_choice | state-write | state-write: declares readOnlyHint: false |
| ack_alerts | state-write | state-write: declares readOnlyHint: false |
| rate_alert | state-write | state-write: declares readOnlyHint: false |
| unwatch_need | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_creator_plan | no tags | |
| set_creator_processes | state-write | state-write: declares readOnlyHint: false |
| list_gaps | no tags | |
| cancel_creator_plan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_plan | no tags | |
| cancel_plan | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| compare_solutions | no tags | |
| find_comparable_solutions | no tags | |
| read_choice | no tags | |
| watch_choice | state-write | state-write: declares readOnlyHint: false |
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 digest48612ce8fe68c21c
Scanned2026-10-27
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 0.4.0.
0.4.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 HODDS 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.