_ registry / mcp http-sse · checked 9m ago

inutriplan-supplement-mcp

https://mcp.inutriplan.com

Registry code: 0e85896bcf1bf24c

api record

Query a curated iHerb supplement product database (35 000+ products, 99 evidence-graded ingredients, 14 categories). Every product URL already contains the affiliate tracking code — never modify or remove the rcode query parameter. Tools: search_supplements (keyword/benefit search), get_supplement_detail (full product facts by ID), search_by_ingredient (find products containing a compound), get_ingredient_info (evidence-graded ingredient research), list_categories (browse taxonomy), get_supplements_by_category (products in a category).

endpoint
https://mcp.inutriplan.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is inutriplan-supplement-mcp live?
Yes — it answered the hub's last check (checked 9m ago). It answered 100% of checks over the last 30 days.
Is inutriplan-supplement-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does inutriplan-supplement-mcp have?
6 tools: search_by_ingredient, get_ingredient_info, get_supplements_by_category, search_supplements, get_supplement_detail, list_categories.
Is inutriplan-supplement-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
125ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 540 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search supplement products
  • find products with an ingredient
  • get evidence for a supplement ingredient
  • browse supplement categories
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories reads open 7h ago

    Return all available iHerb product categories with their URL slugs and live product counts. Use the slug value with get_supplements_by_category to browse products within a specific category.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_by_ingredient reads unknown 9m ago

    Find products that contain a specific ingredient or compound in their ingredients list (e.g. "ashwagandha", "CoQ10", "zinc bisglycinate"). Also returns evidence-graded research context from the ingredient registry when the ingredient is recognised — goals, mechanisms, evidence grade.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ingredient"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "description": "Maximum products to return (1–40). Default 20."
        },
        "ingredient": {
          "type": "string",
          "description": "Ingredient or compound name to search for."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_ingredient_info reads unknown 7h ago

    Look up evidence-graded research context for a supplement ingredient from the curated registry (99 ingredients). Returns canonical name, aliases, health goals, mechanisms of action, evidence grade (Strong / Moderate / Preliminary), research notes, and recommended iHerb search terms.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Ingredient name, alias, or health goal keyword, e.g. \"magnesium\",\n  \"ashwagandha\", \"sleep\", \"testosterone\", \"weight_loss\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_supplements_by_category reads unknown 9m ago

    List top-rated in-stock products within a specific iHerb category. Use list_categories first to discover valid category slugs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category_slug"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "description": "Maximum results (1–60). Default 20."
        },
        "min_rating": {
          "type": "number",
          "default": 4,
          "description": "Minimum star rating (0.0–5.0). Default 4.0."
        },
        "category_slug": {
          "type": "string",
          "description": "Category slug, e.g. \"vitamins\", \"supplements\",\n           \"brain-cognitive\", \"sports\", \"magnesium-complex\"."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • search_supplements reads unknown 9m ago

    Search the iHerb product database using a natural-language query, benefit keyword, ingredient name, or brand name. Uses the PostgreSQL GIN full-text search index first (fast, relevance-ranked), then falls back to a broader ILIKE scan if FTS yields no results.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "description": "Maximum results (1–60). Default 20."
        },
        "query": {
          "type": "string",
          "description": "Search term, e.g. \"magnesium sleep support\", \"omega 3 fish oil\",\n        \"vitamin D immune\", or a brand name."
        },
        "min_rating": {
          "type": "number",
          "default": 4,
          "description": "Minimum star rating filter (0.0–5.0). Default 4.0."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • get_supplement_detail reads unknown 7h ago

    Retrieve complete details for a single iHerb product by its numeric product ID (visible in iHerb URLs, e.g. "72711" from https://www.iherb.com/pr/p/72711). Returns the full supplement facts panel (nutrients, amounts, % daily values), ingredients list, warnings, serving info, and the affiliate purchase link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product_id"
      ],
      "properties": {
        "product_id": {
          "type": "string",
          "description": "iHerb numeric product ID as a string, e.g. \"72711\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0e85896bcf1bf24c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0e85896bcf1bf24c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0e85896bcf1bf24c/badge.svg)](https://brick.blue/agent/0e85896bcf1bf24c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.