Skip to content
HODDS logo

HODDS MCP server

Which MCP servers are HODDS's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to HODDS

Whose server it is
  • Registry nameai.hodds/hoddsverified in the MCP registry

The registry name sits under hodds.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools18
  • Server calls itselfhodds
  • Server version0.6.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 570 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Compare two or three software options for a business need; Check documented sources, pricing and limits before choosing; Monitor whether a chosen software still fits your needs.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • For "Compare two or three software options for a business need", the likely first call is search_solutions.
  • For "Check documented sources, pricing and limits before choosing", the likely first call is compare_solutions.
  • For "Monitor whether a chosen software still fits your needs", the likely first call is watch_need.
  • Keep approval on for send_feedback: they delete, send or pay without saying so.
  • send_feedback, set_current_choice, set_creator_processes, cancel_creator_plan, cancel_plan change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer88 ms
  • Space in an agent's context≈ 5,531 tokensthe definitions of all its tools (18), which an agent carries on every turn
  • Tool definitionsA · 97 of 100
  • Typed results18 of 18 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 18

What an agent can do with it

  • can do · Compare two or three software options for a business need
  • can do · Check documented sources, pricing and limits before choosing
  • can do · Monitor whether a chosen software still fits your needs

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that delete, send or pay, marked as not destructive: send_feedback
  • Tools that change data, on a server that answers without a sign-in: send_feedback, set_current_choice, set_creator_processes, cancel_creator_plan, cancel_plan

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers18 tools · read 2026-10-29
  • search_solutions

    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")…

  • get_solution

    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…

  • list_processes

    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…

  • send_feedback

    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…

  • watch_need

    Watches a need; CATEGORY follows a process. Initially not_computed; rules produce challenger/switch brief; alerts on following calls. Unknown constraints stay uninterpreted. prepaid-v1: payment_required (402), draft_id, watch_status…

  • get_watch

    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)…

  • list_watches

    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…

  • set_current_choice

    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.

  • ack_alerts

    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…

  • rate_alert

    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.

  • unwatch_need

    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.

  • get_creator_plan

    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…

  • set_creator_processes

    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…

  • list_gaps

    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)…

  • cancel_creator_plan

    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…

  • get_plan

    Returns the plan of the organisation of the token: FREE, PAID, PAST_DUE, ENDING or ENDED; watched solutions billed in the current Stripe period, offer_version, invoice and payment proof. initial_basket, when present, gives the account's…

  • cancel_plan

    Stops the subscription at period end; new paid watches are refused immediately. Then paid watches close and remain readable 30 days. No renewal minimum. Agent tokens and legacy free rights are unchanged. Without a paid plan the tool…

  • compare_solutions

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "hodds": {
      "type": "http",
      "url": "https://hodds.ai/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http hodds https://hodds.ai/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://hodds.ai/mcp as a custom connector in the settings.

OpenAPI spec

35 paths, read 2026-10-29. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.