Skip to content

KATA Research Automation MCP server

io.github.dharan1007/katadharan1007streamable-httpv3.0.0Scanned

Deterministic research automation with live OpenAlex search and reusable workflow programs.

8 tools: 6 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 6 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

6 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 KATA Research Automation MCP server can do

The KATA Research Automation MCP server is published by the GitHub account dharan1007. It has 8 tools. It can create or change data (6 tools: kata_plan_triage, kata_diagnose_web_interop, kata_apply_command, kata_compile_workflow and 2 more), but cannot delete data. 2 tools only read.

3 tools bring in text other people can write (kata_search_research, kata_plan_triage and kata_run_automation).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 3.0.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.

8 tools

Changes things 6Claude Code: ask
  • kata_apply_commandApply one allowlisted semantic workspace command and return the next workspace snapshot.No findings

    Why it is in this group

    • The name "kata_apply_command" says "apply": a word for a change.
    Description, as the server wrote it
    Apply one allowlisted semantic workspace command and return the next workspace snapshot.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • kata_compile_workflowCompile two compatible semantic demonstrations into a deterministic JSON-Schema-constrained program.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Compile two compatible semantic demonstrations into a deterministic JSON-Schema-constrained program.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • kata_diagnose_web_interopClassify observed WebMCP, MCP, browser and API constraints and return a conservative compliant integration path without weakening security controls.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Classify observed WebMCP, MCP, browser and API constraints and return a conservative compliant integration path without weakening security controls.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • kata_execute_programExecute a compiled deterministic program transactionally against a supplied workspace snapshot.No findings

    Why it is in this group

    • The name "kata_execute_program" says "execute": a word for a change.
    Description, as the server wrote it
    Execute a compiled deterministic program transactionally against a supplied workspace snapshot.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • kata_plan_triageCreate a deterministic triage plan from live OpenAlex results or supplied works without mutating a workspace.Reads text others write1 finding

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Create a deterministic triage plan from live OpenAlex results or supplied works without mutating a workspace.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • kata_run_automationRun a deterministic automation only when its preview fingerprint still matches current inputs.Reads text others writeNo findings

    Why it is in this group

    • The name "kata_run_automation" says "run": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Run a deterministic automation only when its preview fingerprint still matches current inputs. Nested tools are depth-bounded.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools
  • kata_preview_automationPreview an automation and return matching works plus an integrity fingerprint.No findings

    Why it is in this group

    • The name "kata_preview_automation" says "preview": a word for reading.
    Description, as the server wrote it
    Preview an automation and return matching works plus an integrity fingerprint. Makes no changes.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • kata_search_researchSearch live scholarly works through OpenAlex.Reads text others writeNo findings

    Why it is in this group

    • The name "kata_search_research" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search live scholarly works through OpenAlex. Returns normalized real research records; never mock data.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
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 20, 2026, 19:04 UTC, unchanged since Oct 22, 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
6
Protocol version
2025-11-25
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 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://kata-webmcp.vercel.app/api/mcp: tools/list returned 8 tools to an anonymous client, including kata_plan_triage (write), kata_diagnose_web_interop (write), kata_apply_command (write), kata_compile_workflow (write), kata_execute_program (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

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

    Matched text

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

    What this check looks for

History

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

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http kata https://kata-webmcp.vercel.app/api/mcp
claude mcp add --transport http kata https://kata-webmcp.vercel.app/api/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__kata__kata_search_research",
      "mcp__kata__kata_preview_automation"
    ],
    "ask": [
      "mcp__kata__kata_plan_triage",
      "mcp__kata__kata_diagnose_web_interop",
      "mcp__kata__kata_apply_command",
      "mcp__kata__kata_compile_workflow",
      "mcp__kata__kata_execute_program",
      "mcp__kata__kata_run_automation"
    ],
    "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 kata. Review it before you use it.

Capability tags behind 3 rules
  • mcp__kata__kata_search_research untrusted-input
  • mcp__kata__kata_plan_triage untrusted-input
  • mcp__kata__kata_run_automation untrusted-input

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/io.github.dharan1007/kata/verify?hash=9840f833bdef0130ec479bf41212dabbdbc620747126d9a01c819b0753ad6892" | jq -e '.changed == false'

Pinned hash 9840f833bdef, from Nov 19, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.dharan1007/kata/changes.xml

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

Badge

Anlyon Radar badge for io.github.dharan1007/kata
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.dharan1007/kata.svg)](https://radar.anlyon.com/servers/io.github.dharan1007/kata)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:32 UTC.

KATA Research Automation MCP server: questions and answers

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

Is the KATA Research Automation MCP server safe?

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

Can the KATA Research Automation MCP server delete data?

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

Can the KATA Research Automation 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 KATA Research Automation MCP server have?

8 tools: 6 write, 2 read. kata_plan_triage, kata_diagnose_web_interop, kata_apply_command, kata_compile_workflow, kata_execute_program, kata_run_automation, kata_search_research and kata_preview_automation.

Does the KATA Research Automation MCP server need sign-in or OAuth?

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

Does the KATA Research Automation MCP server send data to outside services?

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

Has the KATA Research Automation MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.