# METODIC (remote · www.metodic.io)

Design workshops from chat: 750+ facilitation methods, timed agendas, worksheets, slide decks.

- Trust score: 93/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.metodic.io`: 93/100 (this document), [markdown](https://verifymcp.io/servers/io-metodic-metodic/www.md), [page](https://verifymcp.io/servers/io-metodic-metodic/www)

## Channel facts

- Endpoint: `https://www.metodic.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 6155 tokens (~293/item across 21 items; 20 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the METODIC MCP server?

METODIC is a hosted endpoint at https://www.metodic.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-metodic-metodic 'https://www.metodic.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-metodic-metodic": {
      "url": "https://www.metodic.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-metodic-metodic": {
      "type": "http",
      "url": "https://www.metodic.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-metodic-metodic]
url = "https://www.metodic.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-metodic-metodic": {
      "type": "remote",
      "url": "https://www.metodic.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-metodic-metodic --url 'https://www.metodic.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-metodic-metodic:
    url: "https://www.metodic.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-metodic-metodic": {
      "Transport": "http",
      "Url": "https://www.metodic.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-metodic-metodic -t streamable-http -u 'https://www.metodic.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-metodic-metodic": {
      "type": "http",
      "url": "https://www.metodic.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 93, 0)

- [cosmetic] “design_session” reworded the description of “format”

### 2026-11-03 (score 93, 0)

- [security] Stability: 0.97 → pass

### 2026-11-02 (score 93, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 91, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 90, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (20)

### `list_frameworks` (~82 tokens)

Browse frameworks

Browse Metodic's learning and facilitation frameworks (Design Thinking, Liberating Structures, 4C/ID, PreMortem and more) with what each is best for and when to use it. Use it to ground a session design in a real methodology rather than a generic structure.

Input parameters:

- `query` (string): Optional keyword to filter by name/category.

### `find_session_format` (~244 tokens)

Find a proven session format

START HERE when someone describes a PROBLEM or CHALLENGE ('our leadership team works in silos', 'nobody speaks up in retros', 'we need to align on strategy') and wants a session for it. Returns proven, ready-made session formats from Metodic's catalogue: the problem each one solves, who it is for, how long it runs, what it produces, WHY it works, and the named methodology it is built on. These are designed formats, not improvised ones — recommend from these before proposing a structure of your own, and name what each is grounded in. Free and instant. When the user picks one, call design_session with its format_slug.

Input parameters:

- `audience` (string): Optional: who is in the room, e.g. 'executives', 'agile teams', 'teachers'.
- `challenge` (string, required): The problem in the user's own words, e.g. 'departments blame each other instead of solving things'.
- `language` (string): Optional ISO code (en, nl, es, ja). Defaults to the user's language.
- `max_duration` (number): Optional: longest acceptable session length in minutes.

### `answer_from_library` (~588 tokens)

Answer from the Metodic library

The answer format for anything the user could pick up and use. ALWAYS use this — not generate_document, not prose, not a web search — for a question about WHAT TO USE OR READ — 'which energizer for a flat afternoon group', 'what learning formats could I run this session as', 'which framework fits a two-day programme', 'give me a case for this topic'. MATCH THE TOOL TO WHAT WAS ASKED. Asked which SESSIONS, programmes, formats or examples of sessions ('what could I run for an offsite with 30 people', 'show me examples of sessions like this') → find_session_format, and put the results in the formats field, plus list_my_sessions in my_sessions when they mean their own. Asked which ACTIVITY or working form → search_methods, into methods. Asked which METHODOLOGY → list_frameworks, into framework. Reading → search_articles, into reading. Answering a question about sessions with a list of methods is the wrong answer to the question. First call the matching lookup to see what exists, then call THIS with the few you picked and, for each, WHY it fits this user's situation. Metodic resolves every slug against the real library and renders one branded answer card; anything that does not exist is silently left out. Do not answer such questions in prose and do not dump a search result — a chosen shortlist with reasoning is the whole point. Free.

Input parameters:

- `case` (object): Optional single written case. For several, use cases instead.
- `cases` (array): Optional written cases to put in front of participants — use THIS when the user asks for more than one ('give me three cases'). Each is a short scenario the group works on. This is where a case belon…
- `formats` (array): Optional ready-made session formats (slugs from find_session_format).
- `framework` (object): Optional framework to hang it on.
- `intro` (string, required): One or two sentences framing your answer: what you went for and why.
- `methods` (array): Methods you picked, in the order you'd recommend them.
- `my_sessions` (array): Optional: the user's own earlier sessions worth reusing (ids from list_my_sessions).
- `note` (string): Optional closing caveat or tip.
- `question` (string, required): The user's question, in their own words — becomes the heading.
- `reading` (array): Optional reading. Use article_slug for a Metodic article; otherwise give title and author and it is shown as an external work.
- `session_id` (string): Optional but STRONGLY preferred when the conversation is about a session: saves this answer to that session's Answers tab in Metodic, so it outlives this chat. Pass it whenever you know which session…

### `search_articles` (~112 tokens)

Search Metodic's articles

Search Metodic's own published articles on facilitation, workshop design and learning. Use this BEFORE reaching for the open web whenever the user asks for sources, background, reading or inspiration: Metodic has its own writing on these subjects, and an article found here can be cited by slug in answer_from_library and saved to the session. Returns slug, title and summary. Free and instant.

Input parameters:

- `query` (string, required): Keywords, e.g. 'psychological safety', 'retrospective', 'bias'.

### `search_methods` (~158 tokens)

Search method library

Search Metodic's library of PROVEN facilitation methods — hundreds of real, tested formats with timing, step-by-step instructions, facilitator tips and materials (plus any the user saved themselves). ALWAYS use this before suggesting an activity, exercise, energiser, icebreaker, ideation format, retro or workshop segment: recommend methods that exist and have been run, instead of inventing one. Filter by keyword, max duration and category. Free and instant.

Input parameters:

- `category` (string): Optional category filter.
- `max_duration` (integer): Only methods that fit within this many minutes.
- `query` (string): Keyword(s) matched against title/description/category, e.g. 'icebreaker', 'prioritise', 'stakeholder'.

### `design_session` (~460 tokens)

Design a session

Turn the conversation into a REAL session in the user's Metodic account: a timed agenda built from the method library, saved and ready to run, edit, share and export. Returns a session_id immediately and the Metodic card fills itself in about a minute — do not poll design_status yourself unless the client has no card. Costs 2 Metodic credits. This is the hand-off from chat to Metodic: after it, offer worksheets/handouts/documents or send the user to their session.

Input parameters:

- `audience` (string): Audience or experience level (e.g. 'beginners', 'leadership team').
- `days` (integer): Number of days (default 1). Set this whenever the user says two-day, three-day, multi-day or an offsite spanning several days — each day then gets its own opening, breaks and closing, and its own clo…
- `duration_minutes` (integer, required): TOTAL session length in minutes, across all days (min 30). For a two-day programme of about 7 hours a day, that is 840.
- `format` (string): How people take part: 'in-person', 'online' or 'hybrid'. Set it whenever the user says so (an online seminar, on Zoom, in our office): every step is written for that mode.
- `format_slug` (string): Optional: the slug of a proven format from find_session_format. Seeds the design with that structure and records that the format was used — pass it whenever the user picked one.
- `framework` (string): Optional framework slug/name from list_frameworks.
- `goal` (string): The purpose / desired outcome — pass the user's FULL brief verbatim (context, the client's own vocabulary, the named people and their tensions, the constraints, what must NOT happen). The Architect d…
- `language` (string): ISO code (en/nl/es/fr/de/pt/it/ja/zh). Default en.
- `participants` (integer): Number of participants (default 12).
- `topic` (string, required): What the session is about (title or subject).

### `design_status` (~65 tokens)

Design status

Check whether a session started with design_session is ready. While generating it returns a wait instruction; when ready it returns the BRANDED HTML SESSION BRIEF — render it as an artifact. Free (no credits).

Input parameters:

- `session_id` (string, required): The session id design_session returned.

### `refine_session` (~282 tokens)

Refine session agenda

Modify an existing session's agenda IN PLACE without leaving the chat: retime, rename, move, remove or update activities, or add new ones. Put EVERY change the user asked for in ONE call — a second call paints a second full session brief and the user sees the agenda twice. Give a list of operations; they apply in order, and activity numbers are 1-based positions in the agenda AS IT STANDS after any earlier operations in the same call. Start/end times are recomputed automatically and newly added activities get full step-by-step method details. Returns the updated, branded session brief in full, shown right in the chat — so a change looks the same as the original design. Prefer this over sending the user to Metodic for an edit. This edits the same session Metodic Studio shows.

Input parameters:

- `operations` (array, required): Changes to apply, in order. Shapes: {op:'retime', activity, duration_minutes} · {op:'rename', activity, title} · {op:'remove', activity} · {op:'move', activity, to} · {op:'update', activity, descript…
- `session_id` (string, required): The Metodic session (toolkit) id.

### `get_session` (~131 tokens)

Session run-sheet

READ a session so YOU know what is in it before answering a follow-up — this returns text for you, not something the user sees. To SHOW the session to the user, call session_one_pager instead. Gives every activity's agenda slot, method, step-by-step instructions, facili — every activity's agenda slot, method, step-by-step instructions, facilitator tips and materials. Plus a Metodic link for the branded/editable version. Use this to show a session's runnable detail without leaving the chat.

Input parameters:

- `session_id` (string, required): The Metodic session (toolkit) id.

### `session_one_pager` (~146 tokens)

Branded one-pager

Return a complete, self-contained, Metodic-BRANDED HTML one-pager of a session (logo, brand colours, agenda table, activity cards). RENDER THE RETURNED HTML AS AN ARTIFACT so the user sees the branded document. Use for the FULL session overview: the agenda with activity detail, for the facilitator or for stakeholders who want to see the whole design. FREE (no AI, no credits). For a written document with its own purpose and audience — a participant pre-read, briefing email attachment, client brief, prep notes — use generate_document instead.

Input parameters:

- `session_id` (string, required): The Metodic session (toolkit) id.

### `generate_document` (~375 tokens)

Generate document

NOT for a list of sources, methods, formats or reading — that is answer_from_library, which draws on Metodic's own library and saves the result to the session. Use this only for a WRITTEN DOCUMENT with its own audience: a pre-read, a briefing, a client brief, prep notes, an invitation, a follow-up. Creates it with Metodic's real document builder (the same 'Documents' generator as Metodic's Materials tab) and return it as a branded HTML artifact — it is also saved to the session's Documents in Metodic. Use for ANY written document around a session: a participant PRE-READ or BRIEFING to email before the day, a CLIENT BRIEF for the sponsor, facilitator prep notes, an invitation, follow-up summary, or a fill-in template. Do NOT author these documents yourself — this tool writes them in the user's Metodic brand. Takes ~20-30s and ~0.5 Metodic credit.

Input parameters:

- `audience` (string): Who reads it: participant (default), facilitator, or client/sponsor.
- `content_spec` (string): Optional: what it should contain / structure / things to include or deliberately leave out (e.g. 'no method names — keep the exercises a surprise').
- `force` (boolean): Only when the user explicitly wants a separate sendable document that happens to contain cases. Without it, a request for cases is redirected to answer_from_library, where it is saved to the session.
- `purpose` (string, required): What the document is for and what it must achieve, in 1-3 sentences.
- `session_id` (string, required): The Metodic session (toolkit) id.
- `title` (string, required): Document title, e.g. 'Pre-read for participants'.

### `list_my_sessions` (~20 tokens)

My sessions

List the user's recent Metodic sessions with links.

### `share_session` (~250 tokens)

Share a session

Create a shareable link to a session so someone else can see it WITHOUT a Metodic account: a client or sponsor who has to approve the programme, a co-facilitator, or the participants. Optionally writes a client-facing brief first (audience 'client') and shares that alongside the plan. Returns the link. Reuses an existing link for the same session instead of making a second one. Free unless a brief is generated (~0.5 credit).

Input parameters:

- `audience` (string): Who the link is for. 'client' is the default and the most common: a sponsor who must approve it.
- `document` (string): Which saved document opens on the shared page: 'latest' (default for a client — the most recent document in the session, e.g. a brief you just wrote), 'none' for the plan only, or a document id.
- `expires_in_days` (integer): Optional: let the link expire after this many days.
- `session_id` (string, required): Metodic session id.
- `with_brief` (boolean): Also write a short client-facing brief for the session (costs ~0.5 credit). Default false.

### `get_credits` (~53 tokens)

Credit balance

Show the user's available Metodic credits (the balance that generation tools spend — for team members this is the team's shared balance). Call when the user asks about credits, cost, or whether they can afford a generation.

### `add_debrief` (~167 tokens)

Save session debrief

Save a post-session DEBRIEF onto the session in Metodic: how it went, what worked, what to improve, follow-ups. Call after the user has run their workshop and tells you how it went (or after a debrief conversation) — synthesize first, then save. Debriefs accumulate on the session; nothing is overwritten.

Input parameters:

- `follow_ups` (array): Actions owed after the session.
- `notes` (string, required): The debrief synthesis — how the session actually went.
- `rating` (integer): Overall 1-5.
- `session_id` (string, required): The Metodic session (toolkit) id.
- `to_improve` (array): Things to change next time.
- `went_well` (array): Things that worked.

### `generate_worksheet` (~261 tokens)

Generate worksheet

Generate the A4 PARTICIPANT WORKSHEET for ONE activity — the sheet each participant fills in on their own, at the table. NOT the big sheet on the wall: if the user says canvas, wall canvas, poster, brownpaper, large format, A1, A0, matrix or mapping wall, use generate_canvas instead. Uses Metodic's real generator and returns a branded document in the chat (also saved to the session for the print-ready PDF) — do NOT author these yourself. Give the activity's number (1-based, from the agenda). For a whole session, call this once per activity (1, then 2, …). Takes ~15-20s and ~0.5 Metodic credit each — but if a worksheet for that activity already exists it comes back for free, so just ask. Framing activities (Opening/Closing) have no worksheet.

Input parameters:

- `activity` (integer, required): The activity's number in the agenda (1-based).
- `regenerate` (boolean): Only set this to true when the user explicitly wants a NEW version. Left out, an existing one is returned as-is and costs nothing.
- `session_id` (string, required): The Metodic session (toolkit) id.

### `generate_canvas` (~352 tokens)

Generate a wall canvas

THE TOOL FOR ANY CANVAS. Generate the large-format WALL CANVAS for ONE activity using Metodic's real canvas generator, and return it as a branded document in the chat (also saved to the session, and replayable 1:1 to a Miro board). This is the big thing that goes ON THE WALL and that a group fills in together — sized to who shares it (one A1 for the whole room, an A2 per small group) — as opposed to generate_worksheet, which makes the A4 that each participant works on alone. Ask for this whenever the user says canvas, wall canvas, poster, large format, brownpaper, matrix or mapping wall. Give the activity's number (1-based, from the agenda). Takes ~20-30s and 0.5 Metodic credit.

Input parameters:

- `activity` (integer, required): 1-based activity number from the agenda.
- `canvas_type` (string): Optional canvas shape. Metodic has ready-made ones: swot, empathy-map, stakeholder-map, business-canvas, priority-matrix, decision-matrix, journey-map, reflection. Anything else (or leaving it out) m…
- `regenerate` (boolean): Only set this to true when the user explicitly wants a NEW version. Left out, an existing one is returned as-is and costs nothing.
- `session_id` (string, required): The Metodic session id.
- `size` (string): Print size. Leave it on auto: the canvas is A1 when the whole room shares it and A2 when each small group gets its own. Only set it when the user asks for a size.

### `generate_handout` (~185 tokens)

Generate handout

Generate a participant HANDOUT or reference material for ONE activity using Metodic's real generator, and return it as a branded HTML artifact in the chat (also saved to the session). Unlike a worksheet (which participants fill in), a handout is READING/REFERENCE material the participant keeps beside their worksheet — background, a framework, a case study, a persona, a checklist. Give the activity's number (1-based) and optionally a `kind`. Framing activities (Opening/Closing) can have handouts too. Takes ~15-30s and ~0.5 Metodic credit.

Input parameters:

- `activity` (integer, required): The activity's number in the agenda (1-based).
- `kind` (string): What kind of reference material to make. Default: handout.
- `session_id` (string, required): The Metodic session (toolkit) id.

### `generate_slides` (~150 tokens)

Generate slide deck

Generate the session's SLIDE DECK with Metodic's real generator — the same facilitation deck the Metodic app makes: an opening, the day's journey with real times, per activity a chapter, the task (steps, who with, what you make, what you need) and a timer bound to its minutes, breaks with the real return time, live questions, and a closing, all with speaker notes. Shown in the chat as a slide viewer, and saved to the session. One call makes the whole deck. Takes ~40-90s and ~2 Metodic credits.

Input parameters:

- `session_id` (string, required): The Metodic session (toolkit) id.

### `generate_cards` (~139 tokens)

Generate card deck

Generate a METHOD CARD DECK for the session using Metodic's real generator, and shown in the chat as Metodic's paper cards (category post-it colours, icon on the front, steps and a tip on the back; tap a card to turn it). Also saved to the user's decks. One call makes the whole deck. Takes ~30-60s and ~2 Metodic credits.

Input parameters:

- `count` (integer): Roughly how many cards to aim for (e.g. 8-16). Optional.
- `session_id` (string, required): The Metodic session (toolkit) id to base the deck on.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-metodic-metodic/www#diagnostics

## Score history

- 2026-11-05: 93
- 2026-11-04: 93
- 2026-11-03: 93
- 2026-11-02: 93
- 2026-11-01: 92
- 2026-10-31: 92
- 2026-10-30: 91
- 2026-10-29: 91
- 2026-10-28: 90
- 2026-10-27: 90
- 2026-10-26: 90
- 2026-10-25: 89
- 2026-10-24: 89
- 2026-10-23: 88
- 2026-10-22: 88
- 2026-10-21: 87
- 2026-10-20: 87
- 2026-10-19: 86
- 2026-10-18: 86
- 2026-10-17: 85
- 2026-10-16: 85
- 2026-10-15: 84
- 2026-10-14: 84
- 2026-10-13: 83
- 2026-10-12: 83
- 2026-10-10: 82
- 2026-10-04: 79

## Common questions

### What is the METODIC MCP server?

METODIC is an MCP server listed in the public MCP registry as io.metodic/metodic. Design workshops from chat: 750+ facilitation methods, timed agendas, worksheets, slide decks. This page covers its hosted endpoint (https://www.metodic.io/mcp).

### Is the METODIC MCP server safe to use?

METODIC scores 93 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the METODIC MCP server expose?

METODIC exposes 20 tools: list_frameworks, find_session_format, answer_from_library, search_articles, search_methods, and 15 more. Their descriptions and schemas cost roughly 4,220 tokens of context every time the server is loaded.

### Does the METODIC MCP server require authentication?

Yes. METODIC asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the METODIC MCP server still maintained?

METODIC is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the METODIC MCP server?

VerifyMCP ran 14 checks on METODIC, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.metodic.io/mcp
- Website: https://www.metodic.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-metodic-metodic/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-metodic-metodic/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-metodic-metodic/www.json
- HTML version of this page: https://verifymcp.io/servers/io-metodic-metodic/www