Skip to content

ihumane MCP server

ai.ihumane/ihumaneihumane.aistreamable-httpv0.8.0Scanned

Human know-how for AI agents: rules, reasons and checks for design, code, product and writing.

12 tools: 11 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 11 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 11 findings

Tools listed without sign-in. Remote posture

With Anlyon

11 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the ihumane MCP server can do

The ihumane MCP server is published by ihumane.ai, a domain the MCP Registry verified. It has 12 tools. It can create or change data (11 tools: ihumane_start, ihumane_ui_start, ihumane_code_start, ihumane_product_start and 7 more), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 11 findings (annotation-conflict and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 0.8.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Changes things 11Claude Code: ask
  • ihumane_code_startCall this BEFORE writing or changing code that people will keep (a feature, a fix, a refactor).1 finding

    Why it is in this group

    • The name "ihumane_code_start" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_code_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_code_start" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this BEFORE writing or changing code that people will keep (a feature, a fix, a refactor). Returns the Code craft workflow: how to size the job, what to read before writing (existing helpers, the file's conventions, where the ask ends, how it's run and tested), and the rules likely to matter for your task. Ends with the tidy check to run on your change. Free: the workflow, the first step and the core rules; the other rules are ihumane Pro and are named by title.

    Annotations the server declares

    • title: Start a coding task
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_copy_startCall this BEFORE writing words people will read in a product: button labels, error messages, empty states, form labels and help, confirmations, notifications, emails, onboarding, p…1 finding

    Why it is in this group

    • The name "ihumane_copy_start" says "copy": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_copy_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_copy_start" says "copy": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this BEFORE writing words people will read in a product: button labels, error messages, empty states, form labels and help, confirmations, notifications, emails, onboarding, page copy. With ihumane Pro: the full Copy and UX writing workflow, the voice rules, and the rules most likely to matter for your task. Without Pro: the module overview and its seven most important rules.

    Annotations the server declares

    • title: Start writing interface copy (Pro)
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_feedbackCall this once at the end of a task where you used ihumane, if something was missing, wrong or especially useful: a word with no entry, a rule that didn't fit the task, a check tha…No findings

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    Description, as the server wrote it
    Call this once at the end of a task where you used ihumane, if something was missing, wrong or especially useful: a word with no entry, a rule that didn't fit the task, a check that caught a real bug, advice that was too heavy for a small job. People who write ihumane's rules read every message. Write in general terms: no names, emails, URLs, code or anything private about your human or their project.

    Annotations the server declares

    • title: Tell ihumane what helped or what was missing
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • ihumane_get_rulesCall this WHILE building, for the specific thing in front of you, e.g.1 finding

    Why it is in this group

    • The name "ihumane_get_rules" says "get": a word for reading.
    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_get_rules" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_get_rules" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Call this WHILE building, for the specific thing in front of you, e.g. 'loading button', 'card header spacing', 'success message', 'pricing page', 'empty state', 'contrast', 'error message wording', 'error handling', 'naming', 'tests', 'who is it for', 'unasked features', 'asking my human a question', 'reporting a failed step'. Covers UI design, Code craft, Product thinking and Working with your human (and Copy with Pro). Returns the matching rules in full: the rule, why it matters to a person, the agent trap, and how to check it. Without Pro: the matching free rules in full, and the titles of matching Pro rules.

    Annotations the server declares

    • title: Get the rules for what you're building
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_humanCall this once when you start working for a person, on any task (a site, a database, a domain, a document, not only UI).1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_human" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this once when you start working for a person, on any task (a site, a database, a domain, a document, not only UI). Returns how to read what they mean (fast or dictated messages, odd words), when and how to ask, how to hand them a step they must do themselves (sign-ins, clicks, payments) so they can find it, and how to report. Pass a situation to get the most relevant rules first.

    Annotations the server declares

    • title: Work well with your human
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_moduleOpens any ihumane module before that part of the work: its workflow, its first step and the rules likely to matter for your task.1 finding

    Why it is in this group

    • The description's first verb is "open": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_module" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Opens any ihumane module before that part of the work: its workflow, its first step and the rules likely to matter for your task. ihumane_start tells you which modules apply. Modules: ihumane core: 'humans' (Working with your human). Design: 'ui-design' (UI design), 'ux-design' (UX design), 'graphics' (Graphics and images). Engineering: 'code-craft' (Code craft), 'front-end' (Front-end build), 'code-review' (Code review), 'qa-testing' (QA and testing). Product: 'product-thinking' (Product thinking). Writing: 'copy' (Copy and UX writing). Free: each module's start; the other rules are ihumane Pro and are named by title.

    Annotations the server declares

    • title: Open an ihumane module
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_product_startCall this BEFORE building a new product, feature or prototype, when what to build and for whom isn't settled.1 finding

    Why it is in this group

    • The name "ihumane_product_start" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_product_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_product_start" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this BEFORE building a new product, feature or prototype, when what to build and for whom isn't settled. Returns the Product thinking workflow: who it's for (one person in one situation, never invented), the problem behind the request, what success looks like, and what not to build. Small changes to an existing product get a two-line check instead. Free: the workflow, the first step and the core rules; the other rules are ihumane Pro and are named by title.

    Annotations the server declares

    • title: Start deciding what to build
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_reviewCall this BEFORE you tell your human the work is done.1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_review" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this BEFORE you tell your human the work is done. Pass the kind of work. Each module's own review: 'ux', 'graphics', 'front-end', 'code-review', 'qa'. 'ui': render it and look at it, six review lenses (free: the user and accessibility lenses; Pro adds designer, writer, product manager and engineer), and the browser checks. 'code': run it, the verify rules and the tidy check. 'product': walk it through as the person it's for. 'writing': the copy review (Pro). 'other' (any other task): check it against what they asked, then the report rules. Every kind ends with how to report honestly.

    Annotations the server declares

    • title: Review before saying done
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_startCall this at the START of any task you do for a person: a page, a feature, a bug fix, a new product idea, a database change, a document.1 finding

    Why it is in this group

    • The name "ihumane_start" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_start" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this at the START of any task you do for a person: a page, a feature, a bug fix, a new product idea, a database change, a document. Returns which ihumane modules apply and the start tool to call next (UI design, Code craft, Product thinking, Copy), the five rules for working with a person on any task, and the rules most likely to matter for this task.

    Annotations the server declares

    • title: Start any task
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_translate_tasteCall this when your human describes the look, feel or voice with taste words ('clean', 'modern', 'premium', 'playful', 'make it pop', 'friendly', 'professional', 'sounds robotic') …1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_translate_taste" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this when your human describes the look, feel or voice with taste words ('clean', 'modern', 'premium', 'playful', 'make it pop', 'friendly', 'professional', 'sounds robotic') or feeling words ('exciting', 'amazing', 'wow', 'make people excited'). Returns the concrete decisions those words usually mean. Say your translation back to the human in one line BEFORE building or writing, so a wrong reading costs nothing.

    Annotations the server declares

    • title: Translate taste words into decisions
    • readOnlyHint: true
    • openWorldHint: false
  • ihumane_ui_startCall this BEFORE designing or building any user interface (a page, screen, component or flow).1 finding

    Why it is in this group

    • The name "ihumane_ui_start" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "ihumane_ui_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_ui_start" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Call this BEFORE designing or building any user interface (a page, screen, component or flow). Returns the ihumane workflow and the brief: what to find out first, which questions to ask your human (at most 3, each with a default), and which pattern choices you must not make silently. If you pass the task, it also lists the rules most likely to matter. Free: the workflow, the first step and the core rules; the other rules are ihumane Pro and are named by title.

    Annotations the server declares

    • title: Start a UI design task
    • readOnlyHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • ihumane_get_checkReturns a check to run on your own work.1 finding

    Why it is in this group

    • The name "ihumane_get_check" says "get": a word for reading.

    Findings

    • Info

      The description is 2,298 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ts by CSS class or position, and the real clock or random numbers inside a check."

      What this check looks for
    Description, as the server wrote it
    Returns a check to run on your own work. Browser checks run on the RENDERED page (browser console or a browser tool's evaluate/execute): 'spacing': text touching lines, uneven padding. 'contrast': text and field edges too faint against their real background, in light and dark mode. 'affordance' (Pro): controls that look like something they aren't, link underlines, back-link direction. 'stability' (Pro): controls that move or resize when used. 'copy' (Pro): vague labels, 'click here' links, placeholder-only fields, missing alt text, errors with no next step, machine-voice words. Code check, run with Node in the project: 'tidy': leftovers in your change (debug logs, .only in tests, empty catches, likely secrets, new TODOs, commented-out code, very long functions). 'wayfinding' (UX design): Pages that don't say where you are or give a way back: no clear heading or a generic page title, menus with no current item, a breadcrumb that links to itself, a deep page with no way up, a step with no Back or way out, and dead ends. 'images' (Graphics and images): Images shown larger than the file (blurry), files far wider than their slot, stretched images, broken images, images with no width and height, missing or useless alt text, icon-only buttons with no name, heavy files, and icons in one row with different sizes, strokes or styles. 'diffmap' (Code review): The shape of a change before you review it: size, a reading order, and what to look at closely (code changed with no test, migrations, data deletes, risky paths, removed exports still in use, new dependencies, imports of packages the project doesn't have, tests that mock what they test). 'layout' (Front-end build): Sideways scrolling and the element causing it, text cut off by a fixed height, tap targets that are too small at touch widths, stretched or oversized images, clickable divs with no role, fields with no label or the wrong type, and skipped heading levels. 'trust' (QA and testing): Tests you can't trust: tests that check a constant or assert nothing, tests that only check a fake was called, checks that pass for almost any result, snapshot-only tests, fixed waits, retries that hide flaky tests, end-to-end tests that find elements by CSS class or position, and the real clock or random numbers inside a check.

    Annotations the server declares

    • title: Get a runnable check
    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:20 UTC, unchanged since Nov 11, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ihumane.ai/mcp: tools/list returned 12 tools to an anonymous client, including ihumane_start (write), ihumane_ui_start (write), ihumane_code_start (write), ihumane_product_start (write), ihumane_module (write) and 6 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

10 warn1 info
  • The server marks "ihumane_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_start" says "start": a word for a change.

    What this check looks for
  • The server marks "ihumane_ui_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_ui_start" says "start": a word for a change.

    What this check looks for
  • The server marks "ihumane_code_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_code_start" says "start": a word for a change.

    What this check looks for
  • The server marks "ihumane_product_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_product_start" says "start": a word for a change.

    What this check looks for
  • The server marks "ihumane_module" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "open": a word for a change.

    What this check looks for
  • The server marks "ihumane_copy_start" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_copy_start" says "copy": a word for a change.

    What this check looks for
Show 5 more findings
  • The server marks "ihumane_get_rules" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "ihumane_get_rules" says "get": a word for reading.

    What this check looks for
  • The server marks "ihumane_translate_taste" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "ihumane_review" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "ihumane_human" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The description is 2,298 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ts by CSS class or position, and the real clock or random numbers inside a check."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 4 changed.+2 added~4 changedView diff
  2. Tools2 added, 4 changed.+2 added~4 changedView diff

Install

Pinned to version 0.8.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ihumane__ihumane_get_check"
    ],
    "ask": [
      "mcp__ihumane__ihumane_start",
      "mcp__ihumane__ihumane_ui_start",
      "mcp__ihumane__ihumane_code_start",
      "mcp__ihumane__ihumane_product_start",
      "mcp__ihumane__ihumane_module",
      "mcp__ihumane__ihumane_copy_start",
      "mcp__ihumane__ihumane_get_rules",
      "mcp__ihumane__ihumane_translate_taste",
      "mcp__ihumane__ihumane_review",
      "mcp__ihumane__ihumane_human",
      "mcp__ihumane__ihumane_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ihumane. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.ihumane/ihumane/verify?hash=250faceb8d37d2a36a7efb6fb648bf02c468ee221d729759e6354a8688707b80" | jq -e '.changed == false'

Pinned hash 250faceb8d37, from Nov 10, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.ihumane/ihumane/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.ihumane/ihumane
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.ihumane/ihumane.svg)](https://radar.anlyon.com/servers/ai.ihumane/ihumane)

Source: MCP Registry. Synced Nov 10, 2026, 21:17 UTC.

ihumane MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ihumane MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 11 of which can change, send or delete something, and 11 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ihumane MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the ihumane MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the ihumane MCP server have?

12 tools: 11 write, 1 read. ihumane_start, ihumane_ui_start, ihumane_code_start, ihumane_product_start, ihumane_module, ihumane_copy_start, ihumane_get_rules, ihumane_translate_taste and 4 more.

Does the ihumane MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ihumane MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the ihumane MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.